So we've deployed the LDAP Connection Monitor in SAM to about 100 or so DCs. All have LDAP working and they're in a whole bunch of locations globally. However, the results we're seeing are pretty varied. On one poll, the service will show as up and responds fine with a statistic value of 3 (indicating the LDAP version I believe). Then on the next poll, it'll often show as down - mostly with the error message below:
The return code is different than expected. Testing on node '10.1.2.3' failed with 'Down' status ('Down' might be different if script exits with a different exit code).Can not connect to LDAP Server at 10.1.2.3. (-2147016646). Error Code:
-2147016646. Error Message: The server is not operational.
Yet on the following poll, it'll work again. Eg:
This variability in results is undermining the AD team's confidence in Orion's ability to monitor LDAP correctly. So question is, is the error code indicative of network connectivity issues, LDAP connection issues or an Orion issue? And how do we fix it?