Directory sync fails with error Connector communication failed because of invalid data: The specified Bind DN and password could not be used to successfully authenticate against the directory. Sync test Response from connector: Failed to complete dry run

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Changed DNS server as per kb change DNS settings on a vIDM appliance without any issue 
• After doing so triggering directory sync fails intermittently with error Connector communication failed because of invalid data: The specified Bind DN and password could not be used to successfully authenticate against the directory. Sync test Response from connector: Failed to complete dry run 

• Error in the /opt/vmware/horizon/workspace/logs/connector-dir-sync.log is similar to below: 

  2025-06-09T11:59:26,297 ERROR (Thread-8) [################;admin@###################;127.0.0.1;] com.vmware.horizon.connector.admin.controller.DirectoryController - Error occurred while verifying the Directory configuration.
  com.vmware.horizon.connector.exception.ConfigurationVerificationException: Unable to bind to the directory
  Caused by: com.vmware.horizon.directory.DirectoryServiceException: Unknown runtime error occurred
  Caused by: javax.net.ssl.SSLPeerUnverifiedException: hostname of the server '###################' does not match the hostname in the server's certificate.
   
  Caused by: java.security.cert.CertificateException: No subject alternative DNS name matching ################### found.
   at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:230) ~[?:1.8.0_402]
   Caused by: com.vmware.horizon.directory.DirectoryServiceException: Unknown runtime error occurred
   at com.vmware.horizon.directory.ldap.dc.service.context.StartTLSContextFetcher.fetchContext(StartTLSContextFetcher.java:52) 
  Caused by: javax.net.ssl.SSLPeerUnverifiedException: hostname of the server '###################' does not match the hostname in the server's certificate.

• Running nslookup of the DNS showed that it was resolvable but the reverse nslookup reported old incorrect entries

   

Environment

VIDM 3.3.x 

Cause

There were left over DNS entries with incorrect values

Resolution

Reach your DNS provider to remove incorrect DNS records