Unable to Monitor Ldap Service on a Domino Server

hcl-bot · November 15, 2006, 7:59am

Hi,I am trying to monitor LDAP and SMTP services on Domino server from my code. The connection is through a windows API.and the services are running on default ports.

Now, whenever i try to connect to the prot where ldap or smtp is listening to, the connection is refused.

can you suggest what could be the possible reasons for the same and any suggestions to rectify them!!

It would be a great help:).

The error code returned for the refused connection is: 10061.

and one more thing,if anyone can help me out with any LDAP/SMTP related activity logs, it would be a great help.

Thanks,

Gaurav.

hcl-bot · November 15, 2006, 2:25pm

Subject: Unable to Monitor Ldap Service on a Domino Server

I am trying to monitor LDAP and SMTP services on Domino server from my code. The connection is through a windows API.and the services are running on default ports.

If you are concerned that your LDAP client code may not be working correctly, you can try ldapsearch first.

hcl-bot · November 16, 2006, 12:54am

Subject: RE: Unable to Monitor Ldap Service on a Domino Server

Hi Ken,

Thanks for your reply.

But we have a different situation. We have an application in which we monitor the ldap service status [ running or down ] by establishing a connection [WINAPI] to the port on which its listening.

But we are getting the Connection Refused error – 10061 though

service is running on the server and operational.
we are connecting to the correct port [389]

Thanks…

hcl-bot · November 16, 2006, 2:36pm

Subject: RE: Unable to Monitor Ldap Service on a Domino Server

Set aside your monitoring tool for a moment.

Try to reach your Domino LDAP server by running ldapsearch on the Domino server itself. This search tries to retrieve the root DSE of your Domino LDAP server …

ldapsearch -h dominohostname -p 389 -s base “(objectclass=*)”

Now try the same ldapsearch, but run it on the machine you are having problems with.

If the former succeeds but the latter fails, then perhaps you firewalls or something blocking the ldap port.

hcl-bot · November 20, 2006, 8:21am

Subject: RE: Unable to Monitor Ldap Service on a Domino Server

Hi Ken, I ran the Ldapsearch utility but returned the

"ldap_bind_s( dn=, pw=, method=128 ) failed, error

: resultCode 81 (Can’t contact LDAP server)"

Query: In the “-h dominohostname” option do we need to give the Domino Hostname or the ldap hostname where the Ldap server is actually running ? [ex: ldap.acme.com]

– [The hostname is different from the Domino server name] – In this case we gave the hostname.

The output of the sh stat ldap shows some stats related to ldap search –

LDAP.Anonymous LDAP Connections = 18

LDAP.Average LDAP Search time = 0,102

LDAP.Failed LDAP Connections = 57

LDAP.Longest LDAP Search time = 4,797

LDAP.Simple LDAP Connections = 1094

LDAP.Total LDAP Connections = 1112

LDAP.Total LDAP Search Entries Returned = 9169

LDAP.Total LDAP Search time = 2ÿ579,307

LDAP.Total LDAP Searches = 25189

LDAP.Total LDAP Searches for Root DSE = 10

Does this mean that Ldap is operational – Please suggest.

NOTE: This is a Clustered Setup also …

Regards,

Gaurav.

hcl-bot · November 22, 2006, 8:53am

Subject: RE: Unable to Monitor Ldap Service on a Domino Server

“ldap_bind_s( dn=, pw=, method=128 ) failed, error: resultCode 81 (Can’t contact LDAP server)”

Query: In the “-h dominohostname” option do we need to give the Domino Hostname or the ldap hostname where the Ldap server is actually running ? [ex: ldap.acme.com]

– [The hostname is different from the Domino server name] – In this case we gave the hostname.

Yes, the -h argument is something like “ldap.acme.com”. The simple ldapsearch confirms the experience with your application - you cannot connect from your machine to ldap.acme.com using your configuration arguments.

The output of the sh stat ldap shows some stats related to ldap search –

LDAP.Anonymous LDAP Connections = 18

LDAP.Average LDAP Search time = 0,102

LDAP.Failed LDAP Connections = 57

LDAP.Longest LDAP Search time = 4,797

LDAP.Simple LDAP Connections = 1094

LDAP.Total LDAP Connections = 1112

LDAP.Total LDAP Search Entries Returned = 9169

LDAP.Total LDAP Search time = 2ÿ579,307

LDAP.Total LDAP Searches = 25189

LDAP.Total LDAP Searches for Root DSE = 10

Does this mean that Ldap is operational – Please suggest.

Yes, this means that not only is your Domino LDAP server operational, it has serviced 25,189 searches! So there are (other) LDAP client applications successfully using your Domino LDAP server.

The two simplest explanations that I can think of, given that your Domino LDAP is successfully servicing at least one LDAP application, are:

Your LDAP connection arguments are incorrect. (Typing TELL LDAP SHOW on the Domino console will reveal what settings it is running with)

You cannot reach your Domino LDAP Server from your test machine, possibly due to firewalls.

hcl-bot · November 23, 2006, 12:29am

Subject: RE: Unable to Monitor Ldap Service on a Domino Server

Hi Ken,Thanks for the reply.

I understand what you are saying.

What i want to bring to your notice is that this is a clustered set up. As i dont have much knowledge of the clustered set up, so wanted to know if that can be some kind of a problem.

Moreover, acording to my understanding, there can be multiple ldap servers running on different hosts in the clustered set up. and everytime, we are pinging only the local host with 389 port number.

Can you please help us with this!

Thanks in advance…

Gaurav.