Hi,
Actually I found it like that in pam_ldap.conf without any modification from my 
side and changed as described coz I had the same error beforeBut looks didn't 
work any way!
# Another way to specify your LDAP server is to provide anuri 
ldapi:///ldap.domain.com# Unix Domain Sockets to connect to a local LDAP 
Server.#uri ldap://127.0.0.1/#uri ldaps://127.0.0.1/#uri 
ldapi://%2fvar%2frun%2fldapi_sock/
logs (auth.log):Jan 30 19:13:18 mail imaplogin: nss_ldap: failed to bind to 
LDAP server ldapi:///ldap.domain.com: Can't contact LDAP serverJan 30 19:13:18 
mail imaplogin: nss_ldap: could not search LDAP server - Server is unavailable
What do you think? Is this the problem ?I followed pretty much the indicated 
article there' http://www.openldap.org/doc/admin24/runningslapd.html', so I 
assume no real problem in the configuration for this point!
Thanks.
Date: Wed, 30 Jan 2013 08:19:11 +0100
From: [email protected]
To: [email protected]
Subject: Re: Kerberos/LDAP integration


  
    
  
  
    On 01/30/2013 07:33 AM, Asmaa Ahmed
      wrote:

    
    
      
      
        Hello,
        

        
        I am trying to integrate Kerberos to my Openldap server,
          and I am following pretty much the instructions from there
          'http://www.rjsystems.nl/en/2100-d6-kerberos-openldap-client.php'
        But still can't get it work to connect the client server to
          the LDAP one after the integration!
        I can see this error in my logs:
        Jan 30 17:27:17 mail nscd: nss_ldap: failed to bind to LDAP
          server ldapi://ldap.domain.com/: Can't contact LDAP server
        Jan 30 17:27:17 mail nscd: nss_ldap: reconnecting to LDAP
          server (sleeping 1 seconds)...
        Jan 30 17:27:18 mail nscd: nss_ldap: failed to bind to LDAP
          server ldapi://ldap.domain.com/: Can't contact LDAP server
        Jan 30 17:27:18 mail nscd:
            nss_ldap: could not search LDAP server - Server is
            unavailable 
        

      
    
    

    Using ldapi:// is probably incorrect. You're using the wrong
    protocol scheme, and/or you're not using it correctly.

    

    http://www.openldap.org/doc/admin24/runningslapd.html lists the
    different protocol schemes and how to use them.

    

    -- 

    Bjørn
                                          

Reply via email to