Quote: server min protocol = SMB2
client min protocol = SMB2
client max protocol = SMB3

(2017-05-23, 23:59)Milhouse Wrote: You only need to add "client max protocol = SMB3" in the smb.conf used by Kodi and Samba will begin negotiating connections starting with SMB3 instead of NT1.

(2017-05-24, 02:39)wgstarks Wrote: Will changes to smb.conf be preserved through updates to kodi or is it necessary to edit the file after updating?

(2017-05-15, 04:46)Milhouse Wrote: Try adding the following to $HOME/.smb/smb.conf (not sure where this file well be on Android):

Code:

client max protocol = SMB3

and restart Kodi. This will instruct libsmbclient to negotiate a protocol higher than NT1 (which is basically SMB1) when connecting to your server.

It seems that the default libsmbclient configuration used by Kodi will limit/restrict any negotiated connection to NT1 even when the Samba server supports more recent, secure and performant versions of the SMB protocol. And when NT1/SMB1 is disabled on the server (which is highly recommended, for obvious reasons), Kodi won't be able to connect to the server at all.

On your server you should be able to see the types of connection your Samba clients are establishing by running "sudo smbstatus -b".

Edit: "smbstatus -b" output on an Ubuntu 16.04 server:

Code:

neil@nm-linux:~$ sudo smbstatus -b

Samba version 4.3.11-Ubuntu
PID     Username      Group         Machine            Protocol Version
------------------------------------------------------------------------------
1801      neil          neil          192.168.0.6  (ipv4:192.168.0.6:52229) SMB2_10
2751      neil          neil          192.168.0.12 (ipv4:192.168.0.12:55642) Unknown (0x0311)
2714      neil          neil          192.168.0.12 (ipv4:192.168.0.12:55590) Unknown (0x0311)

192.16.0.6 is a Windows 7 PC, with SMB2_10 connection

192.168.0.12 is a LibreELEC 9 test build with Kodi 18a1 and "client max protocol = SMB3" - established connection is SMB3_11.

(The "Unknown (0x0311)" protocol is fixed in Samba 4.4.0)

(2017-05-23, 23:59)Milhouse Wrote: See PR12110. NT1 is the Samba default client max protocol. There is nothing you can configure in your server that will change default Kodi NT1 behaviour. You only need to add "client max protocol = SMB3" in the smb.conf used by Kodi and Samba will begin negotiating connections starting with SMB3 instead of NT1. However you need at least Samba 4.1.0 on the client in order for SMB2/SMB3 protocols to be supported. Setting "client min protocol" is known to cause compatibility issues so don't specify it. Also, Kodi is the client not the server so there's no point specifying server settings in the client smb.conf.

(2017-08-02, 08:04)Koying Wrote: Putting samba 4.5.1 in Kodi is on the agenda.
Some dependencies to be merged first, though

PS. For Android I mean, ofc.
Windows uses its own implementation and "pure" Linux uses whatever samba is on the system.
Ios/OSX will depend on how hard it is and how much time the devs have to work on it.

(2017-10-26, 19:22)Rechi Wrote: Krypton only receives bug fixes, no new features. This means it will stay SMB1 only for android, ios and osx.
v18 nightly versions have a newer version of samba (4.1.23) since 23rd May which also supports SMB2 and SMB3.