Hi Jan, now I'm using the authenticated access specifying in the LDAP Properties "Use Secure connection: never" and it's working. Before I was using anonymous access.
Regards, -rochi On Tue, 2004-11-02 at 15:56 +0100, Jan Mynarik wrote: > Hi, > > it looks like you have a similar problem to one I had. See thread > starting with > http://lists.ximian.com/archives/public/evolution/2004-October/040073.html > > I had the same problem but with the server certificate (signed by own > certificate authority). You seem to have problem with client > certificate. OpenLDAP options added to /etc/ldap/ldap.conf or other > config in the same directory should help. Look for the mentioned mailing > list thread for those ldap options. I used them when I tried to access > LDAP server via ldapsearch. > > Hope it helps a bit. > > Regards, > > Jan "Pogo" Mynarik > > On Fri, 2004-10-29 at 20:34 +0200, Dirk Verh�lsdonk wrote: > > On Thu, 2004-10-14 at 09:44 +0200, Rochi Febo Dommarco wrote: > > > Hi all, > > > > > > I'm trying to connect my Evolution 2.0.2 client to an LDAP (OpenLDAP) > > > directory. > > > > > > When I try to connect I get an error popup with the following text: > > > > > > Error loading addressbook. > > > We were unable to open this addressbook. This either means you have > > > entered an incorrect URI, or the LDAP server is unreachable. > > > > > > In the terminal where I have launched Evo with ... I get: > > > > > > (evolution-2.0:7763): eab-widgets-WARNING **: EABView at present does > > > not support multiple writes on the "source" property. > > > > > > And in the terminal where I have launched slapd I get some errors > > > messages: > > > ... > > > ldap_read: want=8 error=Resource temporarily unavailable > > > ber_get_next on fd 8 failed errno=11 (Resource temporarily unavailable) > > > ... > > > TLS trace: SSL3 alert read:fatal:unknown CA > > > TLS trace: SSL_accept:failed in SSLv3 read client certificate A > > > TLS: can't accept. > > > ... > > > > > > It seems that Evo tries the SSL connections but I have specified in Evo > > > to not use the Secure Connection ('Never' setting). > > > > > > I've attached the complete LDAP log fragment. > > > > > > Any help will be greatly appreciated. > > > > > > Regards, > > > -rochi dommarco > > > > Hi, > > > > I get that error too while trying to connect to my openLDAP-server. But > > I learned that this error will not occur when running evolution with > > root previleges. > > > > So it might be caused by wrong permissions?!?!? > > > > regards > > Dirk > > > > > > _______________________________________________ > > evolution maillist - [EMAIL PROTECTED] > > http://lists.ximian.com/mailman/listinfo/evolution _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
