Is port 389 on AD in anyway used or required when a new client queries via secure LDAP? - Microsoft Q&A
Case of unexplained LDAP requests - ZineTek
Nessus Manager - 'Failed to connect to the LDAP server: Failed to establish a TLS connection' error
How to configure Firewall on Windows server? - Heficed
Blocking the UDP connection to port 389 through the firewall | INTROSERV
Blocking the UDP connection to port 389 through the firewall | INTROSERV
Chapter 2. Setting up a new Directory Server instance Red Hat Directory Server 11 | Red Hat Customer Portal
Connecting to the Okta LDAP Interface Over Port 389 | Okta Support - YouTube
LDAP Port 389 vs 636
Query against port 389 of Microsoft Active Directory gets flummoxed by referrals · Issue #4 · proftpd/mod_ldap · GitHub
Blocking the UDP connection to port 389 through the firewall | INTROSERV
Clear
Upcoming change - Microsoft to disable use of unsigned LDAP port 389 - msandbu.org
LDAP Connection Issue - UCS - Univention Corporate Server - Univention Help
Active Directory Ports Used Client to Server - Active Directory Pro
Ldap auth failing for bind user - Support - TheForeman
Securing your Windows Server against LDAP-service … | TransIP
Active Directory Ports Used Client to Server - Active Directory Pro
Securing Client-side and Server-side LDAP Traffic
389 Directory Server - register-ds-admin.pl and Remote Servers
SSL/TLS on port 389. Say what? - SANS Internet Storm Center
How does Active Directory Synchronization works? – DeskAlerts
Settings for LDAP / LDAPS
