IP Address Conflict with Address 0.0.0.0Last reviewed: January 28, 1998Article ID: Q178550 |
The information in this article applies to:
SYMPTOMSAfter you install ICMP-fix, the following events may be logged in the system event log:
ARTICLE-ID: Q143478 TITLE : Stop 0A in TCPIP.SYS When Receiving Out Of Band (OOB) Data CAUSEThe ICMP hotfix includes a fix where ARP requests sent from 0.0.0.0 are now processed. The handling of ARP requests sent from 0.0.0.0 has been introduced because RFC 1541 suggests that a DHCP client should verify an IP lease offered from a DHCP server by sending an ARP request. In the RFC, the sender'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 (for example, when starting or when the lease has expired), the computer's TCP/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 is received, the above events will be logged. For additional information on the ICMP hotfix, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q154174 TITLE : Invalid ICMP Datagram Fragments Hang Windows NT, Windows 95RESOLUTION Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. Keywords : kbbug4.00 kbfix4.00 NTSrvWkst Version : WinNT:4.0 Platform : winnt Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |