This article describes an issue in which a computer does not obtain IP address from a DHCP failover that is running Windows Server 2012 R2. A hotfix is available to resolve this issue. Before you install this hotfix, check out the Prerequisites section.

Symptoms

Assume that a client computer sends a Dynamic Host Configuration Protocol (DHCP) request to renew the IP address on a DHCP server, and the DHCP server has the Network Access Protection (NAP) feature enabled. In this situation, the client computer cannot extend the IP address lease period. 

Resolution

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 this specific problem.

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, submit a request to 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:

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

To apply this update, you must have update 2919355 installed in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may 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 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 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 8.1/Windows Server 2012 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, 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.3.960 0.17 xxx

    Windows Server 2012 R2

    RTM

    GDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" 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 R2

File name

File version

File size

Date

Time

Platform

Dhcpcore.dll

6.3.9600.17673

363,520

04-Feb-2015

03:23

x64

Dhcpcore6.dll

6.3.9600.17415

269,312

29-Oct-2014

01:28

x64

Dhcpcsvc.dll

6.3.9600.17415

89,088

29-Oct-2014

01:28

x64

Dhcpcsvc6.dll

6.3.9600.17415

66,048

29-Oct-2014

01:29

x64

Dhcpcore.dll

6.3.9600.17673

292,352

03-Feb-2015

23:25

x86

Dhcpcore6.dll

6.3.9600.17415

228,864

29-Oct-2014

01:05

x86

Dhcpcsvc.dll

6.3.9600.17415

64,512

29-Oct-2014

01:05

x86

Dhcpcsvc6.dll

6.3.9600.17415

57,344

29-Oct-2014

01:06

x86

Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2

File property

Value

File name

Amd64_2e9555f81e54e274b06add1b470eb241_31bf3856ad364e35_6.3.9600.17673_none_61e41cc222fac88c.manifest

File version

Not applicable

File size

714

Date (UTC)

05-Feb-2015

Time (UTC)

20:21

Platform

Not applicable

File name

Amd64_773cdd48554689bd2a5a74b3b10149d9_31bf3856ad364e35_6.3.9600.17673_none_3afecb4711940a27.manifest

File version

Not applicable

File size

712

Date (UTC)

05-Feb-2015

Time (UTC)

20:21

Platform

Not applicable

File name

Amd64_microsoft-windows-dhcp-client-dll-minwin_31bf3856ad364e35_6.3.9600.17673_none_5dbcd0252cfa9a61.manifest

File version

Not applicable

File size

24,773

Date (UTC)

05-Feb-2015

Time (UTC)

20:28

Platform

Not applicable

File name

X86_microsoft-windows-dhcp-client-dll-minwin_31bf3856ad364e35_6.3.9600.17673_none_019e34a1749d292b.manifest

File version

Not applicable

File size

24,765

Date (UTC)

05-Feb-2015

Time (UTC)

20:28

Platform

Not applicable



Status

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

References

See the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×