Re: Samba version woes

On Tue, 2018-01-16 at 11:13 +1100, Cameron Simpson wrote: > On 15Jan2018 22:57, Patrick O'Callaghan wrote: > > On Tue, 2018-01-16 at 08:17 +1100, Cameron Simpson wrote: > > > Last year we bought an HP Proliant G8. It has a cool cubic form mactor > > > with 4 > > > 3.5"

Re: Samba version woes

Allegedly, on or about 15 January 2018, Patrick O'Callaghan sent: > I only have my desktop, but that would be Plan C. The irony is that > I'm using Samba purely because I need a backup for my Windows VM, > which is running on the same desktop. Tangential approach: Can you install a NFS client

Re: Samba version woes

On 15Jan2018 22:57, Patrick O'Callaghan wrote: On Tue, 2018-01-16 at 08:17 +1100, Cameron Simpson wrote: Last year we bought an HP Proliant G8. It has a cool cubic form mactor with 4 3.5" SATA drive bays. And an internal SD slot. We've got 2 8TB WD Red drives in it in

Re: Samba version woes

On Tue, 2018-01-16 at 08:17 +1100, Cameron Simpson wrote: > Last year we bought an HP Proliant G8. It has a cool cubic form mactor with 4 > 3.5" SATA drive bays. And an internal SD slot. We've got 2 8TB WD Red drives > in > it in RAID1, the OS on the SD card and /home on a 250GB SSD. That

Re: Samba version woes

On 15Jan2018 12:01, Patrick O'Callaghan wrote: On Mon, 2018-01-15 at 11:07 +1100, Cameron Simpson wrote: On 14Jan2018 23:25, Patrick O'Callaghan wrote: > On further study, I strongly suspect my mods to the config file are > being overwritten on

Re: Samba version woes

On Sun, 2018-01-14 at 20:52 -0500, Bill Shirley wrote: > Does your NAS configuration have a GUI front-end? Perhaps it has a Samba > config template that it applies the GUI changes to to create the actual > smb.conf. It does have a GUI, but the Samba options are extremely limited. > Do you have

Re: Samba version woes

On Mon, 2018-01-15 at 11:07 +1100, Cameron Simpson wrote: > On 14Jan2018 23:25, Patrick O'Callaghan wrote: > > On further study, I strongly suspect my mods to the config file are > > being overwritten on reboot. Apparently the NAS has firmware that > > restores basic stuff

Re: Samba version woes

Does your NAS configuration have a GUI front-end?  Perhaps it has a Samba config template that it applies the GUI changes to to create the actual smb.conf. Do you have shell access? Does it have the 'locate' command so that you can find this template and change it? Does it have cron running so

Re: Samba version woes

On 14Jan2018 23:25, Patrick O'Callaghan wrote: On further study, I strongly suspect my mods to the config file are being overwritten on reboot. Apparently the NAS has firmware that restores basic stuff from a read-only partition on booting. Does it have a persistent

Re: Samba version woes

On Sun, 2018-01-14 at 11:35 -0800, Gordon Messmer wrote: > On 01/14/2018 09:40 AM, Patrick O'Callaghan wrote: > > I get: > > PORTSTATE SERVICE > > 445/tcp open microsoft-ds > > Host script results: > > | smb-protocols: > > | dialects: > > |_NT LM 0.12

Re: Samba version woes

On 01/14/2018 09:40 AM, Patrick O'Callaghan wrote: I get: PORTSTATE SERVICE 445/tcp open microsoft-ds Host script results: | smb-protocols: | dialects: |_NT LM 0.12 (SMBv1) [dangerous, but default] So clearly the config option isn't being used, or

Re: Samba version woes

On Sun, 2018-01-14 at 23:12 +0800, Ed Greshko wrote: > On 01/14/18 21:51, Patrick O'Callaghan wrote: > > I have a Samba server running on a NAS, but according to my Windows VM > > it's running SMB1 and is thus insecure, so Windows won't connect to it. > > > > I've added the line "min protocol =

Re: Samba version woes

On Sun, 2018-01-14 at 23:16 +0800, Ed Greshko wrote: > On 01/14/18 23:11, Patrick O'Callaghan wrote: > > On Sun, 2018-01-14 at 08:57 -0600, Rex Dieter wrote: > > > Patrick O'Callaghan wrote: > > > > > > > I have a Samba server running on a NAS, but according to my Windows VM > > > > it's running

Re: Samba version woes

On 01/14/18 23:19, Rex Dieter wrote: > Ed Greshko wrote: > >> On 01/14/18 21:51, Patrick O'Callaghan wrote: >>> I have a Samba server running on a NAS, but according to my Windows VM >>> it's running SMB1 and is thus insecure, so Windows won't connect to it. >>> >>> I've added the line "min

Re: Samba version woes

On Sun, 14 Jan 2018 15:11:51 + Patrick O'Callaghan wrote: > The Samba version is 3.2.15. Perhaps that is the problem. My fedora 27 box is running samba-4.7.4-0.fc27.x86_64 and my windows 10 virtual machine mounts a samba provided share with no complaints.

Re: Samba version woes

Ed Greshko wrote: > On 01/14/18 21:51, Patrick O'Callaghan wrote: >> I have a Samba server running on a NAS, but according to my Windows VM >> it's running SMB1 and is thus insecure, so Windows won't connect to it. >> >> I've added the line "min protocol = SMB2" to the smb.conf file and >>

Re: Samba version woes

Patrick O'Callaghan wrote: > On Sun, 2018-01-14 at 08:57 -0600, Rex Dieter wrote: >> Patrick O'Callaghan wrote: >> >> > I have a Samba server running on a NAS, but according to my Windows VM >> > it's running SMB1 and is thus insecure, so Windows won't connect to it. >> > >> > I've added the

Re: Samba version woes

On 01/14/18 23:11, Patrick O'Callaghan wrote: > On Sun, 2018-01-14 at 08:57 -0600, Rex Dieter wrote: >> Patrick O'Callaghan wrote: >> >>> I have a Samba server running on a NAS, but according to my Windows VM >>> it's running SMB1 and is thus insecure, so Windows won't connect to it. >>> >>> I've

Re: Samba version woes

On 01/14/18 21:51, Patrick O'Callaghan wrote: > I have a Samba server running on a NAS, but according to my Windows VM > it's running SMB1 and is thus insecure, so Windows won't connect to it. > > I've added the line "min protocol = SMB2" to the smb.conf file and > restarted the service, but

Re: Samba version woes

On Sun, 2018-01-14 at 08:57 -0600, Rex Dieter wrote: > Patrick O'Callaghan wrote: > > > I have a Samba server running on a NAS, but according to my Windows VM > > it's running SMB1 and is thus insecure, so Windows won't connect to it. > > > > I've added the line "min protocol = SMB2" to the

Re: Samba version woes

Patrick O'Callaghan wrote: > I have a Samba server running on a NAS, but according to my Windows VM > it's running SMB1 and is thus insecure, so Windows won't connect to it. > > I've added the line "min protocol = SMB2" to the smb.conf file and > restarted the service, but Windows remains