Location-Aware Profiles The firewall can define different rules based on where
a network interface is connected. This is done through
one of three firewall profiles:
Domain Used when the server is connected to a
network where the Active Directory domain to which
the computer is a member can be accessed.
Private Used when a computer is connected to a
private network behind a private gateway or router.
You must have administrative privileges to configure a
network as Private.
Public Used when the server is connected to an
interface that is directly connected to the Internet or a
network that is neither Private nor Domain.
Authenticated Bypass Allows you to define bypass rules for authenticated
computers. For example, you can block all inbound
HTTP traffic but allow an authenticated computer to
bypass this restriction.
Active Directory user,
computer, and group
integration
If the server is a member of an Active Directory domain,
you can define rules around user and computer accounts
as well as security groups. This requires authentication to
be secured using IPSec with a protocol such as Kerberos
version 5.
IPv6 support Overall, Windows Server 2008 supports IPv6, so
it makes sense to extend the Windows Firewall to
support IPv6.
80 Microsoft Windows Server 2008 Administration
With all these options for defining rules around the Windows Firewall, some defined
order must allow them to be evaluated so that it is clear which rules take precedence
over other rules.
Pages:
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120