Date: Tue, 09 Feb 2010 23:56:48 +0100 From: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de> To: tequnix@frogmi.net Cc: "O. Hartmann" <ohartman@zedat.fu-berlin.de>, freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: net/samba34: after upgrade from samba33 -> samba34 no client can connect to samba34-server anymore! Message-ID: <4B71E830.8020907@mail.zedat.fu-berlin.de> In-Reply-To: <20100209110021.599bddab@zev.home.callooh.com> References: <4B6FF8D0.8030208@zedat.fu-berlin.de> <20100209110021.599bddab@zev.home.callooh.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/09/10 11:00, tequnix@frogmi.net wrote: > Am Mon, 08 Feb 2010 11:43:12 +0000 > schrieb "O. Hartmann"<ohartman@zedat.fu-berlin.de>: > >> I have no idea what's going wrong. The authentication is done via >> LDAP. Using samab33 works without problem. > > did you use "smbpasswd -w ..." to store the ldap password? i realized > that this is a necessary step when upgrading from samba 33 to > samba 34 (when using ldapsam as passdb backend) > > best regards, > =A8reinhard Hello. Yes, I did, but the problem went away, when I removed all old=20 /var/db/samba files and folders. Although samba34 created=20 /var/db/samba34, the existence of folder and files /var/db/samba seemed=20 to cause the problem. Now, everything is smooth and shibny. Thanks, Regards, Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B71E830.8020907>