This article was previously published under Q287032
This article has been archived. It is offered "as is" and will no longer be updated.
If the AddIpAddress function is used repeatedly to add dynamic IP addresses to adapters in a multihomed computer, the routes may be incorrect and it may not be possible to communicate with other computers.
This problem occurs because TCP/IP does not maintain IP addresses and routing table entries correctly.
Windows NT 4.0
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Size File name Platform ----------------------------------------------- 22/02/2001 12:34 174,704 Tcpip.sys Intel
NOTE: Because of file dependencies, this hotfix requires Microsoft Windows NT 4.0 Service Pack 6a (SP6a).
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
You can work around this problem by removing the addresses in the same order that they were added. However, this workaround has been tested only on a computer with two network adapters. It has not been tested with more than two network adapters.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.