I have configured a Windows 2016 system with an AD LDS role, SSL enabled it and am trying to do some additional verifcation of the environment. I have a defined account within the directory that is enabled and has a password assigned. I had expected
to use LDP to remotely confirm the authentication of the system from my workstation as I had already confirmed that I could attach to the directory locally from the server with the appropriate host name, ssl enabled and port defined.
My connection via LDP from the local server (while authenticated as an admin account) returns this:
ld = ldap_sslinit("MYINTERNAL.SERVER.NAME.HERE", 636, 1);
Error 0 = ldap_set_option(hLdap, LDAP_OPT_PROTOCOL_VERSION, 3);
Error 0 = ldap_connect(hLdap, NULL);
Error 0 = ldap_get_option(hLdap,LDAP_OPT_SSL,(void*)&lv);
Host supports SSL, SSL cipher strength = 256 bits
I am able to subsequently bind using the directory account without any apparent issues.
My remote connection from my workstation via LDP (from an entirely different AD domain and account) returns, while using the same connection paramters, this:
ld = ldap_sslinit("MYINTERNAL.SERVER.NAME.HERE", 636, 1);
Error 0 = ldap_set_option(hLdap, LDAP_OPT_PROTOCOL_VERSION, 3);
Error 81 = ldap_connect(hLdap, NULL);
Server error: <empty>
Error <0x51>: Fail to connect to tswadslds03.qa.int.dmz.hban.us.
and concludes with a pop up window stating: Cannot open connection
When I do a bind from the local client using the directory account AFTER attempting this connection it would appear that the account had authenticated but while using port 389 as reflected below:
ld = ldap_open("MYINTERNAL.SERVER.NAME.HERE", 389);
Established connection to MYINTERNAL.SERVER.NAME.HERE.
Retrieving base DSA information...
Getting 1 entries:
Dn: (RootDSE)
I am guessing that LDP in this instance is not getting connected successfully via SSL as originally attempted BUT do not understand exactly why it worked locally via SSL. When I attempt the connection via SSL using the IP address, I get an Schannell
error specifying that the certificate did not match the name but no error at all when using the FQDN from the local client.
Any insights / suggestions / references on this would be appreciated.
sgw