You are currently offline, waiting for your internet to reconnect

IP Address Conflict with Address 0.0.0.0

This article was previously published under Q178550
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
After you install ICMP-fix, the following events may be logged in thesystem event log:

   Event ID: 4199   Source: TCP/IP   Description: The system detected an address conflict for IP address   0.0.0.0 with the system having network hardware address   xx:xx:xx:xx:xx:xx. Network operations on this system may be disrupted as   a result.   Event ID: 26   Source: Applications Popup				

For more information on ICMP-fix, please see the following article in theMicrosoft Knowledge Base:

ARTICLE-ID: 143478
TITLE : Stop 0A in TCPIP.SYS When Receiving Out Of Band (OOB) Data
CAUSE


The ICMP hotfix includes a fix where ARP requests sent from 0.0.0.0 are nowprocessed. The handling of ARP requests sent from 0.0.0.0 has beenintroduced because RFC 1541 suggests that a DHCP client should verify an IPlease offered from a DHCP server by sending an ARP request. In the RFC, thesender's IP address is defined as 0.0.0.0.

If a computer is in a state where it has no valid IP address lease (forexample, when starting or when the lease has expired), the computer'sTCP/IP stack is initialized with the address 0.0.0.0.

If, in this state, an ARP request with sender's IP address 0.0.0.0 isreceived, the above events will be logged.

For additional information on the ICMP hotfix, please see the followingarticle in the Microsoft Knowledge Base:

ARTICLE-ID: 154174
TITLE : Invalid ICMP Datagram Fragments Hang Windows NT, Windows 95
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Properties

Article ID: 178550 - Last Review: 12/05/2015 08:15:18 - Revision: 1.2

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • kbnosurvey kbarchive kbbug kbfix KB178550
Feedback