[SOLVED] Cannot connect to Samba shares

[Don Pedro]

(16th Nov, 2017 11:27 PM)Nachteule Wrote:  Did you already tried this solution?

Just tested and my Kodi is using SMB3_00 protocol now

Unfortunately and contrary to my expectation this does not work for me! What I tried:

• Inserted "client max protocol = SMB3" in /home/xbian/.smb/smb.conf, restarted Raspi
• Additionally added "client min protocoll = SMB2" in /home/xbian/.smb/smb.conf, restarted Raspi
• Did the same with /home/xbian/.smb/smb.conf, restarted Raspi
• I found two more smb.conf, /usr/share/samba/smb.conf and /etc/samba/smb.conf, but from the content I concluded that these are used for the server configuration and I left them out
• Tested temporarily to re-enable SMB V1 on one Linux machine and, whoops, no "Connection timeout" but I get a list of shares and the option to enter the logon credentials
  

So this is proof that the problem here is in fact that Kodi's smbclient does not use SMB V2 or higher but is stuck with SMB V1! From googling I could determine that this seems to be (or was?) a problem with Android, but not with a "regular" Linux distro - and xbian is "bleeding edge", isn't it? So this does not quite match what I'm seeing here, I'm on Raspberry which is of course Debian ARM, not Android. I'm wondering if there is a way to have Kodi's smbclient use SMB higher than V1. Maybe I should in fact ask this on the Kodi forum...

Additionally I will try to manually mount an SMB folder in fstab via the distro's smbclient/mount.cifs, maybe/hopefully this operates with SMB V2, I will report progress. Such a workaround would be acceptable for me, however IMHO Kodi should start supporting SMB V2 and up, as MS is in the progress of disabling the outdated SMB V1 in the aftermath of Wannacry - which absolutely makes sense, no blame on them.

BR

Don