Working With Oracle® Solaris 11.2 Directory and Naming Services: LDAP

Exit Print View

Updated: July 2014
 
 

ldapclient Command Cannot Bind to a Server

The ldapclient command failed to initialize the client when using the –init option with the profileName attribute specified. Possible reasons for failure include the following:

  • The incorrect domain name was specified on the command line.

  • The nisDomain attribute is not set in the DIT to represent the entry point for the specified client domain.

  • Access control information is not set up properly on the server, thus disallowing anonymous search in the LDAP database.

  • An incorrect server address passed to the ldapclient command. Use the ldapsearch command to verify the server address.

  • An incorrect profile name passed to the ldapclient command. Use the ldapsearch command to verify the profile name in the DIT.

As a troubleshooting aid, use snoop on the client's network interface to see what sort of traffic is going out, and determine to which server it is talking.