On a Windows Vista-based computer, the netsh firewall command together with the profile=all parameter does not configure the public profile. For example, the following command opens local port 80 to TCP traffic for the domain profile and for the private profile. But the following command does not open the public profile:

netsh firewall add portopening protocol=TCP port=80 name=”Web Port” profile=all

The Windows Firewall Control Panel program only displays settings for the currently active profile. Therefore, if you run this command, and you then open the Windows Firewall Control Panel program when the public profile is active, you receive the following exception:

“Web Port” was not created for the public profile.

Note: This is expected behavior.

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:

“Web Port” was created.