SMB shares "disconnected"... but not really

[aleith]

Let me preface this by saying I am indeed a fan of Boxee, although by the end of this post it is not going to sound like that.

As soon as money enters the picture the software needs to have some level of polish, and quite frankly the amount of bugs and glitches in boxee box is astounding.

This shares disconnecting issue is absolutely ridiculous. The primary reason I bought this box was for local content, and up until now it has worked (almost) perfectly for it. This needs to be fixed immediately. Users should not have to wade through pages of technical posts to "fix" this themselves, it should just *work*. Samba shares are nothing new, and all of my computers/devices can see each other and have never seemed to have a problem. Boxee box, why cant you?

When this was free software I was running on my Apple TV I didn't complain when there was a problem (although, speaking of that, I don't recall having any problems whatsoever with samba shares when I was using that setup), but now I paid over $200 for this buggy piece of shit and it is starting to wear on me.

For the love of god get your shit together boxee, learn how to properly test your software with some of those millions you just received.

[elrock]

Good news: the bug has just been closed, which I assume means the fix will be included in the next firmware update coming soon. Let's hope it works for Macs as well as Windows machines.

I love my Boxee Box and fortunately I haven't experienced any of the show-stopping bugs reported by others, but this particular bug was very frustrating and I'm glad it seems finally to have been resolved.

[andreas@vogler.name]

I have The Same Problem on Boxeee on Ubuntu 11.4 64bit .
It seems that its not working. I Tried now 0.9.23.15885 from Source....
Have had Many Problems in Doing so, but the Bug Remains.

[switch81]

Ok, I got mine working. In addition to running nmbd, I had to open up my server's firewall tables a bit. I was only letting in port TCP/139, which has served me well thus far, but for the BB I also opened up TCP/137,138 and UDP/137,138,139. Works great now.

I'm having similar issues with everyone on this thread...

My setup involves a Mac Mini running the latest Boxee (0.9.23.15885), and a Ubuntu 10.04 media server with a samba share set up.

I have a netbios name enabled in my smb.conf, and I can ping my ubuntu machine from anywhere on the network. I can also use nmblookup or smbclient from my macmini to find the samba share on my ubuntu machine.

I can also add my ubuntu shares by manually adding the sources by search for the IP or hostname... but the shares end up disconnecting very quickly in Boxee.

A previous replier said that opening ports 137-138 for TCP traffic and ports 137-139 for UDP traffic... are these the ports that Boxee is looking for?

I was reading Ubuntu's samba documentation and found this:

https://help.ubuntu.com/community/Samba/SecuringSamba

Configure your firewall (iptables) to limit access to your server. Samba uses ports
- UDP ports 137 and 138
- TCP ports 139 and 445

Now, I don't have a firewall running my Ubuntu machine, but it doesn't seem to be listening to TCP/137-138, or UDP/139... could this by why the ubuntu share never shows up automatically???

Thanks in advance for any help you guys can provide!!!