Domain Controller Replication Ports

Both udp and tcp port 135 are required for communication between domain controllers and clients to domain controllers.

Domain controller replication ports. Tcp and udp port 445 for file replication service. Udp port 389 for ldap to handle normal queries from client computers to the domain controllers. Often sought on the internet rarely complete here is for a domain controller firewall ports to open so your windows domain controller is able to contact the other domain controllers it is depending on for proper replication.

It displays inbound replication requests that the domain controller needs to issue to become consistent with its source replication partners. Tcp port 139 and udp 138 file replication service between domain controllers. Port 445 is used by dfsr only when creating a new empty replicated folder.

Tcp port 139 and udp 138 for file replication service between domain controllers. The third command is repadmin showrepl displays the replication status when the specified domain controller last attempted to implement inbound replication of active directory partitions. This is applicable for restriction ad replication to a specific port range.

Frequently you must also manually set the file replication service frs rpc port because ad and frs replication replicate with the same domain controllers. Tcp port 139 and udp 138 network ports are used by the sysvol replication service to replicate contents of sysvol folder. Port 5722 is only used on a windows server 2008 domain controller or a windows server 2008 r2 domain controller.

Udp port 389 ldap to handle normal queries from client computers to the domain controllers. Verification that fixed ports are working. This is to used to set the specific ad replication port.

Modify registry to select a static port. It is not used on a windows server 2012 domain controller. The frs rpc port should use a different port.