Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A Windows Server 2008 or Windows Server 2008 R2 NAP-enabled DHCP server incorrectly issues fully accessible IP addresses to Windows XP Service Pack 3 clients that are not NAP compliant


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a network for which the Network Access Protection (NAP) feature is enabled.
  • You configure a NAP-enabled Dynamic Host Configuration Protocol (DHCP) server on a computer that is running Windows Server 2008 or Windows Server 2008 R2 in the network.
  • A Windows XP Service Pack 3 (SP3) client that is not NAP compliant joins the network and tries to obtain IP addresses from the NAP-enabled DHCP server.
In this scenario, the Windows XP SP3 client that is not NAP compliant may receive fully accessible IP addresses from the NAP-enabled DHCP server. The expected behavior is that the client can access limited IP address from the DHCP server at any time.

Additionally, if you run the following command on the client several times, you find that the DHCP server gives the restricted IP address and the fully accessible IP address every other time:

ipconfig /release & ipconfig /renew

↑ Back to the top


Cause

The issue occurs because the NAP-enabled DHCP server incorrectly handles the options in the DHCP packets from Windows XP SP3 clients. It causes the DHCP server to bypass NAP authentication and directly grants fully accessible IP address to the Windows XP SP3 clients that are not NAP compliant.

↑ Back to the top


Resolution

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
Additionally, you must have the DHCP server role installed.
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Restart requirements

You must stop the DHCP service before you apply this hotfix, and then restart the DHCP service after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.0.6001.22xxxWindows Server 2008 SP1LDR
    6.0.6002.22xxxWindows Server 2008 SP2LDR
  • Service Pack 1 is integrated into the original release version of Windows Server 2008.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Dhcpserver.events.xmlNot Applicable58104-Mar-201005:48Not Applicable
Dhcpssvc.dll6.0.6001.22945490,49618-Jul-201114:50x86
Dhcpserver.events.xmlNot Applicable58115-Mar-201105:19Not Applicable
Dhcpssvc.dll6.0.6002.22681492,03218-Jul-201115:22x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Dhcpserver.events.xmlNot Applicable58126-Feb-201004:06Not Applicable
Dhcpssvc.dll6.0.6001.22945618,49618-Jul-201115:02x64
Dhcpserver.events.xmlNot Applicable58115-Mar-201104:35Not Applicable
Dhcpssvc.dll6.0.6002.22681620,54418-Jul-201115:32x64
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.1.760
    0.
    20xxx
    Windows Server 2008 R2RTMLDR
    6.1.760
    1.
    21xxx
    Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Dhcpserver.events.xmlNot Applicable60010-Jun-200920:34Not Applicable
Dhcpssvc.dll6.1.7600.20967729,08814-May-201107:33x64
Dhcpserver.events.xmlNot Applicable60005-Nov-201001:52Not Applicable
Dhcpssvc.dll6.1.7601.21728729,08814-May-201107:11x64

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameUpdate.mum
File versionNot Applicable
File size2,238
Date (UTC)19-Jul-2011
Time (UTC)07:17
PlatformNot Applicable
File nameX86_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.0.6001.22945_none_296d4762b0c458d9.manifest
File versionNot Applicable
File size141,628
Date (UTC)18-Jul-2011
Time (UTC)15:08
PlatformNot Applicable
File nameX86_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.0.6002.22681_none_2b247872ae0eb865.manifest
File versionNot Applicable
File size141,628
Date (UTC)18-Jul-2011
Time (UTC)15:43
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.0.6001.22945_none_858be2e66921ca0f.manifest
File versionNot Applicable
File size141,672
Date (UTC)18-Jul-2011
Time (UTC)15:17
PlatformNot Applicable
File nameAmd64_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.0.6002.22681_none_874313f6666c299b.manifest
File versionNot Applicable
File size141,672
Date (UTC)18-Jul-2011
Time (UTC)15:55
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,254
Date (UTC)19-Jul-2011
Time (UTC)07:17
PlatformNot Applicable

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_2337abaac2afa50fcb46a0fcde670d75_31bf3856ad364e35_6.1.7601.21728_none_898b3936775b224f.manifest
File versionNot Applicable
File size709
Date (UTC)16-May-2011
Time (UTC)12:19
PlatformNot Applicable
File nameAmd64_d9abfd4516df878dc66fc3ac8daba3bb_31bf3856ad364e35_6.1.7600.20967_none_e15af16d9ff03894.manifest
File versionNot Applicable
File size709
Date (UTC)16-May-2011
Time (UTC)12:19
PlatformNot Applicable
File nameAmd64_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.1.7600.20967_none_85a01201ca477460.manifest
File versionNot Applicable
File size194,101
Date (UTC)14-May-2011
Time (UTC)08:10
PlatformNot Applicable
File nameAmd64_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.1.7601.21728_none_87b2af01c74c89df.manifest
File versionNot Applicable
File size194,101
Date (UTC)14-May-2011
Time (UTC)08:48
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,391
Date (UTC)16-May-2011
Time (UTC)12:19
PlatformNot Applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2479424
Revision : 2
Created on : 9/19/2018
Published on : 9/19/2018
Exists online : False
Views : 334