Domain Login Ports

Windows 10 client can join to windows 2019 ad domain with the following ports allow in firewall tcp 88 kerberos key distribution center tcp 135 remote procedure call tcp 139 netbios session service.

Domain login ports. To answer your questions directly here are the major ports used in windows domains. This change was made to comply with internet assigned numbers authority iana recommendations. Udp port 88 for kerberos authentication udp and tcp port 135 for domain controllers to domain controller and client to domain controller operations.

Tcp 445 and udp 445. Check the network port status on a domain controller. User computer login and authentication the following protocols and ports are required.

As i am setting up a vm of windows 2003 server active domain tried for ports needed to successfully let other machines authenticate themselves to the ad server. Ad login replication tcp 389. Ms rpc tcp 1025 1026.

Microsoft ds for server message block smb over ip traffic tcp 88 and udp 88. Lightweight directory access protocol ldap ping tcp 53 and udp 53. These ports are required by both client computers and domain controllers.

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. About port scanner tool. 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.

Both dns tcp and udp 53 network ports are used by clients and domain controllers for name resolution purposes. Tcp port 139 and udp 138 for file replication service between domain controllers. Domain controllers client computers and application servers require network connectivity to active directory over specific hard coded ports.