Problem accessing Kodi SMB shares after upgrade to 8.2.3

KaramH · January 29, 2018 at 1:46 PM

Hi there!

So here's my Setup. I own:

- A HTPC in my living room, that also acts like a server, running on an generic intel chip with LibreELEC 8.2.3 installed

- A RaspberryPi Model 1B in my bedroom, also running LibreELEC 8.2.3

- A Win 10 Laptop, from which I usually copy Media onto the server

Since I just updated to the new LibreELEC version (don't know exactly which one was running previously - it had Krypton 17.3 running) I can't access the server anymore over the SMB-shares. I know, that there have been some changes recently concerning the SMB protocols that Kodi uses, but anything I tried to get it to run just won't work.

Basically the problem is, that I cannot even see the HTPC in the network. I already tried to configure the "new" samba.conf, but even if I let in the standard values it takes no effect.

All three computers are in the same workgroup called "WORKGROUP". But even in the data browser in Kodi i can't see the other machines in the SMB Folder. It only really works via the zeroconf browser. On the Windows Machine though - no chance at all. I tried to access it via it's given name in the explorer (\\HTPC or \\LIBREELEC), via IP-Adress (\\192.168.0.20) and via the share name (i.e. \\192.168.0.20\Update) - but still it seems to not even trying to connect to one of those...

I also tried tweaking the settings of the min-max protocol version in Kodi (1-1, 2-3, 2-2, 3-3, 1-3) but after rebooting it's always set back to "None"...

Does anybody have any Idea what I could do? I'm really running out of ideas right now...

**milhouse** · January 29, 2018 at 2:50 PM

Did you read the announcement documenting the Samba changes? Network browsing is no longer supported which is why you don't see the other shares listed in Kodi - you need to manually add their network location now.

I don't know why the min/max protocol settings would be resetting to "None" after a reboot - that's not right but you're the first person to report it. Are you changing the Kodi client settings, or the settings in the LibreELEC Settings add-on?

If you're editing the Samba Server configuration samba.conf then you may have added an error. Upload your version, and also "journalctl -a" from the server (to a pastebin site, then post the links).

Out of the box LE 8.2.3 with default/stock Samba Server and Kodi client SMB settings will work fine with Windows 7+ so if it's not working then check any changes you've made, reset them to default and start again.

KaramH · January 29, 2018 at 5:07 PM

Allright, after I executed "journalctl -a" I saw that an old iMon-driver seemed to block everything else (ETx), after deactivating it, it finally worked as it should (ETz)...

I can now access again through Windows. Problem solved - I guess.

Thank you very much!

**milhouse** · January 29, 2018 at 7:04 PM

You might also want to fix the typos in your samba.conf:

Code

Jan 29 17:55:03 HTPC smbd[584]: [2018/01/29 17:55:03.007792,  0] ../lib/param/loadparm.c:772(lpcfg_map_parameter)
Jan 29 17:55:03 HTPC smbd[584]:   Unknown parameter encountered: "brwoseable"
Jan 29 17:55:03 HTPC smbd[584]: [2018/01/29 17:55:03.007833,  0] ../lib/param/loadparm.c:1750(lpcfg_do_service_parameter)
Jan 29 17:55:03 HTPC smbd[584]:   Ignoring unknown parameter "brwoseable"
Jan 29 17:55:03 HTPC smbd[584]: [2018/01/29 17:55:03.007861,  0] ../lib/param/loadparm.c:772(lpcfg_map_parameter)
Jan 29 17:55:03 HTPC smbd[584]:   Unknown parameter encountered: "writeabele"
Jan 29 17:55:03 HTPC smbd[584]: [2018/01/29 17:55:03.007871,  0] ../lib/param/loadparm.c:1750(lpcfg_do_service_parameter)
Jan 29 17:55:03 HTPC smbd[584]:   Ignoring unknown parameter "writeabele"