Multiple IP Addresses on a Single NIC

This article was previously published under Q149399
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
A computer with two IP addresses assigned to its interface is unable toconnect to computers across a router.
CAUSE
A single network interface card (NIC) configured with multiple IP addressesdefined on different logical subnets will always use the first IP addressdefined in the TCP/IP configuration as its source address, regardless ofthe destination.
RESOLUTION
To resolve this problem, upgrade to Windows NT Workstation and Serverversion 4.0.

The problem does not occur if the computer has one NIC per IP address (twoNICs).
STATUS
Microsoft has confirmed this to be a problem in Windows NT versions 3.5 and3.51. This problem was corrected in Windows NT Workstation or Serverversion 4.0.
MORE INFORMATION
Consider the following scenario:

A computer with a single NIC and two IP addresses--the first is 130.0.3.2,the second 130.1.7.200--is on the same segment where two routers arepresent, router 1 with IP address 130.0.7.1 and router 2 with IP address130.1.7.100.

The route table is as follows:

Network Address  Netmask         Gateway Address  Interface   Metric0.0.0.0          0.0.0.0         130.1.7.1        130.0.3.2   10.0.0.0          0.0.0.0         130.0.7.1        130.0.3.2   1127.0.0.0        255.0.0.0       127.0.0.1        127.0.0.1   1130.0.0.0        255.255.0.0     130.0.3.2        130.0.3.2   1130.0.3.2        255.255.255.255 127.0.0.1        127.0.0.1   1130.0.255.255    255.255.255.255 130.0.3.2        130.0.3.2   1130.1.0.0        255.255.0.0     130.1.7.200      130.0.3.2   1130.1.7.200      255.255.255.255 127.0.0.1        127.0.0.1   1140.1.0.0        255.255.0.0     130.1.7.100      130.0.3.2   1(Previous entry is an added static route)224.0.0.0        224.0.0.0       130.0.3.2         130.0.3.2   1255.255.255.255  255.255.255.255 130.0.3.2         130.0.3.2   1				


Note that the interface is always 130.0.3.2. Network 140.1.0.0 is on theother side of router 2 (130.1.7.100) and a static route was added for it.With this configuration, connectivity to any host on the local subnet withan IP address of 130.0.x.x or 130.1.x.x is possible. Connectivity to anyhost on the other side of router 1 (130.0.3.2) is also possible.Connectivity to anything beyond router 2 is not possible. A network traceshows that the source IP address is 130.0.3.2 when trying to reach adestination over router 2. Router 2 only knows about network 130.1.0.0 anddoesn't have a route defined for network 130.0.0.0.

Note:
  • A static route can be added in router 2 to fix this problem (i.e. route add 130.0.7.1 130.1.7.100).
prodnt
Properties

Article ID: 149399 - Last Review: 12/04/2015 14:28:54 - Revision: 3.1

Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

  • kbnosurvey kbarchive KB149399
Feedback