And then add the following line anywhere in the file: client max protocol = NT1 Used by Windows NT. There is nothing you can configure in your server that will change default Kodi NT1 behaviour. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. Anyway, the Samba team recommends to use this workaround. This is from man page: NT1: Current up to date version of the 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. NT1: Current up to date version of the protocol. CORE: Earliest version. SMB1 was disabled on windows server because of security concerns like wannacry. > SMB2: Re-implementation of the SMB protocol. SMB2: Re-implementation of the SMB protocol. Package: smbclient Version: 2:4.11.0+dfsg-10 Severity: normal Dear Maintainer, after update in testing of samba pkgs version 2:4.11.0+dfsg-10 maxprotocol=NT1 seems no more working as aspected ----- $ smbclient \\\\192.168.0.101\\tmp Unable to initialize messaging context Enter BDEV\ilprof's password: Try "help" to get a list of possible commands. Used by Windows Vista > and newer. SMB2: Re-implementation of the SMB protocol. Samba-3.xでは"max protocol"、Samba-4.xでは"server max protocol"と"client max protocol"が指定可能です。 プロトコルバージョンの表記は、smb.confの表記に合わせてあります。 表の"O"がサポートされていること、表の"-"がサポートされていないことを表します。 So “max protocol” was NT1(SMB1) as default. The location of the Samba configuration is as follows: /etc/samba/smb.conf. NT1: Current up to date version of the protocol.

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. Used by Windows NT. Used by Windows Vista and later versions of Windows. Then, open the file (as root or sudo) in a text editor. SMB2 has sub protocols … -m|--max-protocol protocol This allows the user to select the highest SMB protocol level that smbclient will use to connect to the server. Used by Windows NT. Samba 4.10 made it possible to set min/max protocol version via libsmbclient API. Long filename support. NT1: Current up to date version of the protocol.

server min protocol = NT1 to your smb.conf file on the server (in my case, my PC). If I change protocol to NT1, the speed drops to around 50Mbyte/s.

SMB2 has sub protocols available. Known as CIFS. Used by Windows Vista and newer. Known as CIFS. Long filename support. LANMAN2: Updates to Lanman1 protocol. min protocol (G) The value of the parameter (a string) is the lowest SMB protocol dialect than Samba will support. The Samba implementation of SMB2 is currently marked experimental! .The SMB1 protocol has been disabled in the Samba server and client utilities by default In Samba 4.11, the default values of the `server min protocol` and `client min protocol` parameters have been changed from `NT1` to `SMB2_02` because the server message block version 1 (SMB1) protocol is deprecated. Used by Windows Vista and later versions of Windows. If I change protocol to NT1, the speed drops to around 50Mbyte/s. The Samba implementation of SMB2 is currently marked experimental!

If legacy clients are no longer able to connect, type this command in the Shell, then restart the SMB service: sysctl freenas.services.smb.config.server_min_protocol=NT1 If that resolves the issue, you can make that setting permanent by going to System → Tunables →Add Tunable and creating a Tunable with these settings: Used by Windows NT. Used by Windows Vista and newer.

Used by Windows Vista and later versions of Windows. I set “min protocol = SMB2” on samba server but client couldn’t negotiate with server on protocol (smbd[…]: No protocol supported !) We are running a NT4-style Samba PDC for our domain > controller. Setting "client min protocol" is known to cause compatibility issues so don't specify it. Used by Windows Vista and newer. NetBIOS est historiquement le premier protocole réseau utilisé pour partager des fichiers entre micros. Samba est une application qui permet d'utiliser sous Linux le protocole SMB (« Session Message Block ») également appelé le protocole NetBIOS ou LanManager. - - Samba: "min protocol = SMB2" causes "protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE" ... LANMAN2: Updates to Lanman1 protocol. > NT1: Current up to date version of the protocol. Used by Windows NT.