Installing AD Password Filter Fails On MS Windows 2003 / Ldapbindssl.exe Fails With: Ldap bindERROR / System Error Code: 1397 / LDAP Error Code: 52 / Error Message: Server Unavailable
(Doc ID 1528077.1)
Last updated on FEBRUARY 27, 2019
Applies to:Oracle Internet Directory - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Oracle Internet Directory (OID) 11g, e.g., 188.8.131.52.
Successfully installed The Active Directory (AD) Password Filter on other Microsoft (MS) Windows 2008 and 2003 Domain Controllers (DC).
(Note: Using the PW Filter from the OID 10g media on Win2k3 as a workaround to the problem outlined in <Document 1520463.1> and associated <Bug 15990599>.)
Installation of the PW Filter in a Windows 2003 R2 32bit machine fails with errors concerning the connection to the load balancer front-ending OID, and when testing with ldapbindssl.exe, it fails with the following errors:
Checking if SSL is enabled
SSL not enabled.
SSL being enabled...
System Error Code: 1397
LDAP Error Code: 52
Error Message: Server Unavailable
Verified that the Trusted root certificate is imported.
Telnet and ping tests to the OID hostname also work, as well as ldapbind -U 2.
The same problem occurs if bypasing the load balancer and using the OID physical hostname and/or IP address.
The ldapbindssl.exe attempt is not being recorded in the OID logs, so the connection does not seem to be reaching OID.
After a failed test, this error occurs in the MS Event Viewer:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document