On ti, 04 huhti 2017, Chris Murphy wrote:
Hi,
Got a Fedora 25 Server using fairly default smb.conf, nothing special,
just to share some storage.
Three clients: macOS 10.12.4, Fedora 26, and Windows 10
On the server, using 'smbstatus' I see the following protocols used
for each client when connected:
Windows 10: SMB3_11
macOS: SMB3_02
Fedora 26: NT1
This is true whether I use smbclient or Nautilus to make the connection.
The smb.conf man page says for "client min protocol" and "client max protocol":
Normally this option should not be set as the automatic
negotiation phase in the SMB protocol takes care of choosing the
appropriate protocol.
We discussed that some time ago upstream and decided still to keep NT1
as default. There are still too many servers running with NT1 variant --
almost all consumer class NAS servers from 5-7 years old don't support
SMB2 or higher protocols. This is noticeable.
We can add couple lines explaining how to change defaults in smb.conf
shipped with Samba.
If I do:
server min protocol = SMB2
server max protocol = SMB3
These are _server_ options, not _client_ as above.
Windows and macOS can still connect however:
[chris@f26h ~]$ smbclient //10.0.0.3/brick1
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
If I comment out the above, and go with:
client min protocol = SMB2
client max protocol = SMB3
Both Nautilus and smblient connect with NT1 protocol.
You did not change client side options.
If I use:
smbclient -m smb3 //10.0.0.3/brick1
I get SMB3_11 protocol connection. So the smbclint *can* do SMB3_11,
it just refuses to autonegotiate it, and even seems to ignore the
server's client and server min directive.
-m option simply sets 'client max protocol' to its value.
I'm not sure how to get Nautilus to use SMB3 or if it even supports
it, or if it's ultimately using smbclient behind the scene.
It is using libsmb library which uses client options from smb.conf
--
/ Alexander Bokovoy
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
