PDA

View Full Version : Issue with BBox and UPnP



sajh
December 1st, 2010, 03:23 PM
Hi,

I just got my BBox 2 days ago, but am yet to successfully stream any local files from my server. As I am not a big fan of SMB due to some bad blood in my relationship with that historically I thought I would seize the opportunity to give UPnP a go. However, seeing as you are currently reading this read I think its safe for me to spoil the outcome by simply stating "ARRRRRRGH".

My current setup at home is:

A laptop running Windows XP acting as a server in this test with TVersity (UPnP server) connected via wireless.
A stationary rig running WIndows XP, with Boxee installed connected wired
A BBox connected via wireless.

For some reason, when attempting to view available UPnP sources at the BBox, I get "No files found at source" whilst if I attempt the same at my stationary, using Booxe, I can successfully connect to the TVersity server and stream the shared content.

Worth noting is that I have done no tweaking what-so-ever to the TVersity settings, so I hardly think that I managed to lock out the BBox somehow, and when I run wireshark at the laptop (server) I see a huge amount of network traffic whenever I use Boxee at my stationary, and no traffic whatsoever when trying to connect through my BBox. I am somewhat certain that I have not messed anything up with any port forwarding or so in my router either.

Let me know whatever other information might be of use to be able to pinpoint the error.


Cheers!


(sorry if this has already been addressed before, seems my googling kung fu is not up to par this evening. feel free to redirect me to any self-help-thread together with any decent amount of insults.)

sajh
December 3rd, 2010, 12:42 PM
shameless bump

sajh
December 3rd, 2010, 12:52 PM
nevermind, turned out to be a noob mistake as suspected.
By default boxee was a part of a workgroup named WORKGROUP. Removing this and doing an old fashioned windows-esque reboot solved the issue it would seem.


Thread can be locked, closed, removed, burned or whatever end seems most suitable.

bmcassagne
November 3rd, 2011, 02:07 PM
This was the only solution I could find to my Media Server problem. Now after the latest update this solution will not work either. If I delete the workgroup name it just pops back in there.

Ronald
November 4th, 2011, 05:31 AM
This was the only solution I could find to my Media Server problem. Now after the latest update this solution will not work either. If I delete the workgroup name it just pops back in there.
To my knowledge SMB filesharing is always done in a workgroup of some kind.
That is simply how Microsoft designed it to work. (SMB is the native filesharing protocol of Windows.)
So it makes sense that your attempt to delete it causes the software to use a default instead.

What you need to do is not to delete your workgroup setting for Boxee, but instead to redefine that string to match the workgroup used by your server. And if you have more than one server in your LAN (PCs, NAS, whatever), then they should all be configured to be part of the same workgroup.

As for UPnP usage, I'm not really sure what rules should apply here, but most recent reports about it seem to agree that this is pretty much bugged out of all consideration right now anyway. So for the time being SMB is a better choice for sharing files in a LAN with Boxee.

Best regards: Ronald