I'm getting similar issues with regards to smbd dieing and a broken
connection to slapd though I'm not using TLS; same release 3.0.24-2. I
have configured the samba on this box as a PDC. I did a test setup of
samba as a PDC about a year ago and was able to get it working okay,
ver. around
Hi, Steve
3, linux clients with LDAP authentication don't comply
4, AFAIK, samba on client dosen't comply (need to prove)
5, eGroupWare webserver with LDAP user authentication dosen't comply
Comply with what?
I'm sorry for error, comply=complain.
--
To UNSUBSCRIBE, email to [EMAIL
What is the cn in the SSL certificate being used by the LDAP server? It
seems odd that this would work at all with start tls, unless your SSL
certificate was set up oddly.
This is the beginning of the /etc/ldap/slapd-cert-ldap1.pem
Certificate:
Data:
Version: 3 (0x2)
Hi
I haven't found log messages from smbd die.
It's quite difficult to do some real testing, because this is our
production server. However I'll try it probably in Thursday.
Are there any log messages when the smbd dies?
I haven't found any. I'll try it again.
And all of these other
On Mon, Mar 05, 2007 at 01:49:02PM +0100, Mgr. Peter Tuharsky wrote:
Are there any log messages when the smbd dies?
I haven't found any. I'll try it again.
That's unusual; even on a segfault, smbd should throw a stack trace in the
log.
And all of these other clients are configured to use
On Mon, Mar 05, 2007 at 01:57:49PM +0100, Mgr. Peter Tuharsky wrote:
What is the cn in the SSL certificate being used by the LDAP server? It
seems odd that this would work at all with start tls, unless your SSL
certificate was set up oddly.
This is the beginning of the
We have successfully workarounded the issue.
We have set the passdb backend to
ldapsam:ldap://localhost:389;
Now it works. Excepting that there are annoying errors in log:
[2007/02/20 14:30:23, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not
On Mon, Feb 19, 2007 at 02:58:17PM +0100, Mgr. Peter Tuharsky wrote:
The odd thing (no easy answers TM) is, that despite of the errors in
log, the Samba domain WORKS for a little while. Machines and users log
on, as if nothing happened. Users get authenticated, network shares are
connected.
On Tue, Feb 20, 2007 at 02:29:15PM +0100, Mgr. Peter Tuharsky wrote:
We have successfully workarounded the issue.
We have set the passdb backend to
ldapsam:ldap://localhost:389;
What is the cn in the SSL certificate being used by the LDAP server? It
seems odd that this would work at all
On Mon, Feb 19, 2007 at 07:31:25AM +0100, Mgr. Peter Tuharsky wrote:
Steve Langasek wrote / napísal(a):
On Thu, Feb 15, 2007 at 01:36:51PM +0100, Mgr. Peter Tuharsky wrote:
We've had a working Samba/LDAP domain based on Sarge. Now we're trying
to move to Etch. We recycled old configs, or
Steve Langasek wrote / napísal(a):
On Mon, Feb 19, 2007 at 07:31:25AM +0100, Mgr. Peter Tuharsky wrote:
Steve Langasek wrote / napísal(a):
On Thu, Feb 15, 2007 at 01:36:51PM +0100, Mgr. Peter Tuharsky wrote:
We've had a working Samba/LDAP domain based on Sarge. Now we're trying
to move to
Steve Langasek wrote / napísal(a):
On Thu, Feb 15, 2007 at 01:36:51PM +0100, Mgr. Peter Tuharsky wrote:
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
On Thu, Feb 15, 2007 at 01:36:51PM +0100, Mgr. Peter Tuharsky wrote:
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.
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:
14 matches
Mail list logo
