Domain Controller Ports Needed
Examples are windows nt based operating systems or third party domain controllers that are based on samba.
Domain controller ports needed. Tcp port 3268 and 3269 for global catalog from client to domain controller. Both udp and tcp port 135 are required for communication between domain controllers and clients to domain controllers. Netbios ports as listed for windows nt are also required for windows 2000 and server 2003 when trusts to domains are configured that support only netbios based communication.
Additionally unless a tunneling protocol is used to encapsulate traffic to active directory a range of ephemeral tcp ports between 1024 to 5000 and 49152 to 65535 are required. Tcp port 139 and udp 138 network ports are used by the sysvol replication service to replicate contents of sysvol folder. Block access from 172 16 1 0 24 to 10 10 10 0 24.
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. Tcp and udp port 445 file replication service. Required ports to communicate with domain controller.
Tcp and udp port 135 domain controllers to domain controller and client to domain controller operations. Opening above ports in firewall between client computers and domain controllers or between domain controllers will enable active directory to function properly. Dynamic ports in windows server.
Tcp and udp port 464 kerberos password change. Administrators and support professionals may use this. Udp port 389 for ldap network port is used to handle normal authentication queries from client computers.
Udp port 389 ldap to handle normal queries from client computers to the domain controllers. Block access from 10 10 10 0 24 to 172 16 1 0 24. Windows 2019 ad domain controller 10 10 10 200.