|
|
|
Maxabout.com > Tips
Working With The Advanced Firewall SettingsAdded on:10/2/2008 1:56:12 AM
In Windows Vista Tips Rated by 1 users
To work with the advanced settings found in the Windows Firewall, begin by opening your Administrative Tools and selecting Windows Firewall with Advanced Security.
The left pane enables you to view and create connection security rules. The Actions pane on the right gives you context-sensitive options. If you scroll down the Overview pane, you will see a link labeled Windows Firewall Properties. Selecting this link opens the Windows Firewall with Advanced Security on Local Computer dialog box. This dialog box has four tabs, one for each profile (Domain, Private, and Public) and one for IPSec configurations.
Each of the profiles has the same types of settings, which makes learning what they do much easier for you. Here are the settings you can configure:
Firewall State—Turns the firewall on or off for the profile tab you are configuring.
Inbound Connections—Establishes one of three rules for your inbound connections. The Block (default) rule blocks connections that do not match any active rules. The Block All Connections rule ignores the rules and blocks everything. The Allow rule allows connections regardless of the firewall rules.
Outbound Connections—You can choose to Allow or Block connections that do not match the firewall rules.
Settings—Selecting the Customize button brings you to another dialog box with the following options:
Display notifications to the user when a program is blocked from receiving inbound communications
Allow unicast response to multicast or broadcast network traffic
Apply local firewall rules (applies only when working with Group Policy)
Apply local connection security rules (applies only when working with Group Policy)
Logging—Selecting the Customize button allows you to determine the location (the default is %windir%/pfirewall.log), the size of the log (the default is 4096KB), whether dropped packets should be logged (the default is no), or whether successful connections should be logged (the default is no).
|
|
|