Domain Controller Join Ports
An active directory domain controller needs to listen on specific ports to service different client requests.
Domain controller join ports. For example when a client computer needs to authenticate it connects to a server which hosts kdc service and which is listening on the port 88. Tcp and udp port 445 for file replication service. Tcp and udp port 53 dns from client to domain controller and domain controller to domain controller.
Udp and tcp port 135 for domain controllers to domain controller and client to domain controller operations. However via experience i. For more information about the dynamic port range change in windows server 2012 and windows server 2012 r2 see.
For more information about how to customize this port see domain controllers and active directory in the references section. Tcp port 139 and udp 138 for file replication service between domain controllers. Tcp port 5722 dfsr rpc sysvol replication between domain controllers.
Tcp port 3268 and 3269 global catalog from client to domain controller. The following message appear even join to domain successfully and there is a lot of tcp high ports are blocked in firewall. Active directory communication takes place using several ports.
It take very long time to for computer to startup and login to domain successfully. As an example when a client computer tries to find a domain controller it always sends a dns query over port 53 to find the name of the domain controller in the domain. Tcp and udp port 389 for ldap to handle normal queries from client computers to the domain controllers.
This differs from a mixed mode domain that consists of windows server 2003 domain controllers windows 2000 server based domain controllers or legacy clients where the default dynamic port range is 1025 through 5000. Required ports to communicate with domain controller this article discusses the required network ports protocols and services that are used by microsoft client and server operating systems server based programs and their subcomponents in the microsoft windows server system. This section also includes remote wmi and dcom communications first used in windows server 2012 domain controller promotion during prerequisite validation and with the server manager tool.