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 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.
> An excellent question for a samba support forum (and mention what version of
> samba you're using).
>
> One option:
>
https://lists.samba.org/mailman/listinfo/samba
Sure. I recognise that this isn't a Fedora issue, however I've had some
luck with Samba questions here in the past so I thought I'd check first
in case it's something obvious. Not really interested in becoming a
Samba expert ...
The Samba version is 3.2.15.
OK....
I found the way to list the versions being offered by a remote service.
nmap -p445 --script smb-protocols <target system>
Example, for my NAS....
[root@meimei ~]# nmap -p445 --script smb-protocols ds
Starting Nmap 7.60 (
https://nmap.org ) at 2018-01-14 23:14 CST
Nmap scan report for ds (192.168.1.152)
Host is up (0.00027s latency).
PORT STATE SERVICE
445/tcp open microsoft-ds
MAC Address: 00:11:32:2A:64:E2 (Synology Incorporated)
Host script results:
| smb-protocols:
| dialects:
| 2.02
| 2.10
| 3.00
| 3.02
|_ 3.11
--
Fedora Users List - The place to go to speculate endlessly