Open Software Solutions

Consider the following scenario:

•	You are running a Windows Vista-based computer in a network environment. There are multiple computers in this network.
•	You assign or change the IP address for the Windows Vista-based computer. You do this either manually or by using an application.

In this scenario, you receive the following error message about a network error that concerns duplicate address detection (DAD):

Additionally, the following event is logged in the System log:

Event ID: 4199
Event Source: Tcpip
Event Type: Error
Description:
The system detected an address conflict for IP address <IP address> with the system having network hardware address <MAC address>. Network operations on this system may be disrupted as a result.

Back to the top

After you assign or change an IP address on a Windows Vista-based computer, the system searches the network for a computer that is already using this IP address. If the search reveals no computer that is already using this IP address, the IP address is officially assigned to the Windows Vista-based computer. The problem that is described in the Symptoms section occurs if another computer sends a ping message to the new IP address before the system finishes the search process. The system was not designed to be pinged while it is searching for a new IP address.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Update.mum	Not Applicable	2,226	06-Feb-2008	17:43	Not Applicable
X86_0e9f6a6025542fd410733180ad52a98f_31bf3856ad364e35_6.0.6000.20766_none_8deb993f272788ba.manifest	Not Applicable	1,045	06-Feb-2008	17:43	Not Applicable
X86_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.0.6000.20766_none_5503ed2ed16fd5e8.manifest	Not Applicable	3,908	06-Feb-2008	04:38	Not Applicable
X86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20766_none_5fee1635ab7bf941.manifest	Not Applicable	28,871	06-Feb-2008	04:36	Not Applicable
Netio.sys	6.0.6000.20766	217,144	06-Feb-2008	04:20	x86
Netiomig.dll	6.0.6000.20766	49,152	06-Feb-2008	04:13	x86
Netiougc.exe	6.0.6000.20766	22,016	06-Feb-2008	02:14	x86
Tcpip.sys	6.0.6000.20766	806,400	06-Feb-2008	02:16	x86
Tcpipcfg.dll	6.0.6000.20766	167,424	06-Feb-2008	04:15	x86

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_9b471cd1c1d80e4b4708dd208166ac69_31bf3856ad364e35_6.0.6000.20766_none_5e3248a71dcc73cd.manifest	Not Applicable	1,051	06-Feb-2008	17:43	Not Applicable
Amd64_e3d5402babe726048033206ef9f013e9_31bf3856ad364e35_6.0.6000.20766_none_74a99771b5e9a34a.manifest	Not Applicable	1,051	06-Feb-2008	17:43	Not Applicable
Amd64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.0.6000.20766_none_b12288b289cd471e.manifest	Not Applicable	3,916	06-Feb-2008	05:00	Not Applicable
Amd64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20766_none_bc0cb1b963d96a77.manifest	Not Applicable	28,941	06-Feb-2008	04:58	Not Applicable
Package_1_for_kb948363~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,022	06-Feb-2008	17:43	Not Applicable
Package_2_for_kb948363~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,239	06-Feb-2008	17:43	Not Applicable
Update.mum	Not Applicable	1,925	06-Feb-2008	17:43	Not Applicable
Wow64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.0.6000.20766_none_bb773304be2e0919.manifest	Not Applicable	2,730	06-Feb-2008	04:31	Not Applicable
Wow64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20766_none_c6615c0b983a2c72.manifest	Not Applicable	22,999	06-Feb-2008	04:31	Not Applicable
Netio.sys	6.0.6000.20766	324,664	06-Feb-2008	04:42	x64
Netiomig.dll	6.0.6000.20766	59,904	06-Feb-2008	04:31	x64
Netiougc.exe	6.0.6000.20766	25,600	06-Feb-2008	02:33	x64
Tcpip.sys	6.0.6000.20766	1,191,936	06-Feb-2008	02:35	x64
Tcpipcfg.dll	6.0.6000.20766	232,960	06-Feb-2008	04:33	x64
Netiomig.dll	6.0.6000.20766	49,152	06-Feb-2008	04:13	x86
Netiougc.exe	6.0.6000.20766	22,016	06-Feb-2008	02:14	x86
Tcpipcfg.dll	6.0.6000.20766	167,424	06-Feb-2008	04:15	x86

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about duplicate address detection (DAD), visit the following MSDN Web site:

Back to the top