Список портов, необходимых для корректной работы к контроллером домена
DC to DC and DC to client communications Require Numerous ports
There’s no secret to this. That’s the simplest I can put it.
And, the list of ports required is long, to the dismay of network infrastructure engineering teams that must bequest ports to allow AD to communicate, replicate, etc., these ports must be opened. There really isn’t much that can be done otherwise.
Here’s the list with an explanation of each port:
|Protocol and Port||AD and AD DS Usage||Type of traffic|
|TCP 42||If using WINS in a domain trust scenario offering NetBIOS resolution||WINS|
|TCP 135||Replication||RPC, EPM|
|TCP 137||NetBIOS Name resolution||NetBIOS Name resolution|
|TCP 139||User and Computer Authentication, Replication||DFSN, NetBIOS Session Service, NetLogon|
|TCP and UDP 389||Directory, Replication, User and Computer Authentication, Group Policy, Trusts||LDAP|
|TCP 636||Directory, Replication, User and Computer Authentication, Group Policy, Trusts||LDAP SSL|
|TCP 3268||Directory, Replication, User and Computer Authentication, Group Policy, Trusts||LDAP GC|
|TCP 3269||Directory, Replication, User and Computer Authentication, Group Policy, Trusts||LDAP GC SSL|
|TCP and UDP 88||User and Computer Authentication, Forest Level Trusts||Kerberos|
|TCP and UDP 53||User and Computer Authentication, Name Resolution, Trusts||DNS|
|TCP and UDP 445||Replication, User and Computer Authentication, Group Policy, Trusts||SMB, CIFS, SMB2, DFSN, LSARPC, NbtSS, NetLogonR, SamR, SrvSvc|
|TCP 9389||AD DS Web Services||SOAP|
|TCP 5722||File Replication||RPC, DFSR (SYSVOL)|
|TCP and UDP 464||Replication, User and Computer Authentication, Trusts||Kerberos change/set password|
|UDP 123||Windows Time, Trusts||Windows Time|
|UDP 137||User and Computer Authentication||NetLogon, NetBIOS Name Resolution|
|UDP 138||DFS, Group Policy, NetBIOS Netlogon, Browsing||DFSN, NetLogon, NetBIOS Datagram Service|
|UDP 67 and UDP 2535||DHCP (Note: DHCP is not a core AD DS service but these ports may be necessary for other functions besides DHCP, such as WDS)||DHCP, MADCAP, PXE|
And We Must Never Forget the Ephemeral Ports!!
And most of all, the Ephemeral ports, or also known as the “service response ports,” that are required for communications. These ports are dynamically created for session responses for each client that establishes a session, (no matter what the ‘client’ may be), and not only to Windows, but to Linux and Unix as well.
See below in the references section to find out more on what ‘ephemeral’ means.are used only for that session. Once the session has dissolved, the ports are put back into the pool for reuse. This applies not only to Windows, but to Linux, Unix and other operating systems, as well. See below in the references section to find out more on what ‘ephemeral’ means.
The following chart shows what the ephemeral ports are depending on the OS version, and what they are used for.
|Window 2003, Windows XP, and Windows 2000||TCP & UDP||1024-5000||Ephemeral Dynamic Service Response Ports|
|Windows 2008/Vista and newer||TCP & UDP 49152-65535||Ephemeral Dynamic Service Response Ports|
|TCP Dynamic Ephemeral||Replication, User and Computer Authentication, Group Policy, Trusts||RPC, DCOM, EPM, DRSUAPI, NetLogonR, SamR, FRS|
|UDP Dynamic Ephemeral||Group Policy||DCOM, RPC, EPM|
If the scenario is a Mixed-Mode NT4 & Active Directory scenario with NT4 BDCs, then the following must be opened:
|TCP & UDP 1024 – 65535||NT4 BDC to Windows 2000 or newer Domain controller PDC-E communications||RPC, LSA RPC, LDAP, LDAP SSL, LDAP GC, LDAP GC SSL, DNS, Kerberos, SMB|
See, wasn’t that simple?
The Short list without port explanations:
|TCP and UDP||389|
|TCP and UDP||88|
|TCP and UDP||53|
|TCP and UDP||445|
|TCP and UDP||464|
|TCP & UDP||1024-5000|
|TCP & UDP||49152-65535|
If the scenario is a Mixed-Mode NT4 & Active Directory scenario with NT4 BDC:
The following Ephemeral ports must be opened (yes, it’s pretty much the whole range):
|TCP & UDP||1024-65535|