Following on from the discussion below in the Ransomware thread, I've been trying to turn off SMB1 in Windows (given it's been highlighted as an security risk) but still retain access to my Seagate Goflex Home, which is an old NAS device.

However I've not had any luck with the change suggested.

I don't think there's an officially supported way to get into the Linux it's running, but there is a workaround on the OpenStora website. This allowed me to access the /etc/samba folder and replace the smb.conf with a modified version containing the extra "max protocol " line, as suggested by @jimbo45.

I tried both SMB3 and SMB2, rebooting between each change.

But I still can't access the fileshare on a Windows 10 machine with the SMB1 feature switched off.

I did run the smbstatus command, which returned:
Samba version 3.0.28-0.el5.8.oe5

I'm wondering if the version of Samba running on this NSA might simply be too old to support SMB2 or SMB3 ?

It's a long time since I used Unix to any degree so it's possible I missed something.

Here's part of the original discussion:
Me said: View Post
It turns out that this stopped me accessing my old NAS drive (at least the way I've been using it) so I've been going round turning SMB1 back on again.

jimbo45 said: View Post

Hi there
On the SAMBA config on your NAS box set it to SMB2 or 3 - then that should allow you to remove SMB1 from Windows.

Do it in the GLOBAL section --file is called smb.conf and usually exists in folder /etc/samba
max protocol = SMB3
# can set it to SMB2 if you want experimental SMB2 support.
workgroup = WORKGROUP
server string = Samba Server Version %v

; max protocol = SMB2

log file = /var/log/samba/log.%m
max log size = 50
security = user
passdb backend = tdbsam
name resolve order = bcast host lmhosts wins


You need to restart the smb and nmb (or depending on your system - might be called smbd and nmbd) services - or probably better re-boot the NAS server.

Check with (as root or sudo user) that the config file is OK with TESTPARM.