Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

LDAP Search not working correctly.

461 views
Skip to first unread message

dboltz

unread,
Aug 19, 2008, 1:15:33 PM8/19/08
to
I'm running Domino and Sametime ver 7.01 on Windows servers and I’m
having difficulty with LDAP searching. As far as I can tell,
everything is setup correctly on the server but when trying to run
ldapsearch I get the error 81 (Can’t contact LDAP server). I do
notice that if I run on localhost from the server it will work but if
I use the hostname it doesn’t.
Here’s the output…

C:\Documents and Settings\admin>ldapsearch -v -h sametime cn="dave*"
ldap_sslinit( sametime, 389 )
ldap_bind_s( dn=, pw=, method=128 ) failed (V3), error
: resultCode 81 (Can't contact LDAP server)
Backing down to V2 bind...
ldap_bind_s( dn=, pw=, method=128 ) failed, error
: resultCode 81 (Can't contact LDAP server)


C:\Documents and Settings\admin>hostname
sametime

C:\Documents and Settings\admin>ldapsearch -v -h localhost cn="dave*"
ldap_sslinit( localhost, 389 )
filter pattern: cn=dave*
returning: ALL

*** Filter is: (cn=dave*) ***
....

Does anyone have some ideas why I can’t query the LDAP server in this
case?

Regards,
Dave

dboltz

unread,
Aug 19, 2008, 2:13:57 PM8/19/08
to
Please forgive me. I figured out my problem. In basic terms, the
problem was between my chair and keyboard…

I tried to connect to the 389 port on my server using telnet and it
failed. Because of this I decided to retrace my steps and check the
entire configuration. The configuration looked good but the ldap
service wasn’t loaded on the server. I guess I overlooked that
because the ldapsearch on localhost worked and therefore I figured it
was already loaded. As soon as I ran ‘load ldap’ on the server,
everything worked as advertised.

Regards,
Dave B.

0 new messages