Case of unexplained LDAP requests - ZineTek
Upcoming change - Microsoft to disable use of unsigned LDAP port 389 - msandbu.org
Blocking the UDP connection to port 389 through the firewall | INTROSERV
Clear
Port Query Error / Incorrect Results? - Microsoft Q&A
Active Directory Ports Used Client to Server - Active Directory Pro
SSL/TLS on port 389. Say what? - SANS Internet Storm Center
Linux on Active Directory – The World According to Mitch
Securing your Windows Server against LDAP-service … | TransIP
Microsoft Entra Connect: What is the ADConnectivityTool PowerShell Module - Microsoft Entra ID | Microsoft Learn
PortQry and PortQryUI – rakhesh.com
Blocking the UDP connection to port 389 through the firewall | INTROSERV
Blocking the UDP connection to port 389 through the firewall | INTROSERV
domain controller firewall ports – Dimitri's Wanderings
Active Directory Ports Used Client to Server - Active Directory Pro
LDAP Port 389 vs 636
Is port 389 on AD in anyway used or required when a new client queries via secure LDAP? - Microsoft Q&A
Old Protocols, New Exploits: LDAP Unwittingly Serves DDoS Amplification Attacks
LDAP authentication process
Blocking the UDP connection to port 389 through the firewall | INTROSERV
Network Ports | TCP & UDP Well-Known Port Numbers ⋆ IpCisco
Active Directory Ports Used Client to Server - Active Directory Pro
