TIP Since the Windows Firewall is enabled on all interfaces on all profiles by default, simply enabling
Terminal Services in Remote Administration mode won??™t allow you to control the server remotely using
Remote Desktop Protocol (RDP). The right way is to explicitly open the Terminal Services port on the
server. This can be achieved by adding a firewall rule to allow inbound TCP connections to port 3389
through netsh:
Netsh advfirewall firewall add rule name="TS Admin" protocol=TCP
dir=in localport=3389 action=allow
Configure the Windows Firewall
The Windows Firewall is a host-based, bidirectional network traffic filter. Unlike the initial
incarnation of the Windows Firewall that debuted in Windows XP SP2 and filtered
only inbound traffic, the new Windows Firewall can control both inbound and outbound
traffic. The current Windows Firewall is also network-aware, in that you can define policies
depending on whether the server is on the network where it can authenticate to the
domain, on a public network that is directly attached to the Internet, or on a private network
explicitly defined. For example, you can configure policies to allow file and print
sharing when in a domain network and then block it if on a public network.
37 Chapter 2: Server Core
Configuring the firewall involves either working with the Netsh command at the
command prompt or using the Windows Firewall with Advanced Security MMC snapin
from a remote Windows Server 2008 server.
Pages:
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76