Ldaps Port

https://techcommunity.microsoft.com/t5/sql-server...
By Default LDAP Port is 389 and LDAPS port is 636 let us choose the default values click Next Create a new Application Directory Partition named CN MRS DC CONTOSO DC COM Click Next Using the default values for storage location of ADLDS files Click Next Choosing Network Service Account for running the

https://serverfault.com/questions/682594
You should use TCP ports 389 and or 636 Port 636 is for LDAPS which is LDAP over SSL Encryption on port 389 is also possible using the STARTTLS mechanism but in that case you should explicitly verify that encryption is being done Microsoft s KB article says Start TLS extended request LDAPS communication occurs over port TCP

https://learn.microsoft.com/en-us/troubleshoot/...
LDAPS communication occurs over port TCP 636 LDAPS communication to a global catalog server occurs over TCP 3269 When connecting to ports 636 or 3269 SSL TLS is negotiated before any LDAP traffic is exchanged Multiple SSL certificates

https://blog.purestorage.com/purely-informational/...
The default port allocated for LDAPS is the encrypted port 636 but administrators can use the alternative unencrypted port 389 for cleartext queries What Is LDAPS Lightweight directory access protocol over SSL LDAPS is a vendor neutral method for connecting computers and network resources

https://access.redhat.com/.../changing_the_ldap_and_ldaps_port_numbers
Changing the LDAP and LDAPS Port Numbers By default Directory Server uses port 389 for the LDAP and if enabled port 636 for the LDAPS protocol You can change these port numbers for example to run multiple Directory Server instances on one host

https://learn.microsoft.com/en-us/troubleshoot/...
Step 1 Verify the Server Authentication certificate Step 2 Verify the Client Authentication certificate Step 3 Check for multiple SSL certificates Step 4 Verify the LDAPS connection on the server Step 5 Enable Schannel logging This article discusses steps about how to troubleshoot LDAP over SSL LDAPS connection problems

https://access.redhat.com/documentation/en-us/red...
15 1 Changing the port numbers using the command line You can change the port numbers of the LDAP and LDAPS protocol using the command line LDAP and LDAPs port change requires update of the nsslapd port and nsslapd securePort parameters Procedure Optionally Display the current port numbers for the instance

https://directory.apache.org/api/user-guide/5.1-ldaps.html
LDAP supports SSL it s called LDAPS and it uses a dedicated port As of today and since 2000 LDAPS is deprecated and StartTLS should be used

https://techcommunity.microsoft.com/t5/core...
LDAPS is best used to protect credentials during a simple LDAP bind This is when a user name and password could be exposed MMC snap ins use sign and seal There is no way to make clients prefer LDAPS because the type of connection depends on the application that is running on the client computer