Microsoft KB Archive/896615

From BetaArchive Wiki

Article ID: 896615

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows XP Professional x64 Edition




SYMPTOMS

When you use a Dynamic Host Configuration Protocol (DHCP) client that is running Microsoft Windows Server 2003, the client may send an incorrect fully qualified domain name (FQDN) to the DHCP server in the option field of a DHCP-Request packet. 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 setting is enabled. When this problem occurs, you see an incorrect FQDN in the Name column of the DHCP server's address lease record for the DHCP client.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003


Hotfix information

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 any other hotfixes.

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 tool in Control Panel.

Windows Server 2003, 32-bit versions
File name File version File size Date Time Platform SP requirement Service branch
Dhcpcsvc.dll 5.2.3790.330 103,424 12-May-2005 02:43 x86 None RTMQFE
Dhcpcsvc.dll 5.2.3790.2443 116,224 12-May-2005 02:49 x86 SP1 SP1QFE
Windows Server 2003, Itanium-based versions
File name File version File size Date Time Platform SP requirement Service branch
Dhcpcsvc.dll 5.2.3790.330 286,208 11-May-2005 14:47 IA-64 None RTMQFE
Wdhcpcsvc.dll 5.2.3790.330 103,424 11-May-2005 14:47 x86 None WOW
Dhcpcsvc.dll 5.2.3790.2443 306,688 11-May-2005 14:47 IA-64 SP1 SP1QFE
Wdhcpcsvc.dll 5.2.3790.2443 116,224 11-May-2005 14:47 x86 SP1 WOW
Windows Server 2003 and Windows XP, x64-based versions
File name File version File size Date Time Platform SP requirement Service branch
Dhcpcsvc.dll 5.2.3790.2443 224,256 11-May-2005 14:47 x64 SP1 SP1QFE
Wdhcpcsvc.dll 5.2.3790.2443 116,224 11-May-2005 14:47 x86 SP1 WOW

Note The x64-based versions of Windows Server 2003 contain the features and fixes in Windows Server 2003 Service Pack 1.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows Server 2003 Service Pack 2.

MORE INFORMATION

For more information about a similar problem that occurs in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

317288 A DHCP client may send an incorrect FQDN in a DHCP-Request packet



Additional query words: DHCP client service

Keywords: kbbug kbfix kbqfe kbpubtypekc kbwinserv2003sp1fix kbwinserv2003presp1fix kbwinxp64bit2003sp1fix kbhotfixserver kbwinserv2003sp2fix KB896615