I have an LDAP server, that i can query from a host using ldapsearch.
Code:
ldapsearch -x -v -ZZ -D "cn=test tester,ou=People,dc=lol,dc=local" -W
or
Code:
ldapsearch -x -v -ZZ -D "cn=test tester,ou=People,dc=lol,dc=local" -W -H ldap://192.168.1.11
Returns a valid identical search, and reflects what I've put in LDAP. I have ldap listening on both 389 and 636 right now, can use ldap search with or without the TLS switch (-ZZ) and it always works. you can even telnet to the address and port to see it's listening, and 'netsat -pant | grep (port)' shows it's listening.
However if i try to log in from this host with a simple 'su' command, it returns:
su: user test does not exist
the log files on the server are blank, the log files on the client are as follows:
Code:
ul 30 12:19:27 host3 nslcd[21654]: [1bd7b7] ldap_start_tls_s() failed: Connect error (uri="ldap://192.168.1.11")
Jul 30 12:19:27 host3 nslcd[21654]: [1bd7b7] failed to bind to LDAP server ldap://192.168.1.11: Connect error
Jul 30 12:19:27 host3 nslcd[21654]: [1bd7b7] no available LDAP server found
What did i miss here? how is 'ldapsearch' able to talk to ldap, but 'su' isn't?
