OUR NETWORK:TiVo Community TechLore MediaSmart Home Pogoplugged See all... About UsAdvertiseContact Us
Previous Thread | Next Thread

 
Learn about scoring Forum's Raw Score: 233449.0
March 27, 2009 04:31 AM

Categories: PRO

Rating (0 votes)
Rate This!

Member Avatar

rlatens

Member
Joined: 03/26/2009

Hi All.

In my work we are the owners of 2 brand new slingbox pros. These are working great except for one strange networking issue.

We use many subnets at work, for this example ill call them:

192.168.1.x

192.168.2.x

192.168.3.x

192.168.4.x

192.168.5.x

192.168.6.x

192.168.7.x

Now, we have the slingboxes plugged into our 192.168.7.x network, either via static or dhcp we are unable to connect to the slingbox via the client from any local subnet apart from 192.168.7.x which is the subnet the slingbox is plugged in to. I have installed the client on 2 notebooks, 1 a macbook and the other is a windows xp laptop, neither client can connect to the slingboxe(s) unless they are plugged into the same subnet.

Is there something im missing in the setup? Both slingboxes are on DHCP but the same problem exists when using a STATIC assigned address on the 7 network. I am unable to verify packets entering the slingbox as there doesn't seem to be a shell i can login to.

Any assistance would be appreciated, seems strange that an IP based device isn't adhering to IP principles :)

 Thanks

Ryan

Discussion:    Add a Comment | Comments 1-8 of 8 | Latest Comment

Sgt Rock Avatar
  Member
March 27, 2009 6:51 AM

Maybe 192.168.7.x has some sort of firewall / access control list blocking sling traffic, ask the network admin.

Can you ping from devices on the other subnets to anything on 192.168.7.x, that would rule out a routing issue.

Generic Member Avatar
Member
March 27, 2009 7:01 AM

Hi there and thanks for the reply.

I am the network admin so we can safely rule out issues at our side :) We can ping the ip of either slingbox from both the 192.168.7.x network and also from any other subnet, ie we can ping 192.168.7.x from 192.168.1.x and 192.168.2.x

This would let you assume that data is getting to and from the slingbox, but it appears not. Our switches have no firewall rules setup so i can safely say its the slingbox not working across subnet, not the local network at fault

NA9D Avatar
  Moderator
March 27, 2009 7:44 AM

The Slingboxes do not work on the LAN across subnets. Your players and clients must all be on the same subnet in order to see them. If you must use different subnets, then what you will need to do is specify a direct connection to the Slingbox IP. Or use the Finder ID and treat it like a remote WAN connection. The result in either case will be that you'll need to force higher resolutions as the software will assume you are on a WAN connection in either case.

The Slingboxes send out broadcast packets on the LAN and that is how the software picks them up and knows they are there. Broadcast packets do not traverse gateway interfaces between subnets.

Slinging w/ Catcher, ProHD, Pro, Solo, AV, and a Classic. Two TivoHDs, Roku Photobridge and a Roku Soundbridge, AppleTV, and Vudu.www.na9d.net Follow me on Twitter

Generic Member Avatar
Member
March 27, 2009 8:01 AM

Hi NA9D and thanks for clarifying this for me.

I have been trying by a direct connection locally by ip, in the "directory" menu clicking "edit" > then entering the IP and default port.

This also fails, as well as the "discovery". Ill try the finder service but in essence what you are saying is, if a client on the local lan, which is on a different subnet, can only connect to the device by going online, through a port forward and back into the internal network?

192.168.7.x ---> gateway --> internet --> back to gateway ---> 192.168.1.x

excuse the crude drawing.

I wasn't able to find any information on your website about multicast traffic in use, or the slingbox having to be on the same subnet. Could you please send me a link as having multicast traffic on our main lan isn't a great idea.

Thanks again

NA9D Avatar
  Moderator
March 27, 2009 8:58 AM

You should certainly be able to connect via a direct LAN IP connection if all the gateways and routes are configured fine in your router. But discovery won't work since the broadcast packets don't traverse the router interface.

Slinging w/ Catcher, ProHD, Pro, Solo, AV, and a Classic. Two TivoHDs, Roku Photobridge and a Roku Soundbridge, AppleTV, and Vudu.www.na9d.net Follow me on Twitter

View unverified member's comment - posted by Parker

Generic Member Avatar
Member
April 3, 2009 3:41 AM

Update:
It seems multi-lan or wan access is disabled until you run the remote setup wizard.

Once i ran the wizard this unlocked the slingbox and both are now accessible across all our network :)

Thanks for replies all.

NA9D Avatar
  Moderator
April 3, 2009 6:51 AM

Yes, you have to run the setup assistant to set up a fixed IP for the Slingbox and I forgot to mention that yeah, you gotta enable remote setup for it to work. The box thinks you are making a remote connection when you operate across LAN subnets.

Slinging w/ Catcher, ProHD, Pro, Solo, AV, and a Classic. Two TivoHDs, Roku Photobridge and a Roku Soundbridge, AppleTV, and Vudu.www.na9d.net Follow me on Twitter

Discussion:    Add a Comment | Back to Top | Comments 1-8 of 8 | Latest Comment

Add Your Reply

(will not be displayed)

Email me when comments are added to this thread

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

You can also log in using OpenID.

close this window
close this window