samba issue

[Ellyson13]

I have a problem with version from 22.06.2017 when i install it. samba call to write a pass but i dont have it.. in other version i share a file without pass..

[escalade]

Works fine here.

[lefty420]

There is a problem but its is samba side, I recommend creating a new windows account with admin privileges with a user and password. And add that user to your smb share. This bug only seems to effect libreelec as my unbuntu machines can still access without a user/pass. Needless to say my experience is you need a username and password to access windows samba share from within libreelec. On 26 June 2017 at 10:34 Ellyson13 <notifications@github.com> wrote:I have a problem with version from 22.06.2017 when i install it. samba call to write a pass but i dont have it.. in other version i share a file without pass.. —You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.  

[escalade]

There is no such thing as a "Windows samba share", samba = SMB server for Linux and Unix. Anonymous access using LE as a client is a known Kodi issue when using samba4 I think.

[lefty420]

I just meant if your sharing a windows drive / folder from a windows pc. On the latest build it asks for a username and password to connect to a smb share. Even with turning off password sharing from within windows. So if your current windows user doesnt have a password you cannot connect to the share. This only happens with trying to connect librelec to a windows smb share, ubuntu is unaffected. Once I created a new windows user and set it up with a password I was able to connect. On 26 June 2017 at 14:21 escalade <notifications@github.com> wrote:There is no such thing as a "Windows samba share", samba = SMB server for Linux and Unix. Anonymous access using LE as a client is a known Kodi issue when using samba4 I think. —You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.  

[escalade]

I understand what you meant, but correction was needed because you are either talking about a Windows share or a Samba share, two different things. Like I said it's a known issue.

[lefty420]

Fair comment ;) Wonder if its a libreelec issue or kodi as my ubunbtu machine is uneffected and can access the windows smb without issue. On a side note have you considered wine for the build? I think this could open the build up for gamer ready systems. You can even use lutris to install steam just a thought x On 26 June 2017 at 14:42 escalade <notifications@github.com> wrote:I understand what you meant, but correction was needed because you are either talking about a Windows share or a Samba share, two different things. Like I said it's a known issue. —You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.  

[escalade]

I believe i answered that twice now. Wine is x86 only and LE is x86_64 only so no can do. It's also got nothing to do with this issue.

On Mon, 26 Jun 2017 at 17:14, lefty420 ***@***.***> wrote: Fair comment ;) Wonder if its a libreelec issue or kodi as my ubunbtu machine is uneffected and can access the windows smb without issue. On a side note have you considered wine for the build? I think this could open the build up for gamer ready systems. You can even use lutris to install steam just a thought x On 26 June 2017 at 14:42 escalade ***@***.***> wrote:I understand what you meant, but correction was needed because you are either talking about a Windows share or a Samba share, two different things. Like I said it's a known issue. —You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#32 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB7rdWzBDoUMFraC_Ef0JJKCULQoqOCSks5sH8q-gaJpZM4OFE_k> .

-- Sent from Gmail