In the Windows Vista and Windows XP SP2 Firewall, what is scope and how do I use it?
Windows Vista and Windows XP (Service Pack 2) have a built-in network firewall feature. Windows Firewall works by preventing applications on your computer from communicating with other computers. By default, the firewall is set to either block or allow traffic to each program, with no additional settings. However, you can allow a program to communicate with only some computers; defining the range of allowed computers is called setting the scope of the firewall.
When the Windows Firewall is on, by default it blocks communication until told to unblock it for a specific program. Such unblocked programs go into a list of exceptions in the Windows Firewall settings.
On this page:
Windows Vista
- From the
Startmenu, selectControl Panel.
- Double-click
Security Center, and then clickWindows Firewallon the left. Again on the left, clickAllow a program through Windows Firewall. If you aren't logged in with administrative rights, you will be prompted to do so.
- Select the program for which you wish to allow only limited
network communication, and click
Properties.
- In the
Edit a Programwindow, chooseChange scope....
- Choose the scope options which best suit the application.
- Click
OKto close each of the three open windows.
Windows XP
- From the
Startmenu, selectControl Panel, orSettingsand thenControl Panel.
- Double-click
Network Connections.
- Right-click the icon for your Internet connection (probably
Local Area Connection).
- Select the
Advancedtab.
- On the right side of the box labeled "Windows Firewall", choose
Settings....
- On the
Generaltab, ensure thatDon't allow exceptionsis not checked.
- Select the
Exceptionstab.
- Select the program for which you wish to allow only limited
network communication, and click
Edit....
- In the
Edit a Programwindow, chooseChange scope....
- Choose the scope options which best suit the application.
- Click
OKto close each of the four open windows.
More information
To customize your firewall effectively, select the most limited scope options possible without hindering the functionality of the application. In other words, you want to block communication only with computers that the application never needs to legitimately interact with, and you want to do so with as many such computers as possible.
For example, if you wanted to secure the Remote Desktop application,
and you connect to your computer only from one other computer for
which you know the IP address, you would set the scope
option to Custom list, and then enter the IP address of the
single computer from which you want to be able to access this
computer. After you click OK through all of the remaining
windows, Windows will ignore Remote Desktop requests from any IP
address other than the one you specified.
Rather than a specific IP address, you can specify a subnet, a list of
IP addresses or subnets, or both. For example, if you wanted to allow
communication with all computers on the Indiana University campus, you
could choose Custom list and enter:
Although that range is not perfect, it should allow interaction with almost every IU computer while blocking access from any non-IU computer.
For more tips on securing your Windows XP computer, including images of the dialog windows discussed in this document, visit the Microsoft knowledge base article "How to Configure Windows XP SP2 Network Protection Technologies on a Single Computer" at:
http://www.microsoft.com/technet/security/smallbusiness/prodtech/windowsxp/protsing.mspxAlso see:
- In Windows XP, how do I configure the firewall to allow pings?
- In Windows XP, how do I configure the firewall to allow UISO vulnerability scanning?
- At IU, after installing Windows XP SP2, how do I configure the Windows Firewall to allow Symantec AntiVirus to be controlled through the Symantec System Center?
Last modified on April 09, 2008.






