From owner-freebsd-questions@FreeBSD.ORG Wed Nov 3 06:47:44 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 ABC60106564A for ; Wed, 3 Nov 2010 06:47:44 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id 6D37A8FC1E for ; Wed, 3 Nov 2010 06:47:44 +0000 (UTC) X-Virus-Scanned: amavisd-new at BSDLabs AB Message-ID: <4CD1058C.3030302@intersonic.se> Date: Wed, 03 Nov 2010 07:47:40 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.11) Gecko/20101022 Thunderbird/3.1.5 MIME-Version: 1.0 To: Bartosz Stec References: <4CD09908.6080508@it4pro.pl> In-Reply-To: <4CD09908.6080508@it4pro.pl> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: mount_smbfs problem after upgrade Samba 3.4 -> 3.5 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: Wed, 03 Nov 2010 06:47:44 -0000 On 11/03/10 00:04, Bartosz Stec wrote: > >> Hi, > Hello! >> I'm doing a major overhaul of our Samba servers including an upgrade to >> the latest port version, 3.5.6. I'm getting most things in place but a >> remaining problem is that I cannot any longer use mount_smbfs: >> >> mount_smbfs -I 192.168.1.8 //peo at mars >> /inter >> /home/mnt >> Password: >> mount_smbfs: unable to open connection: syserr = Authentication error >> >> Samba server log says: >> mbd/sesssetup.c:1703(reply_sesssetup_and_X) >> reply_sesssetup_and_X: Attempted encrypted session setup without >> negprot denied! >> >> >> smbclient works fine and so does connecting to the shares from Windows >> and Konqerour like "smb://192.168.1.8/". >> >> Anybody on the list with enough knowledge of Samba that could take a >> shot at this? Apparently something changed between version 3.4 and 3.5 >> of Samba. > My knowledge about Samba is limited at best, but it seems that I found > possible couse and working override (solution?). Check this PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=151887 > If this fixes your problem too, please submit followup - more > information port maintainer gets, less time he's gonna need to fix this. > Yes, it fixed my problem. Submitting followup, thanks.