Windows 2019, Windows 2022 by default has got port available from 49152 to 65535 - available 16384 ports. On another server I've got the same issue - no connection to domain controller or to different server, connections reamains intact, I can connect to server remotely - by C$ or by some ports, on server I can't establish new rdp connection with message that there are no available domain controllers, gpupdate is not working, zabbix monitoring is not working, but... after change of available ports by expanding range to 32768-65535 magically everything start works.
netsh intreface ipv4 tcp set dynamicportrange
Pokazywanie postów oznaczonych etykietą communication. Pokaż wszystkie posty
Pokazywanie postów oznaczonych etykietą communication. Pokaż wszystkie posty
2018-10-30
ports required between client and domain controller
Between client and domain controller (is always initiated from client side):
- Kerberos - 88 TCP/UDP
- RPC mapper - 135 TCP
- NetBIOS - nothing - it is not required since 2000!
- SMB/NetBT - 445 TCP/UDP
- Kerberos Password Change - 464 TCP/UDP
- LDAP - 389 TCP/UDP
- LDAP SSL - 636 TCP
- LDAP GC - 3268 TCP
- LDAP SSL GC - 3269 TCP
- DNS - 53 TCP/UDP
- RPC ports - 49152-65535 since Vista/2008, for older clients (legacy? I hate this word) 1025-5000
- (optional) DHCP - 67 DHCP
Subskrybuj:
Posty (Atom)