test

System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)

ldapclient Cannot Bind to Server

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

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

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

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

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

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

  6. 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.