Have you on the server side verified that
LDAP is up and listening on the proper port? ps –eaf | grep slapd netstat -na | grep 389 tcp
0 0
0.0.0.0:389
0.0.0.0:*
LISTEN If the above come back and indicate it is
up and listening see if you can telnet to the <ip> 389 and get something
back. Also you could check to see if you are
getting errors on server startup by checking the slapd.log on the server side
and see if it is reporting any errors. If you are using the command line search
are you specifying the remote server using the –h option? Most of the errors seem to indicate there
is nothing listening on the server to handle the search request. --Kris Burton From:
openldap-technical-bounces+kris.burton=acision.com@OpenLDAP.org [mailto:openldap-technical-bounces+kris.burton=acision.com@OpenLDAP.org]
On Behalf Of Donny George
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. |