You receive more DHCP logs on a DHCP server than expected after you create a virtual network on a computer that is running Windows Server 2008 R2

Consider the following scenario:

• You install a Hyper-V virtual machine guest operating system on a computer that is running Windows Server 2008 R2.
• You create a virtual network.
• The VMSwitch component of the virtual network is attached to a physical network adapter that has IPv4/IPv6 binding enabled.
• You configure both virtual and physical network adapters to use dynamic address allocation.�
• A dynamic host configuration protocol (DHCP) server is deployed�to assign IP addresses.�

In this scenario, the computer sends many DHCP requests to the DHCP server. Therefore, you receive�more DHCP logs on the DHCP server than expected.

This issue occurs because the virtual network adapter has the same MAC address as the physical network adapter. Therefore, the DHCP server assigns the same IP address to both network adapters. Additionally, the IP stack on the Hyper-V server rejects duplicate IP addresses. Therefore, the computer�sends DHCP requests continuously.�

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.

Notes

• To resolve this issue, install the update on the Hyper-V server.
• After you install the update, the invalid configuration that binds the IPv4/IPv6 protocol on the physical network adapter is blocked.
  

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 Service Pack 1 (SP1).� For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Registry information

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

Restart requirement

You do not have to restart the computer after you apply this update.

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 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.1.760 1.22xxx	Windows Server 2008 R2	SP1	LDR

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

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:

Additional file information

Additional file information for Windows Server 2008 R2

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