More info after doing some additional testing today. My issue goes away when I change the port to a global catalog port 3268 or 3269 (ie, issue happens when using LDAP/LDAPS ports 389 or 636, but when using LDAP/LDAPS GC ports 3268 or 3269, it works fine). Going to share this info with VMware technical support. Question for you - If you open up AD Sites and Services, have you verified that the DC you're trying to bind to is "checked" as a Global Catalog?
↧