How to restrict FRS replication traffic to a specific static port (319553)

MORE INFORMATION

FRS is a multiple-threaded, multiple-master replication engine that replaces the LANMan Directory Replication (LMRepl) service in Microsoft Windows NT versions 3.x and 4.0. Windows 2000-based domain controllers and servers use FRS to replicate system policy and logon scripts for client computers that are running Windows 2000 and earlier. Additionally, FRS can replicate content between Windows 2000-based servers that host the same fault-tolerant Distributed File System (DFS) roots or child-node replicas.

FRS Replication

By default, FRS replication over remote procedure calls (RPCs) occurs dynamically over an available port by using RPC Endpoint Mapper (also known as RPCSS) on port 135; the process is the same for Active Directory or Microsoft Exchange Server replication. You can override this default functionality and specify the port that all FRS replication traffic passes through (you can configure Active Directory in the same way). When you do so, you can limit replication to a static port. For additional informationabout how to restrict Active Directory replication traffic to a port, click the following article number to view the article in the Microsoft Knowledge Base: NOTE: Before you change the default port settings in your production environment, set up a lab to simulate FRS use and to test performance. Some administrators keep only policies and scripts in SYSVOL, but other administrators may keep large amounts of data. Because every environment is different, make sure that you make your test configuration as close as possible to the production environment.

In FRS replication, the client does not know the complete binding. Therefore, when the client connects to an RPC endpoint, the RPC run-time on the client contacts RPC Endpoint Mapper on the server at a well-known port (port 135), and obtains the port to connect to for the service that is supporting the RPC interface. The service registers the endpoint when it starts, and it has the choice of a using either a dynamically assigned port or a specific port.

You can use the following procedure to configure FRS to run on a specific port. When you do so, the port is registered with RPC Endpoint Mapper.

NOTE: This article does not describe FRS replication through a firewall. If you use a firewall, you must open a number of ports (for example, Kerberos and others) for FRS replication to work. If you must initiate FRS replication over a firewall, use virtual private networking (VPN). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

How to Restrict FRS Traffic to a Specific Static Port

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Modify the following value on each domain controller where the restricted port is to be used:

1. Start Registry Editor (Regedt32.exe).
2. Locate and then click the following key in the registry:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTFRS\Parameters

3. On the Edit menu, click Add Value, and then add the following registry value:

   Value name: RPC TCP/IP Port Assignment
   Data type: REG_DWORD
   Value data: Type an available port. This value needs to be specified in decimal format.

   NOTE: If you do not type a value, this registry setting always uses a value of zero and a dynamic TCP/IP port assignment is used.
4. Quit Registry Editor.

IMPORTANT: You must see if there is an intermediate network device or software that is being used to filter packets between domain controllers. If so, verify that the device or the software allows communication over the specified port. Additionally, make sure the destination TCP port that you set is open on the firewall.

For additional information about the post-SP2 hotfix for FRS, click the following article number to view the article in the Microsoft Knowledge Base: For additional information about RPC Endpoint Mapper, click the following article number to view the article in the Microsoft Knowledge Base: