Bind Issue with 2016 AD

[Omaelk]

Question by @Deltr0nz 

I am trying to connect our StruxureWare DC to our AD and I am getting a “bind was unsuccessful”, and we are currently running StruxureWare DC version 7.5.0. I found on your forms the following link where a user had some success, however this option will not work starting in February of 2021 when Microsoft disables this. Here is the link I am referring to.

LDAP connection to 2016 DC with StruxureWare Data Center Expert - Exchange Community (se.com)

Please advise.

[Anonymous user · Accepted solution]

Hi @Deltr0nz,

The first thing that I'd recommend is that you look at the following FAQ and particularly the video under "Managing Remote Users".

https://www.se.com/ie/en/faqs/FA158395/

Also note that both the DCE server and the PC running the DCE client must be able to reach the AD server on port 389.

If you are using SSL then there are a few extra things to look out for:

The DC server's SSL cert must be trusted by both the DCE server and the machine where the DCE client is installed.

The DC is being added by host-name not IP, this will not work, the host-name must also match the name on the SSL cert.

The DCE can resolve the host-name of the DC using DNS.

There is network connectivity between the DCE server on port 636 and there is network connectivity between the client and the DC on port 636.

I'd advise that you first ensure that your DC is working correctly with SSL (Authentication using SSL is not enabled by default), next check the DNS, then the certificates. 

-Gavan