Your message dated Mon, 29 Dec 2008 09:53:54 +0100
with message-id <[email protected]>
and subject line Closing old bug without feedback
has caused the Debian Bug report #500609,
regarding Timeout connecting to LDAP server
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
500609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500609
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: samba
version: 3.0.24-2


We've had a working Samba/LDAP domain based on Sarge. Now we're trying to move to Etch. We recycled old configs, or modified the new ones to be equal.

Now, when I start Samba, it seems it cannot connect the LDAP server. I've got these errors in log:

lib/smbldap.c:smb_ldap_start_tls(612)
  Failed to issue the StartTLS instruction: Connect error
lib/smbldap.c:another_ldap_try(1150)
  Connection to LDAP server failed for the 1 try!

Soon, the smbd exits.
The SLAPD works fine itself, even the authentication goes against it. Just the SMBD cannot connect to it.

I'm googling s while and I found this link:
http://www.ldap.org.br/pipermail/ldap-l/2004-July/000852.html

Was the Samba compiled with correct attributes?

I really don't know, whether this is package error, config error, or OpenLDAP/libgnutls13/Samba communication error.

Peter


--- End Message ---
--- Begin Message ---
For this old bug as well, we really need some feedback as Jelmer requested
in September 2008.

Without feedback, there is no chance that the bug, if still there, can
be investigated.

If you still experience it, please reopen the bug.





-- 


Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to