You are currently offline, waiting for your internet to reconnect

Error message when you add a reservation to a scope on a Windows Server 2008 R2-based DHCP server: "The specified DHCP client is not a reserved client"

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 R2.
  • You install the Dynamic Host Configuration Protocol (DHCP) Server role on the computer.
  • You configure a scope on the DHCP server.
  • You configure a distribution range in the scope. The distribution range does not cover all IP addresses in the scope.
  • You try to add a reservation to the scope. The IP address is outside the configured distribution range.
In this scenario, you cannot add the reservation to the scope, and you receive the following error message:

The specified DHCP client is not a reserved client
This issue occurs because the DHCP server checks to determine whether the IP address is in the defined distribution range of the scope when a new reservation is added.

Hotfix information

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.


To apply this hotfix, you must be running Windows Server 2008 R2. Additionally, you must have the DHCP Server role installed.

Registry information

To use the hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Note If you stop the DHCP Server service before you install this hotfix, you do not have to restart the computer.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global 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 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 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 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 x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform Applicable60010-Jun-200920:34Not Applicable
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_124f637645c08c5ee320087a7fa9af76_31bf3856ad364e35_6.1.7600.20782_none_d12a16cc853ddd65.manifest
File versionNot applicable
File size709
Date (UTC)17-Aug-2010
Time (UTC)07:27
PlatformNot applicable
File nameAmd64_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.1.7600.20782_none_85856cebca5c3341.manifest
File versionNot applicable
File size194,101
Date (UTC)17-Aug-2010
Time (UTC)05:53
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,681
Date (UTC)17-Aug-2010
Time (UTC)07:27
PlatformNot applicable

Article ID: 2360872 - Last Review: 10/14/2010 05:56:00 - Revision: 2.0

  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Foundation
  • kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2360872