A DHCP Client May Send an Incorrect FQDN in a DHCP-Request Packet

Article translations Article translations
Article ID: 317288 - View products that this article applies to.
This article was previously published under Q317288
Expand all | Collapse all

SYMPTOMS

A Dynamic Host Configuration Protocol (DHCP) client may send an incorrect fully qualified domain name (FQDN) in the DHCP-Request packet in option field 81. The client may send the primary domain suffix instead of the connection-specific domain suffix, even though the "Register DNS records with connection-specific DNS suffix" policy has been turned on. When this situation occurs, you see an incorrect FQDN in the Name column if you look at the address lease on the DHCP server.

CAUSE

This behavior occurs because the DHCP client is not parsing policy settings correctly.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to Obtain the Latest Windows XP Service Pack
The English version of this fix should have the following file attributes or later:
   Date         Time   Version      Size   File name
   ----------------------------------------------------
   27-Feb-2002  18:57  5.1.2600.31  94720  Dhcpcsvc.dll
				

STATUS

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 Windows XP Service Pack 1.

Properties

Article ID: 317288 - Last Review: October 27, 2006 - Revision: 1.2
APPLIES TO
  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional
Keywords: 
kbhotfixserver kbqfe kbbug kbfix kbnetwork kbwinxpsp1fix KB317288

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com