From owner-freebsd-questions@FreeBSD.ORG Tue Feb 9 22:56:51 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E3A8106566B; Tue, 9 Feb 2010 22:56:51 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 245F48FC13; Tue, 9 Feb 2010 22:56:50 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1Nez0j-0006cX-JD>; Tue, 09 Feb 2010 23:56:49 +0100 Received: from e178020182.adsl.alicedsl.de ([85.178.20.182] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1Nez0j-000570-GB>; Tue, 09 Feb 2010 23:56:49 +0100 Message-ID: <4B71E830.8020907@mail.zedat.fu-berlin.de> Date: Tue, 09 Feb 2010 23:56:48 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100207 Thunderbird/3.0.1 MIME-Version: 1.0 To: tequnix@frogmi.net References: <4B6FF8D0.8030208@zedat.fu-berlin.de> <20100209110021.599bddab@zev.home.callooh.com> In-Reply-To: <20100209110021.599bddab@zev.home.callooh.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable X-Originating-IP: 85.178.20.182 Cc: "O. Hartmann" , 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! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2010 22:56:51 -0000 On 02/09/10 11:00, tequnix@frogmi.net wrote: > Am Mon, 08 Feb 2010 11:43:12 +0000 > schrieb "O. Hartmann": > >> 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