Known Issues for Managing Windows Firewall Notifications

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Review the following known issues before you manage Windows Firewall notifications.

  • Windows Firewall does not display notifications if you select the Don't allow exceptions check box in Windows Firewall in Control Panel, or if you enable the Do not allow exceptions policy setting in Group Policy, or if you use the netsh firewall set opmode exceptions = disable command. There are no Windows Firewall settings that allow you to override this behavior.

  • Windows Firewall does not display notifications for programs that rely on the Winsock driver to dynamically bind to a UDP port. If a program uses this method (sometimes referred to as wildcard binds) to bind to a UDP port, you might be able to use the netstat command and other troubleshooting tools to determine which UDP port is being used, and then add that port to the exceptions list.

  • Windows Firewall does not display a notification when a system service attempts to listen for incoming traffic on a port and the incoming traffic is blocked. This is also true for any program that runs like a system service (that is, a program that runs under an account that has higher privilege than a user account, for example, the Local System account, or a program that runs even when there is no user logged on to the computer).