Expected Behavior of Multiple Adapters on Same Network

• Microsoft Windows NT Workstation version 4.0
• Microsoft Windows NT Server version 4.0
• Microsoft Windows NT Server, Enterprise Edition version 4.0 - Microsoft Cluster Server

SUMMARY

If you configure a computer running Windows NT with more than one network adapter on the same physical network and subnet, the behavior may or may not be as expected as compared to other implementations. This article discusses expected behavior of this type of nonstandard Windows NT configuration.

MORE INFORMATION

Consider the following configuration of a computer running Microsoft Windows NT:

• A working computer with Microsoft Windows NT installed.
• Two network adapters connected to the same physical network (or hub).
• TCP/IP installed as the network protocol
• Adapter addresses on the same subnetwork 192.168.0.1 and 192.168.0.2
• Assume a client on the network uses the address 192.168.0.119

Assume that the server needs to send a packet using the TCP/IP protocol to a client with the address 192.168.0.119. This address is on the local subnet, so use of a gateway is not required to reach the client. The protocol stack uses the first route it finds in the local routing table. This is typically the first adapter installed, which, in this case, is 192.168.0.1. If the transmission fails, subsequent retries may use the same adapter according to the entry found in the routing table.

If the network cable for the 192.168.0.1 adapter fails, this does not necessarily cause the routing table to be updated with the removal of the route. Therefore, the second adapter still may not be used.

Another consideration is that some network applications bind to specific adapters in the system. If a network application were to bind to the second adapter specifically, application-related traffic received from clients on the first adapter may be ignored by the application. This may be a result of NetBIOS name registration on the network. Additionally, if the adapter fails to which the application is bound, the application may fail if it does not decide to use the other adapter. Depending on the application, the other adapter may or may not be used.

In most instances, unless applications specifically demand, this type of configuration is not beneficial. Some manufacturers make fault-tolerant network adapters to guard against a single point of failure. These adapters allow two adapters to be placed in the same server, but only allow use of one adapter at a time. If the primary adapter fails, the driver deactivates the first card and activates the second with the same address configuration. The end result is a fairly seamless transition to the alternate adapter. This is the preferred method to guard against a single network adapter as a single point of failure.

Microsoft Cluster Server

Microsoft Cluster Server (MSCS) does not make use of additional adapters on the same network and relies on existing features of the TCP/IP protocol. In the event of adapter failure, the software does not automatically try to register IP Address Resource addresses on the other adapter. If you want to avoid a single network adapter as a single point of failure, consider use of a fault-tolerant network adapter set as mentioned previously in this article.