IP addresses become APIPA when DHCP failover server running Windows Server 2012 or Windows Server 2012 R2 is unavailable

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 EssentialsWindows Server 2012 R2 Foundation

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: 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

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.

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