I recently disabled SMBv1 on my server after the WannaCry storm. It immediately killed OSMC’s ability to connect to shares through SMB.
Information how to make Kodi work together with SMBv2/3 is hard to find in one place and the posts are sometimes contradicting each other.
It basically comes down to some additions in the .smb/smb.conf file.
You need to add or change to following 3 settings under the global headline.
client min protocol = SMB2
client max protocol = SMB3
client NTLMv2 auth = yes
Didn’t expect it to unfortunately, but it lets us use SMB2/SMB3 where we can.
Kodi v17 is still focused on Samba 3.x, but the good news is they are moving forward. I believe the WAF based buildsystem has been an obstacle for them. We found this problematic when trying to chase down some regressions in the upstream (Debian) version of Samba.
Apologies if I didn’t make myself clear, I was trying to say thats where you would find it.
Anyway you can edit using nano:
make the changes and ctrl-x to exit and yes to save changes.
I may be wrong, but I believe smbstatus is installed as part of Samba (SMB) Server. Which shouldn’t be required for connecting to smb shares on another device. If your having issues setting up Samba (SMB) Server, you would probably better starting a new topic.
I’ve successfully modified the file, but Kodi doesn’t appear to respect it.
With SMB v1 disabled on my server, Kodi cannot access the shares.
If I re-enable SMB v1 on my server, Kodi can access the shares, which it shouldn’t be able to given I have client min protocol = SMB2 set.
Do I need to modify the global smb.conf file also?
I’m not familiar with this as I should be, I use NFS for my shares. Any changes made ~/.smb/smb.conf, should be respected without making changes to the global version. Did you restart OSMC after making changes?
Also it may be worth posting ~/.smb/smb.conf, also debugging logs may give us more of an Idea of whats going on.
Sorry guys for providing a faulty parameter.
SMB3_11 is not a valid option for every samba configuration. SMB3 should be working for most installations. I changed it in the post.
smbstatus is a command run on a samba server. For a Windows server you can do the same with PowerShell. Use: Get-SmbSession | Select-Object -Property SessionId,ClientComputerName,ClientUserName,NumOpens,Dialect | Format-Table