TCP/IP Bound to Two Different NICs Doesn't Work

ID: Q123280

The information in this article applies to:

Microsoft Windows NT Workstation versions 3.5, 4.0
Microsoft Windows NT Server versions 3.5, 4.0
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server

SYMPTOMS

You have two different network interface cards (NICs) (in the case this problem was discovered, an Intel EE16 and an Eagle NE2000) both bound to TCP/IP, each attached to a different network. Pinging a host on the second NIC in the TCP/IP bindings is unsuccessful. An error message appears explaining that you cannot reach the host with the address of the NIC that appears first in the TCP/IP bindings. You can successfully ping the default gateway associated with the second NIC.

WORKAROUND

Switch the order of the bindings of the two NICs and restart your computer.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: adapter prodnt

Keywords : kbnetwork nttcp kbbug3.50 NTSrvWkst
Version : WINDOWS:2000; winnt:3.5,4.0
Platform : WINDOWS winnt
Issue type :