When the certificate for an Active Directory server is modified, the configuration must be updated in NSX Manager.
Until it is updated, attempting to log into NSX Manager with an AD user fails with below.Your login attempt was not successful. Unable to contact the LDAP Server.
OR
Your login attempt was not successful. The username/password combination is incorrect or the account specified has been locked.
In the NSX UI, testing the Connection Status for the LDAP Server(s) under System > User Management > LDAP will fail.
OR
VMware NSX-T Data Center
VMware NSX
NSX manager will fail its connection to an LDAP server due to a mismatch between the certificate information stored in NSX Manager and the active certificate on the LDAP server. There are other issues that can cause the connection to fail such as incorrect credentials, network connection problems, and so forth, but this article is specific to having an LDAP Server's certificate information in NSX that is different from the current certificate used by the LDAP Server.
nc -vz <LDAP server FQDN or IP> 636". If the connection fails, then you will first need to troubleshoot the networking and get it working.openssl s_client -connect <LDAP server FQDN or IP>:636 -showcerts"Reference https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/3-2/administration-guide.html
If the above workaround doesn't work this error also matches the Signing algorithm compatibility issue KB below:
VMware NSX LDAPS server connection not working POST upgrade to VMware NSX 4.1.X