LDAP document in Directory Assistance: "LDAP server is unavailable"

We (our customer) has quite some Domino servers (9.0.1FP10).

They will switch their Active Directory to LDAPS in some weeks.
Our tests to have the Domino server connect to the AD using LDAPS weren't successful.
Update to Domino V10 or Domino V11 is not possible.

We found a way using OpenLDAP as LDAP proxy between Domino V9 and AD:
Domino connects to OpenLDAP on the same machine (127.0.0.1) using LDAP, OpenLDAP connects to AD using LDAPS.

On the test server and some production servers this approach works, but for three servers not.

We have a LDAP document in the Directory Assistance connecting to 127.0.0.1:9389, where the OpenLDAP server listens.
LDAP clients like the one from Softerra and the (Unix) ldapsearch can connect to the OpenLDAP server on this port, and querys are answered.

But those three Domino server can't connect to the OpenLDAP:
[07B0:0045-03C4] NAMELookup::<ProcessDeferredNAB> Domains retrieved from DAGetDomainReplicas: names.nsf,*[127.0.0.1]:9389 via Directory Assistance
[07B0:0045-03C4] 13.08.2020 09:53:37,56 <LDAP GW> LDAP server is unavailable ReturnCode=0x0051 (Can't contact LDAP server)
[07B0:0045-03C4] 13.08.2020 09:53:37,56 <LDAP GW> LDAP server is unavailable ReturnCode=0x0051 (Can't contact LDAP server)

In the OpenLDAP log (set to maximum), there is no sign of a connection attempt.

All three Domino servers have working LDAP documents to the Active Directory using LDAP (without TLS). These documents are disabled and the new ones to OpenLDAP are enabled for the test.

All verify buttons in the LDAP document work.

We temporarily switched on all related debug settings.

We tried show xdir reload.
We tried show xdir debug (no result).
The show xidir doesn't show the line for the connection to OpenLDAP, but it shows the AD connection using LDAP (without TLS).
The connections to OpenLDAP and AD aren't enabled concurrently, but alternatively.

The servers, where the OpenLDAP connections works, and those, were it doesn't, are configurated exactly the same (as far as I can see).

Anyone any idea, how to get Domino connect to OpenLDAP? Or at least to get more details, why this doesn't work on some servers, but on others it works?

Or the really big alternative: How can I get Domino V9 to connect to Active Directory via LDAPS?

Hello,

you need to enable LDAP debug/console logging and check why Domino fails to connect to AD. If it is certificate issue (Domino client is not trusting AD) then it can be resolved very fast - simply by adding trust cert to JVM keystore. If it is cipher issue then situation is slightly harder but still can be resolved (by using different JVM options in config file).

Also, you need to check your Directory Assistance database - there are few useful buttons such as "check connection" that can give you an answer - what is actually is not working properly.

Hi Thomas,

I've gotten this to work to Azure ADDS using Domino 11, but I'm not as familiar with the supported ciphers and SSL/TLS over the wire with version 9. However, this blogger seems to have gotten things to work a while back and it might be worth a read: https://blog.darrenduke.net/darren/ddbz.nsf/dx/solution-domino-directory-assistance-to-active-directory-when-using-ssl-does-not-break-with-9.0.1-fp4.htm .