From owner-freebsd-questions@FreeBSD.ORG Mon Feb 8 11:41:42 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 EB5B21065670; Mon, 8 Feb 2010 11:41:42 +0000 (UTC) (envelope-from ohartman@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 A7DA88FC0A; Mon, 8 Feb 2010 11:41:42 +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 <1NeRzp-00018l-Il>; Mon, 08 Feb 2010 12:41:41 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1NeRzp-0006xG-H8>; Mon, 08 Feb 2010 12:41:41 +0100 Message-ID: <4B6FF8D0.8030208@zedat.fu-berlin.de> Date: Mon, 08 Feb 2010 11:43:12 +0000 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100206 Thunderbird/3.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: Subject: 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: Mon, 08 Feb 2010 11:41:43 -0000 After upgrading from samba33 to samba34 from most recent ports, no Windows_XP and Windows_7 client is capable of connecting to the samba server anymore! I use the same config as before, did a testparm (it shows this ahaead: Load smb config files from /usr/local/etc/smb.conf max_open_files: sysctl_max (11095) below minimum Windows limit (16384) rlimit_max: rlimit_max (11095) below minimum Windows limit (16384) ). I have no idea what's going wrong. The authentication is done via LDAP. Using samab33 works without problem. Regards, Oliver