ldap communication has stop to work

[Ilovecheckpoint]

I have noticed randomly, ldap communication to AD does not work anymore.

Synthoms are the followings:

selecting Ldap account unity property:

Fetch branches: Failed to connect to LDAP Server. Please ensure that the administrator's credentials are correct and try again

If I enable ldaps, the fingerprint fetch does not work.

Account role: when I try to add a user: errore retreiving results

I have checked and updated the AD account and it did not solve the problem.

Communication from management server and from the gateway to AD is opened.

Does exists an exaustive guide on troubleshooting the problem?

Ideally, I would like to automatize a check ldap and ldaps every day to be sure there is no problem.

[simonemantovani]

If you can use LDAP in clear text, try to perform a capture with tcpdump between managemen server and LDAP server, so it will be possible to verify possible issues.

[Lesley]

Do you have this issues on all DC servers that you connect with? Do you use IDC? (please note: Check Point recommends to use Identity Collector as the Identity Source instead of AD Query.)

You can use the build on tool for further debugging: https://support.checkpoint.com/results/sk/sk100406

What is output during issue: adlog a dc

[Chris_Atkinson]

Where possible please confirm the details of the version / JHF levels and Windows server versions involved.

[spottex]

If the AD team recently updated their AD cert, they need to provide the new Cert MD5 fingerprint so you can add it and retest the fetch query