Network and Sharing Center does not display Windows Firewall domain policies in Windows Vista or in Windows Server 2008, you cannot browse the network

Consider the following scenario:

• In the Active Directory domain environment, you create the Predefined Windows Firewall outgoing and incoming rules for File and Printer Sharing and Network Discovery.
• You select Allow the connection for the Firewall outgoing and incoming rules.
• The Firewall rules are applied to the client computer.

In this scenario, you encounter the following issues on a client computer that is running Windows Vista or Windows Server 2008:

Issue 1
In Network and Sharing Center, you see that Network discovery and File sharing are turned off.

Issue 2
When you click View computers and devices, you do not see any computers in Network Explorer. Additionally, you receive the following message in the information bar of Network Explorer:

This problem occurs because Network Explorer, and Network and Sharing Center check the local firewall policy. However, they do not check whether the domain firewall policy is configured. Even though the domain policy is configured to enable network discovery, or file sharing, Network and Sharing Center show that these settings are disabled. Therefore, Network Explorer does not let the user browse the network. This occurs because of a conflict between the local Firewall policy and the domain Firewall policy.

To resolve this problem, install the following hotfix on the client computer. This hotfix enables Network and Sharing Center, and Network Explorer to check the local Firewall policy, and the domain Firewall policy to determine whether Network discovery or File sharing is enabled.

Note The Domain policy takes effect without this hotfix. This hotfix only changes the display in Network and Sharing Center, and Network Explorer.

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 on computer that is running Windows Vista, you must have Windows Vista SP1 or Windows Vista SP2 installed.

No prerequisites are required for computers that are running Windows Server 2008.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported IA-64-based versions of Windows Server 2008

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

The Group Policy is located in the following location:

Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security

For more information about the introduction to Windows Firewall with Advanced Security, visit the following Web site:

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

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

Additional files for all supported IA-64-based versions of Windows Server 2008