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 = SMB2" to the smb.conf file and > > restarted the service, but Windows remains unconvinced. > > > > What else do I need to do? Is there an easy way to ping the server > > (from Linux) and check what protocol it's using? Note that Linux has no > > problem connecting to the server. > > > > Who is your NAS supplier? > > Maybe try adding > > min protocol=SMB2 > max protocol=SMB3 > > and restarting the service on your NAS? > > If that doesn't work, does your NAS supplier have a support line? Not in any meaningful way. It's an old Iomega unit I've had for about 8 or 9 years, running an obsolete version of Debian. The Samba version is one I updated myself from a repo that attempts to keep more recent versions of software than the manufacturer supplies. It's almost certain that this is down to getting the config right, so I'll try Rex's suggestion and ask on the Samba list. > I could not find a way to determine remotely the version of smb in use. If you find > out, that would be good to know. I know what it is because I can log into the NAS. I don't really care as long as I can make it default to protocol version 2 or higher. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
