Information Technology Reference
In-Depth Information
Additionally, you needed to enable access to TCP port 135.
On Windows Server 2003 computers with Service Pack 1 installed, you simply need to
verify that the preconfigured Allow Remote Desktop Exception setting has been enabled
through the Windows Firewall Control Panel applet, the Registry, or Group Policy. As with
other Windows Firewall exceptions, you should restrict the scope of the remote assistance
exception to protect your systems against attacks targeted at the well-known RPC port, TCP 135.
See Also
￿
Recipes 4-4, 4-5, and 4-11 for more on configuring the remote assistance exception
￿
Microsoft TechNet: “Configuring System Service Exceptions”
( http://technet2.microsoft.com/WindowsServer/en/Library/
9a29df7b-235a-42fd-9c25-13f6be94ad9a1033.mspx )
9-17. Troubleshooting Active Directory Replication
Problem
You want to troubleshoot Active Directory replication on a Windows Server 2003 computer.
Solution
Using a Graphical User Interface
To select one or more Active Directory domain controllers to view, do the following:
1.
Open the Replmon Support Tools utility.
2.
Right-click on the Monitored Servers node in the left pane, and select Add Monitored
Server.
3.
Select the Add the Server Explicitly by Name radio button, and click Next. Enter the
Fully Qualified Domain Name (FQDN) of the server that you wish to monitor.
4.
To specify a different set of credentials, place a check mark next to Use Alternate
Credentials, and click Change. Enter an administrative username in the format
DomainName \ UserName in the Username text box. Enter the password in the
Password text box, and click OK.
5.
Click Finish.
6.
Repeat steps 2-5 for any additional servers that you wish to monitor.
7.
To view your current replication topology, right-click on a domain controller in the left
pane and select Show Replication Topologies.
Search WWH ::




Custom Search