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 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 > ^^ One example of ill-advised suggestion. SMB2 does not do what you think > it does. :-/ (it's non-obvious, but doesn't work in most cases) > OK, fine. But my later post about what nmap reports shows my NAS offering only 2.X and 3.X protocols. So, maybe even if it is ill-advised, it is doing the needful thing on my Synology NAS? -- Fedora Users List - The place to go to speculate endlessly
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
