AD Server Config - Test connect fails when using secure ldap - VisualCron - Forum

Community forum

Brad Dresler
I believe secure ldap is required in order to make groups work, however, I can only get secure ldap to work when pointed directly at a domain controller.

<domainname> works
<domainname>:636 does not work
<domaincontroller01>:636 works

I've confirmed dns on the host resolves <domainname> to <domaincontroller01>. Pointing it to the DC directly works, but it should be pointed at the domain name in the event that DC fails.

To add to this, <domainname>:636 worked at one point, probably the first week or so after implementation. I've got an AD group configured in user permissions using it. If I try to add another group using <domainname>:636 as AD server it fails.
Scroll to Top