On Wed, Apr 5, 2017 at 1:38 AM, Alexander Bokovoy <[email protected]> wrote:
> 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.
Yeah.
> We can add couple lines explaining how to change defaults in smb.conf
> shipped with Samba.
What's missing, is the connect the dots that the smbclient
specifically is limited to NT1 by default, and therefore
autonegotiation mentioned in the man page does not apply. The only way
to get autonegotiation for the smbclient is to have a local smb.conf
>> client min protocol = SMB2
>> client max protocol = SMB3
>>
>> Both Nautilus and smblient connect with NT1 protocol.
>
> You did not change client side options.
When I add only the line:
client max protocol = SMB3
To the client computer /etc/samba/smb.conf, when I connect using
smbclient, it is an SMB3_11 protocol version connection. That's good.
Problem is, I can no longer connect through Nautilus from this same
computer and login environment. It doesn't see the server at all in
the GUI. If I comment out this line and reboot (logging out and
logging back in does not fix it), now it's back. I've reproduced this
several times.
CURIOUSLY, over on the server, it thinks there's some connection
that's been made by Nautilus, even though Nautilus sees nothing and
reports no errors either in the GUI or in the journal. I'm gonna guess
this is a bug...
Samba version 4.5.6
PID Username Group Machine
Protocol Version Encryption Signing
----------------------------------------------------------------------------------------------------------------------------------------
15018 nobody nobody f26h (ipv4:10.0.0.122:56622)
SMB3_11 - -
Service pid Machine Connected at
Encryption Signing
---------------------------------------------------------------------------------------------
IPC$ 15018 f26h Wed Apr 5 06:09:13 PM 2017 MDT -
-
No locked files
--
Chris Murphy
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
