Posts by shaggy996

Quote from milhouse

Samba shares added in Kodi have nothing to do with the "samba config file" which is for the LibreELEC Samba server and should only be modified by users that understand what it is they are modifying. You're conflating a different issue with whatever problem you have.

I've no idea what your problem is as you haven't mentioned anything useful, so I can't even hazard a guess as to whether what you suggest will work or not (it probably won't, actually).

If you've got a problem accessing your Samba shares then provide details of your Samba server (make, model, version) and what the problem is. Nobody here knows what server(s) you run in your network, or how they may be configured, or what updates have been applied by you which may or may not have disabled certain Samba-related features. I know for a fact that LibreELEC 8.1.2.will work out of the box with the vast majority of Samba servers, but there are some broken Samba servers that need to be worked around (or contact your vendor for an updated server), and there are some features (anonymous access, network browsing) that are no longer supported.

I'll repeat what is already stated in the announcement when dealing with Samba client issues:

1. Try forcing SMB1 in Kodi Settings > Services > SMB Client > Maximum protocol version. SMB1 should work with old and buggy servers, but won't work with more secure modern Samba servers that only support SMB2+ (in which case use SMB2 or SMB3, or better yet leave it as None so that the client - ie. Kodi - auto-negotiates the best protocol).

2. Anonymous access no longer works. You'll now have to configure a username/password in your server, then enter the same username/password details into Kodi when accessing the share and prompted for authentication.

3. Network browsing no longer works when SMB1 is disabled in your master browser (and is flaky at best even when it is). You'll now need to add a network location before adding your Sources.

Display More

Im not sure if you started your replay as soon as I posted or did not read my post. Right after the post I edited in more info on the setup.

As I said a windows 7 computer sharing folders on an open samba, no username or password.

the kodi player is a chromebox with the os removed loading straight to Libreelec.

It works perfect on 8.0.2 and has through all the older versions of kodi I have run.

Now when I go to add a share and brows on kodi it does not even see the workgroup which also has a few windows 10 computers on it.

I have already changed the minimum version to smb v1 and have tried every combination.

I have tried typing in the path manually by IP and share name.

So far nothing besides reverting to 8.0.2 will make it even see the workgroup.

Quote from milhouse

It's a file that you created - use whatever method you used when you originally created it.

I never created anything file wise. I installed libreelec using a usb drive installer, started it and went in through the file section in kodi and added samba shares. So if i go into the file section and delete the shares and restart it will fix it? This is installed on a chromebox modified so that it only has libreelec on it. there is no chrome os any more.

So far all i know to do is revert to 8.0.2 because that works.

I have 2 folders shared off of a windows 7 computer with an open samba share, no user info required. I update to 8.1+ and samba wont even see the workgroup let alone any shares.

Quote from milhouse

That's because, unfortunately, Samba has a number of "moving parts" and we can't foresee every problem scenario that users might have. We have, to the best of our ability, explained the potential issues, but it's up to users to take this information on board and then sort out their own networks - be they Windows, Linux or other Samba servers, with or without SMB1 support, with or without Windows 10 to cause even more problems, with or without anonymous access, with or without LibreELEC OS mounts etc.

If we could give a single guaranteed "do this then this" solution that fixes this Samba mess for everyone, trust me we would have. If anyone feels they can do a better job of explaining how to resolve the different potential problems users with random Samba or Windows servers may face, please add something in the Wiki!

But no one even goes about explaining how to replace your samba config file. All that is said is to replace it with the new one and there is no info at all on how to actually do this.