DHCP Client XIDs Differ in DISCOVER and REQUEST Packets
Article ID: 183180
Article Last Modified on 10/31/2006
APPLIES TO
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0 Developer Edition
This article was previously published under Q183180
SYMPTOMS
When you capture a network trace using a network analyzer, such as
Microsoft Network Monitor, you may see Dynamic Host Control Protocol (DHCP)
traffic where the DHCP client does not use the same xid in its DISCOVER and
REQUEST packets.
RESOLUTION
To resolve this problem, obtain the latest Windows NT 4.0 Service Pack.
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 4.0.
This problem has been corrected in the latest U.S. Service Pack for
Windows NT version 4.0. For information on obtaining the Service Pack,
query on the following word in the Microsoft Knowledge Base:
SERVPACK
Microsoft has confirmed this to be a problem in Windows NT 3.51. We are
researching this problem and will post additional information here in
the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
The xid is the transaction identifier and is used by computers to
synchronize communications and to identify which packet is the correct
response to a request.
REFERENCES
For more information, please see RFC1541.
RFCs may be obtained through the Internet as follows:
Paper copies of all RFCs are available from the NIC, either individually or
on a subscription basis (for more information, contact NIC@NIC.DDN.MIL).
Online copies are available through FTP or Kermit from NIC.DDN.MIL as
rfc/rfc####.txt or rfc/rfc####.PS (#### is the RFC number without leading
zeros).
Keywords: kbbug kbfix KB183180