If you open the Windows Firewall Control Panel program when the domain profile or the private profile is active, you will receive the following exception:
Profiles in versions earlier than Windows VistaIn versions of Windows that are earlier than Windows Vista, Windows Firewall supported the following two profiles:
- The domain profile: This profile applies when all interfaces on the computer are connected to the domain of which it is a member.
- The standard profile: This profile applies the rest of the time.
Profiles in Windows VistaIn Windows Vista, profile support has been extended to include the following three profiles:
- The domain profile: The domain profile applies when all interfaces are connected to domain locations. A network is automatically considered as a domain network location type when the network is authenticated to the domain of which it is a member.
- The private profile: The private profile applies when at least one interface is connected to a private network location, and any additional interfaces are connected to either private or domain locations. A local administrator can classify a non-domain network as private. The private network location type is intended for use in the home or in the small office when it is connected behind an edge device such a router.
- The public profile: The public profile applies when an interface is connected to a public network location. Any network is considered a public network when the network is not connected to the domain, and a local administrator has not specified the network as private. The public network location is intended for use in locations such as airports or coffee shops.
When you specify the profile=current parameter, the exception for the public profile is created if the current profile is the public profile. This is not the case when you specify the profile=all parameter. This behavior is intended to maintain application compatibility. For example, when the public profile is the active profile at the time that the command is run, the following command opens local port 80 to TCP traffic for the public profile:
ID do Artigo: 947213 - Última Revisão: 22/10/2008 - Revisão: 1