Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A Windows Vista-based or Windows Server 2008-based computer that is connected to a domain uses the public profile or the private profile for the Windows Firewall policy instead of the domain profile


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Windows Vista-based or a Windows Server 2008-based computer that is connected to a domain.
  • The computer uses two or more network adapters.
You expect the domain profile to be used for the Windows Firewall profile. However, in this scenario, the public profile or the private profile is used instead.

Windows Firewall policy includes rules for remote assistance, for remote administration, for file-and-print sharing, and so on. Therefore, if you rely on these rules to access a client remotely, you cannot access the client when the public profile or the private profile is used.

↑ Back to the top


Cause

This behavior occurs if one or more of the network adapters cannot contact a domain controller. This behavior is intended to enforce more restrictive firewall settings over less secure connections, depending on the network location type. Only one firewall profile may be active on the computer at the same time.

↑ Back to the top


More information

To determine which firewall profile is currently being used, click Start, type wf.msc in the Start Search box, and then click wf.msc in the Programs list. The active profile is indicated in the Overview section in the "Windows Firewall with Advanced Security" Microsoft Management Console (MMC).

For more information, visit the following Microsoft Web site: You can set firewall rules in a Group Policy object (GPO) by using Windows Firewall together with the Advanced Security node in the Group Policy Management Console (GPMC) that is available in Windows Server 2008 or in Windows Vista. In GPMC, you can create different firewall rule sets for each of the following network location profiles or for a combination of them:
  • Domain
  • Private
  • Public
Note These rules apply only to computers that are running Windows Server 2008 or Windows Vista. These rules do not apply to computers that are running earlier versions of Windows, such as Windows Server 2003 or Windows XP with Service Pack 2.

If you set the rules in a GPO by using the Windows Firewall node in the Administrative Templates section of Group Policy Object Editor, you can create rules only for the Domain and Standard profiles. If this GPO is applied to Windows Vista or to Windows Server 2008, the rules in the Standard profile apply whenever the computer�s network location profile is set to Private or Public. The rules in the Domain profile still apply only when the computer�s network location profile is set to Domain.

We recommend that you create separate GPOs to deliver firewall or connection security rules to your computers. Use one GPO for computers that are running Windows Vista or Windows Server 2008. In this GPO, create the rules by using Windows Firewall together with the Advanced Security node. Use a different GPO for computers that are running earlier versions of Windows. In this GPO, create the rules by using the Windows Firewall node in the Administrative Templates section. Use group filtering or Windows Management Instrumentation (WMI) filtering to make sure that the policies apply only to computers that are running the appropriate operating system.

↑ Back to the top


Keywords: kbinfo, kbexpertiseinter, kbtshoot, KB938756

↑ Back to the top

Article Info
Article ID : 938756
Revision : 3
Created on : 7/9/2009
Published on : 7/9/2009
Exists online : False
Views : 405