The DHCP traffic is blocked after you enable the "Do not allow exception" and "Prohibit unicast response to multicast or broadcast requests" Windows Firewall settings in Windows 7 or in Windows Server 2008 R2

Applies to: Windows 7Windows Server 2008 R2

Symptoms


Consider the following scenario:
  • You have a computer that is running Windows Server 2008 R2 or Windows 7.
  • You enable the following Windows Firewall settings by using Group Policy settings or some netsh commands:
    Windows Firewall: Do not allow exception

    Windows Firewall: Prohibit unicast response to multicast or broadcast requests
  • You request an IP address from a DHCP server.
In this scenario, you cannot obtain an IP address from the DHCP server.

If you run the ipconfig /renew command, you receive the following error message:
An error occured while renewing interface name : unable to contact your DHCP server. Request has timed out
  • If at least one of these two Windows Firewall settings is disabled, you can obtain an IP address from the DHCP server.
  • If both of these two Windows Firewall settings are enabled, DHCP traffic is strictly blocked.

Cause


This issue occurs because the DHCP traffic is incorrectly blocked.

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

To apply this hotfix, you must be running Windows 7 or Windows Server 2008 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.

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 7 and 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 and for Windows 7" section. MUM and 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 x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Firewallapi.dll6.1.7600.16385462,84814-Jul-200901:15x86
Firewallapi.mofNot applicable1,91310-Jun-200921:29Not applicable
Icfupgd.dll6.1.7600.1638589,08814-Jul-200901:15x86
Mpsdrv.mofNot applicable1,08810-Jun-200921:28Not applicable
Mpsdrv.sys6.1.7600.1638560,41613-Jul-200923:52x86
Mpssvc.dll6.1.7600.20793566,27203-Sep-201004:37x86
Mpssvc.mofNot applicable1,90010-Jun-200921:29Not applicable
Wfapigp.dll6.1.7600.1638518,94414-Jul-200901:16x86
Wfapigp.mofNot applicable1,08310-Jun-200921:29Not applicable
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Firewallapi.dll6.1.7600.16385748,03214-Jul-200901:40x64
Firewallapi.mofNot applicable1,91310-Jun-200920:47Not applicable
Icfupgd.dll6.1.7600.16385108,54414-Jul-200901:41x64
Mpsdrv.mofNot applicable1,08810-Jun-200920:46Not applicable
Mpsdrv.sys6.1.7600.1638577,31214-Jul-200900:08x64
Mpssvc.dll6.1.7600.20793826,36803-Sep-201005:23x64
Mpssvc.mofNot applicable1,90010-Jun-200920:47Not applicable
Wfapigp.dll6.1.7600.1638522,52814-Jul-200901:41x64
Wfapigp.mofNot applicable1,08310-Jun-200920:47Not applicable
Firewallapi.dll6.1.7600.20793462,84803-Sep-201004:36x86
Firewallapi.mofNot applicable1,91322-Jul-200923:13Not applicable
Mpsdrv.mofNot applicable1,08822-Jul-200923:12Not applicable
Mpssvc.mofNot applicable1,90022-Jul-200923:13Not applicable
Wfapigp.dll6.1.7600.2079318,94403-Sep-201004:40x86
Wfapigp.mofNot applicable1,08322-Jul-200923:14Not applicable
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.16385482,89614-Jul-200901:58IA-64
Tcpip.sys6.1.7600.207843,778,43219-Aug-201006:19IA-64

Status


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

More Information


How to enable the Windows Firewall settings that are related to this issue

Method 1: Use some "netsh" commands

Run the following netsh commands to enable the Windows Firewall settings that are described in the "Symptoms" section:
netsh advfirewall set currentprofile settings unicastresponsetomulticast disable

netsh advfirewall set currentprofile firewallpolicy blockinboundalways,allowoutbound

Method 2: Use Group Policy settings

To use Group Policy settings to enable the Windows Firewall settings that are described in the "Symptoms" section, follow these steps:
  1. Locate the following item:
    Computer Configuration\Administrative Templates\Network\Network Connections\Windows Firewall\Standard Profile or domain profile if you are in a domain
  2. Double-click the Windows Firewall: Do not allow exceptions setting to enable the setting.
  3. Double-click the Windows Firewall: Prohibit unicast response to multicast or broadcast requests setting to enable the setting.
  4. Apply these Group Policy settings to a computer that is running Windows Server 2008 R2 or Windows 7.
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 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot applicable
File size1,880
Date (UTC)03-Sep-2010
Time (UTC)17:44
PlatformNot applicable

File nameX86_9e5535d519009cec06d72b3be6f57aae_31bf3856ad364e35_6.1.7600.20793_none_574199be1dec9bf9.manifest
File versionNot applicable
File size691
Date (UTC)03-Sep-2010
Time (UTC)17:44
PlatformNot applicable

File nameX86_networking-mpssvc-svc_31bf3856ad364e35_6.1.7600.20793_none_9a6763994257d38c.manifest
File versionNot applicable
File size236,940
Date (UTC)03-Sep-2010
Time (UTC)17:51
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_82d76101c29975e1f04067b179cf9e1f_31bf3856ad364e35_6.1.7600.20793_none_4c35dc53875033c4.manifest
File versionNot applicable
File size1,032
Date (UTC)03-Sep-2010
Time (UTC)17:44
PlatformNot applicable

File nameAmd64_e5ce7a59dbaeba566203109456a95891_31bf3856ad364e35_6.1.7600.20793_none_cffe727c12dc40ab.manifest
File versionNot applicable
File size695
Date (UTC)03-Sep-2010
Time (UTC)17:44
PlatformNot applicable

File nameAmd64_networking-mpssvc-svc_31bf3856ad364e35_6.1.7600.20793_none_f685ff1cfab544c2.manifest
File versionNot applicable
File size236,946
Date (UTC)03-Sep-2010
Time (UTC)17:53
PlatformNot applicable

File nameUpdate.mum
File versionNot applicable
File size2,114
Date (UTC)03-Sep-2010
Time (UTC)17:44
PlatformNot applicable

File nameWow64_networking-mpssvc-svc_31bf3856ad364e35_6.1.7600.20793_none_00daa96f2f1606bd.manifest
File versionNot applicable
File size76,903
Date (UTC)03-Sep-2010
Time (UTC)05:03
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_0bd415bdb7c5b6369a58b22418214952_31bf3856ad364e35_6.1.7600.20784_none_47a83f5dfb78ac9f.manifest
File versionNot applicable
File size704
Date (UTC)20-Aug-2010
Time (UTC)01:58
PlatformNot applicable

File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20784_none_b37eae9ee0d65d4b.manifest
File versionNot applicable
File size3,782
Date (UTC)20-Aug-2010
Time (UTC)01:58
PlatformNot applicable

File nameUpdate.mum
File versionNot applicable
File size1,684
Date (UTC)20-Aug-2010
Time (UTC)01:58
PlatformNot applicable