Topic: Windows 10 and Samba 4 and max protocol

[TerryF]

Possible issue and what you can do about it re Windows 10 and SME Server 10 https://lists.samba.org/archive/samba/2016-November/204801.html

There are plenty of links to other sites re solution etc including from Mr Microsoft, just google Windows 10 and Samba 4

[ReetP]

Dump Windows 10 seems the simplest solution

[TerryF]

Dump Windows 10 seems the simplest solution

Unfortunately I am trapped like the other 270 million odd users

[Jean-Philippe Pialasse]

Well, similar issue with Fedora 26 ...

[brianr]

Well, similar issue with Fedora 26 ...

https://bugs.contribs.org/show_bug.cgi?id=10433

[ReetP]

Samba 4 now defaults to smb (protocol) v3.

I don't know what settings are in v10 but it probably needs a key to allow changes to the smb version for backwards compatibility.

SME v9 with Samba 3 only has smb (protocol) v1.

This bug refers:

https://bugs.contribs.org/show_bug.cgi?id=10433

As far as a S4 client goes you would need to add ver=1.0 to connect to SME v9.

[dvdsmith]

I have a couple questions on expectations when in the future scenario one is upgrading from v9.2 to v10 (or backup 9.2 and restore to v10).

Will the SMBv3 be the default on an upgrade or will it still be SMBv1 as it was in the v9.2 install?
If a Win10 client was authenticated to the v9.2 server prior to upgrade, will it automatically detect and use SMBv3 (or v2) allowing one to disable SMBv1 on the client without breaking authentication and share access?

I'm just thinking through the order of steps to go through when in the future moving from Samba 3 to 4 and the inevitable demise of SMBv1.

[ReetP]

Samba 4 itself defaults to v3. That isn't per se a choice by SME.

There is nothing to stop anyone raising a bug and asking for a modfiable key, and possibly a v1 default.

[Jean-Philippe Pialasse]

Samba 4 itself defaults to v3. That isn't per se a choice by SME.

There is nothing to stop anyone raising a bug and asking for a modfiable key, and possibly a v1 default.

you mean , nothing stop anyone from using existing modifiable key :

Code: [Select]

config setprop smb ServerMaxProtocol NT1
 expand-template /etc/smb.conf
 service smb restart
documented at least there: https://wiki.contribs.org/Windows_10_Support#notes_about_Window_10_and_SME_Server_10 (the key exists also for SME9)


The question is what should be the default....


for fedora 26 The value default refers to the latest supported protocol,            currently SMB3_11.

for SME 9 Default: max protocol = NT1 ;  Default: min protocol = CORE (supported up to SMB2 ; but not the SMB2_10 and later version )
for SME 10 Default max protocol = SMB3 ; By default SMB3 selects the SMB3_11 variant;   Default: server min protocol = LANMAN1

as we do not set any server max protocol ourself in the config (unless key is used) we then default our server to the default samba value.

[ReetP]

Sorry I wasn't aware that key existed.

I guess SME 10 should run with the new Samba 4 default v3 but some notes in the wiki (unless they exist already!)

[dvdsmith]

...

The question is what should be the default....


for fedora 26 The value default refers to the latest supported protocol,            currently SMB3_11.

for SME 9 Default: max protocol = NT1 ;  Default: min protocol = CORE (supported up to SMB2 ; but not the SMB2_10 and later version )
for SME 10 Default max protocol = SMB3 ; By default SMB3 selects the SMB3_11 variant;   Default: server min protocol = LANMAN1

as we do not set any server max protocol ourself in the config (unless key is used) we then default our server to the default samba value.

Thanks for explaining this, and it outlines what is essentially my question. On a clean install max protocol would obviously default to SMB3. However once 10 is released and one is upgrading from 9.2, will the max protocol automatically change to SMB3 or will it stay at the current NT1? One shouldn't assume one or the other, as in similar situations I've seen either happen. Should be noted in the wiki like ReetP says.

[Jean-Philippe Pialasse]

Thanks for explaining this, and it outlines what is essentially my question. On a clean install max protocol would obviously default to SMB3. However once 10 is released and one is upgrading from 9.2, will the max protocol automatically change to SMB3 or will it stay at the current NT1? One shouldn't assume one or the other, as in similar situations I've seen either happen. Should be noted in the wiki like ReetP says.

well the issue we saw making some try with TerryF, is that the different subprotocols of SMB2 and SMB3 are very badly implemented from one version of samba to another and also and more importantly from one version of windows to another.


to give you an idea here is the man page of a fedora 26. Imagine that a SME9 stops with only SMB2 without hability to specify which sub-protocol as it only knows SMB2_02. And that setting SMB2 without specifiying more might not be understood the same way from a win 7 to a win 8, a non up to date win 10 or a up to date  a win 10.

Code: [Select]

Possible values are :

           ·   CORE: Earliest version. No concept of user names.

           ·   COREPLUS: Slight improvements on CORE for efficiency.

           ·   LANMAN1: First modern version of the protocol. Long filename
               support.

           ·   LANMAN2: Updates to Lanman1 protocol.

           ·   NT1: Current up to date version of the protocol. Used by
               Windows NT. Known as CIFS.

           ·   SMB2: Re-implementation of the SMB protocol. Used by Windows
               Vista and later versions of Windows. SMB2 has sub protocols
               available.

               ·   SMB2_02: The earliest SMB2 version.

               ·   SMB2_10: Windows 7 SMB2 version.

               ·   SMB2_22: Early Windows 8 SMB2 version.

               ·   SMB2_24: Windows 8 beta SMB2 version.

           By default SMB2 selects the SMB2_10 variant.

       ·   SMB3: The same as SMB2. Used by Windows 8. SMB3 has sub protocols
           available.

           ·   SMB3_00: Windows 8 SMB3 version. (mostly the same as SMB2_24)

           ·   SMB3_02: Windows 8.1 SMB3 version.

           ·   SMB3_10: early Windows 10 technical preview SMB3 version.

           ·   SMB3_11: Windows 10 technical preview SMB3 version (maybe
               final).

more over defaulting to SMB3 might do also some damage when upgrading with win10 client  that were already set to use NT1, or still present win 7 or win XP