Symptoms
Consider the following scenario:
-
Two Dynamic Host Configuration Protocol (DHCP) servers are configured for failover.
-
DHCP Network Access Protection (NAP) is configured on both DHCP servers.
-
A client computer obtains an IP address from DHCP server 1.
-
DHCP server 1 is unavailable, and DHCP server 2 detects that DHCP server 1 is unavailable.
-
The client computer sends a rebind request.
In this scenario, the client computer cannot obtain the IP address from DHCP server 2, and an Automatic Private IP Addressing (APIPA) address is assigned to the client computer.
Resolution
To resolve this issue in Windows Server 2012 R2, install update rollup 2967917.
To resolve this issue in Windows Server 2012, install the hotfix that is described in the "Hotfix information" section.
Update information
For more information about how to obtain update rollup 2967917, click the following article number to view the article in the Microsoft Knowledge Base:
2967917 July 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote 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
There are no prerequisites for installing this hotfix.
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 2012 file information notesImportant Windows 8 hotfixes and Windows Server 2012 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 8/Windows Server 2012" 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:
Version
Product
Milestone
Service branch
6.2.920 0.21xxx
Windows Server 2012
RTM
LDR
-
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 2012" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 2012
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Dhcpserver.events.xml |
Not applicable |
600 |
06-Jul-2012 |
19:53 |
Not applicable |
|
Dhcpssvc.dll |
6.2.9200.21132 |
1,110,528 |
29-May-2014 |
00:28 |
x64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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 for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
|
File property |
Value |
|---|---|
|
File name |
Amd64_4696449c8aa52976a9b2b29a76400162_31bf3856ad364e35_6.2.9200.21132_none_c7d2caccf1da7513.manifest |
|
File version |
Not applicable |
|
File size |
709 |
|
Date (UTC) |
29-May-2014 |
|
Time (UTC) |
08:43 |
|
File name |
Amd64_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.2.9200.21132_none_829110633a461aea.manifest |
|
File version |
Not applicable |
|
File size |
284,803 |
|
Date (UTC) |
29-May-2014 |
|
Time (UTC) |
03:07 |
