Can No Longer Get to Kodi From Windows Over SMB Connection...

gjwAudio · September 7, 2017 at 8:03 AM

Help ! please...

Auto-updated to LE 8.1.1 on ancient 847 NUC (and set Min protocol to SMBv1)... now, can't browse NUC from ancient Windows (XP) Explorer over the network.

After latest 8.1.1 update, trying to map NUC as a network drive gets stuck at "Connect to localhost" login, asking for username/password. Similar failure trying to use desktop shortcuts to specific Kodi folders (ie: "\\192.168.1.170\Root File System\storage\.kodi\temp" ).

Samba service in LE is set to use Password Authentication, but login fails. Tried it without Authentication set too - same result (login fails).

Curiously, Kodi is reporting itself to the network as "OpenELEC (%h)", even though I have changed every settings field I could find to "LibreELEC".

FWIW, the WORKGROUP name has been successfully changed, and survives successive reboots. Also, going in the other direction - File Manager in Kodi can access data on the XP machine just fine.

This loss of this access is fairly disastrous, as I usually administer the NUC through Windows Explorer.

Help and directions would be greatly appreciated.

Thanks.

**Klojum** · September 7, 2017 at 8:58 AM Official Post

Do you use a passworded account on your Windows XP box?

If not, create one.

**escalade** · September 7, 2017 at 12:18 PM

You should have read the release notes. Remove your old /storage/.config/samba.conf and reboot.

gjwAudio · September 7, 2017 at 8:19 PM

Quote from escalade

You should have read the release notes. Remove your old /storage/.config/samba.conf and reboot.

escalade

Many Thanks for theEFFECTIVE tip & remedy.

Deleting the samba.conf file + reboot did indeed restore Windows network browsing capability as before.

Re-reading the Release Notes suggests there's NO WAY for the user to affect the behaviour of the Samba config. Previously I added this to the standard config:

Code

[Root File System]
path = /
available = yes
browsable = yes
public = yes
writable = yes

Is there any way to achieve this under the new regime ?

Thanks again for Help & Support.

SyntaXErroR · September 7, 2017 at 9:12 PM

Just saw this post, had same issue but didn't even manage to delete samba.conf. rolled back to 8.0.2...

LE 8.1.1 - Samba mess

**chewitt** · September 8, 2017 at 11:08 AM Official Post

gjwAudio If you re-read the instructions a third time there's a section that states users with Samba3 configs need to update them to be based on the new Samba4 template - that's all. Yours was Samba3 and (as explained) needed updating. You can choose to nuke it too, but then you loose your customisations. Content of file has changed but process hasn't.