Samba shares problem with LibreELEC (Krypton) v7.90.008 [WORKAROUND]

Quote from escalade

Probably a better default anyway since most users won't edit their hosts file.

I don't think that this would be a better default (at least not long-term). A local hosts file (if it/an entry exists) should override a broadcast.

Now, if there is a known bug with the SMB client as used by Libreelec/Kodi which can't be fixed easily, making a temporary change to the default as a work-around would be acceptable if it was well documented (in the forum, release notes, comments in the actual file, etc.) that it is a work-around in version xx for a specific problem then it would seem ok.

I agree, and that's why I changed the order in the first place. Let's have someone actually test this before considering anything further.

Quote from outcave

I'm sorry but the fix proposed by escalade on post #14 does not work.
I back to use "/storage/.config/hosts.conf" workaround

I can confirm, that the fix proposed by escalade on post #14 does not work.

Using Libreelec Milhouse #1128 generic - the only solution for me is to edit the host.conf the way outcave said.

Quote from outcave

Ok Ok... I found the issue and the solution (or better to say: the workaround)!
The problem is the name resolution... LibreELEC will connect to the Samba (SMB) share via the hostname (beacuse I added the Samba share via the GUI and the hostname was presented to me), "NAS" in my case: smb://NAS/Multimedia/Film/HD/Cartoon/testmovie.1080p.x264.mkv.
So I have edited the file "/storage/.config/hosts.conf" with the IP and hostname (same as "/etc/hosts" file):

Code

# hosts.conf


# This configuration file allows you to manually map hostnames to
# IP addresses


# Format:  <ipaddress> <hostname1> <hostname2>
# Example: 192.168.0.3 libreelec libreelec.mynetwork


# NOTE: do not edit /etc/hosts directly
# edit /storage/.config/hosts.conf then reboot
192.168.1.200 NAS
127.0.0.1       localhost LibreELEC
::1     localhost ip6-localhost ip6-loopback LibreELEC

Display More

Now the access to the Samba shares is always OK and really more fast!

I leave to Kodi and LibreELEC team the "work" to understand:

1. Why with the Skin "Confluence" this problem is not faced
2. Why with the oldest version of LibreELEC this problem there was not

Anyway, I expect and I hope, that the access to Samba shares will be guaranteed also via hostname without any action needed by the user into the /etc/hosts file (as it should be)...

Thanks.

Display More

Ok Thank you so much for this post! I have had this same issue for weeks and I thought it was my network connection but it is exactly this. I did go in and rename my share and it worked perfectly. So Probably a Stupid Question but i want to try the fix above.

Format: <ipaddress> <hostname1> <hostname2> Is this the Ip adress where my files are stored (for me it is a server i built that house my files or my odroid c2 address?)
Is the hostname 1 the name of my Odroid C2 ? (It would be libreelec) & would Host name 2 be the name of my desktop as it is seen on the share? DESKTOP-UU0E2M1?
Any help is appreciated!!

Hi OutCave, Still Must be missing something The first image is where I am Editing the file? I cant seem to locate the Storage folder? The Second Image is my workgroup name. The third Image is my Ip address on my Odroid & the 4th Picture is my is what the Smbshare looks like pointed to my Movies files.

Could you possibly show me what my Hosts.conf file should look like with the info I provided? & some guidance on how to get where /storage/.config/hosts.conf is if I am not looking in the correct place? I just remoted in with the Ip of of my odroid but I am not sure if that will work.

The Ip for my my Media server is Picture #5

Any Help Greatly appreciated. After this I should be golden with the Latest release of Kripton it looks Fantastic!!!

Your hosts file will just say

# hosts.conf # This configuration file allows you to manually map hostnames to# IP addresses # Format: <ipaddress> <hostname1> <hostname2># Example: 192.168.0.3 openelec openelec.mynetwork # NOTE: do not edit /etc/hosts directly# edit /storage/.config/hosts.conf then reboot


192.168.1.2 DESKTOP-U0whatever
192.168.1.3 LIBREELEC

Probably the LIBREELEC entry isn't necessary.

It's imporant you use static IPs of course.

Also, when you add SMB share movies to Kodi via the GUI, you can use the IP address manually instead of choosing 'Browse'. This can be more reliable in my experience.

Thank you for the reply, I will try that when I get home, Can you please give me a little more info on how to get to the file Hosts.conf I can remote in through windows but am not seeing /storage/.config/hosts.conf ( I can put the file in the ConfigFiles directory where the Dummy Host file lives) Will that work? Or is there some other way to get to it. The first screenshot shows what i see when i remote in. Sry guys just learning my way through.

Quote from Qualityofpicture

Thank you for the reply, I will try that when I get home, Can you please give me a little more info on how to get to the file Hosts.conf I can remote in through windows but am not seeing /storage/.config/hosts.conf ( I can put the file in the ConfigFiles directory where the Dummy Host file lives) Will that work? Or is there some other way to get to it. The first screenshot shows what i see when i remote in. Sry guys just learning my way through.

The one that you see in your first picture above is the hosts file. It just doesn't have any entries yet.
All you have to do is add the entries to it and save (making sure to keep the .conf extension) then reboot

Quote from Iridium

S2) Add the NAS with explicit IP in the gui smb://<IP address>/<Shared Folder>

So you add the IP address & the shared folder name. I just replaced the Shared folder name with the Ip and it seemed to work?

Quote from Qualityofpicture

Thank you for all the help. I think I fnally got the work around working! Network seems to be rock solid.

I have the same Problem with V7.90.009.

My NAS and my HTPC are the same device. But I can't copy some files from my laptop to my smb-shares.

Only the internal storage (update folder etc.) is working, but not the external drives.

I used the Workaround in Post #1 and #9, but they didn't help.

So what can I do?

Hi

I have the same kind of issue, I can access all files on my Pi from Windows PC, but if I copy files from my Windows PC to my Hard drives connected on my Pi, I can only copy files less then 500mb, but it takes forever, any files larger gives an error.
I can access my Windows shares via Kodi and watch the files.

This worked with V7.90.008, but in V7.90.009 it is not working.

I tried the solutions in the Forum, but didn't work.

There should be a fix in 7.90.010 for copy-to-HDD issue.

In the meantime change "strict allocate = yes" to "strict allocate = no" in your /storage/.config/samba.conf

Quote from milhouse

There should be a fix in 7.90.010 for copy-to-HDD issue.

In the meantime change "strict allocate = yes" to "strict allocate = no" in your /storage/.config/samba.conf

Thank you very much. Worked Perfectly after the change.