[SOLVED] Cannot connect to Samba shares

[Don Pedro]

(14th Nov, 2017 06:49 AM)Skywatch Wrote:  So how are you mounting the samba shares if not via here?

As I wrote, I try to use the GUI functionality from within xbian/Kodi, however this seems not to work. What it does under the hood of course I do not know.

(14th Nov, 2017 06:49 AM)Skywatch Wrote:  Did you see this? .....
http://wiki.xbian.org/doku.php/samba

Yes I did, however this describes how you configure a share on the xbian machine. These shares are there and they do work, I can access them from my Windows machine. But what I want to do is access a SMB share on another machine from within xbian. If this means that these shares are written as mountpoints to fstab, well then be it. But obviously the GUI has some problems doing so.

Cheerz

Don

---

(14th Nov, 2017 07:00 AM)Nachteule Wrote:  Did you tried IP-address? That's working for me. Maybe you have a DNS issue

Good point, didn't think of that! So I tried it, but unfortunately it makes no difference, plain IP gives the same connection timeut message.

What I also found out:

• Strangely sometimes(!) the browse function in xbian does list the available machines, so it did this time, I can see all the machines that do offer SMB shares on my net. Don't know why this sometimes works and sometimes not!
• But already if I only try to browse one of those machines to list its available shares I get "Connection timeout".
• I get this error independently if I try to browse a Linux or a windows machine.
• But wait, there is one exception! I have a Fritzbox and if I try to browse this it doesn't error but comes up with a new screen asking me for the login credentials!
  

How come?? This is really weird!

(14th Nov, 2017 07:00 AM)Nachteule Wrote:  But anyway, browsing for SAMBA servers does not work for me as well, no idea why.

Tried some days same procedure with my LE 9.x test installation, same result there. Never see my SAMBA servers

This seems to be a common problem. The net is full of people having this issue. Maybe this is due to the many ways a windoze machine populates the browse list. hosts file, wins server, broadcasts, master browser, netbios, etc., pp. - with such a chaos of obsolete and not so obsolete techniques things can only get awry...
Again Apple showed them how to do this reliable and with no configuration effort on the participating machines. It is justified they named it "zeroconf"...

Cheerz

Don