From owner-freebsd-questions@freebsd.org Tue Jan 2 18:32:10 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 17AF2EB28CC for ; Tue, 2 Jan 2018 18:32:10 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from outmx-028.london.gridhost.co.uk (outmx-028.london.gridhost.co.uk [95.142.156.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D563E6C909 for ; Tue, 2 Jan 2018 18:32:09 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk (unknown [82.71.56.121]) (Authenticated sender: mailpool@milibyte.co.uk) by outmx-028.london.gridhost.co.uk (Postfix) with ESMTPA id 0EB2E22A08279 for ; Tue, 2 Jan 2018 18:31:59 +0000 (GMT) Received: from [192.168.1.13] (helo=curlew) by curlew.milibyte.co.uk with esmtp (Exim 4.90) (envelope-from ) id 1eWRM6-0000i1-8G for freebsd-questions@freebsd.org; Tue, 02 Jan 2018 18:32:06 +0000 Date: Tue, 2 Jan 2018 18:32:06 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Message-ID: <20180102183206.25a6dd12@curlew> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Subject: Unable to write from Windows PC to samba shares after upgrading to samba46 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jan 2018 18:32:10 -0000 After using pkg upgrade samba44 has been upgraded to samba46 with the result that Windows (XP and 7) clients now only have read access to my home directory and cannot write to it. Initially the XP clients couldn't even access any shares after the upgrade because the user name and password were no longer recognised but adding "ntlm auth = Yes" to the [global] section of /usr/local/etc/smb4.conf cleared that problem. Here's the current version of smb4.conf. Apart from adding "ntlm auth = Yes" it's identical to the setup I've been using without problems with samba44. Are there any other parameters which I should add to regain write access to my home directory share? [global] netbios name = CURLEW workgroup = HOME security = User ntlm auth = Yes server string = FreeBSD interfaces = 192.168.1.13/24 hosts allow = 192.168.1.0/255.255.255.0 passdb backend = tdbsam domain logons = Yes printcap name = /dev/null load printers = no printing = bsd # Uncomment the following line, if Windows 10 machines should be able # to log on to your NT4-style domain. server max protocol = NT1 [homes] read only = No browseable = No [photos] path = /home/photos read only = Yes [backup] path = /nobackup read only = Yes [tmp] path = /tmp read only = No -- Mike Clarke