OUR NETWORK:TiVo Community TechLore RoboCommunity MediaSmart Home DVRplayground See all... About UsAdvertiseContact Us

 
Learn about scoring Forum's Raw Score: 122626.0
July 7, 2008 05:41 PM

Categories: Networking

Rating (0 votes)
  • 1
  • 2
  • 3
  • 4
  • 5
Rate This!

Member Avatar

ehintz

  Member
Joined: 07/07/2008

Howdy all,

I've had fairly consistent crashing from the SlingBox over the past year. At one point it was happening 2-3x weekly, recently it seems like 1-2x monthly, with an occasional longer run. Near as I can tell, it always occurs while watching the stream and making several remote inputs. The connectivity is lost, and the SB simply drops off the network-it can no longer be pinged. Once this happens the only solution is a powercycle.

The SB was already replaced once, this is when the behavior went from 2-3x weekly to 1-2x monthly. 

Support have suggested that this can happen with an ethernet cable in excess of 10 feet between the SB and router. In this case, the SB is connected to a 10/100 switch, which is in turn on a ~50ft run to the dsl router-their claim is that the 50' run from switch to router is a potential cause. Other devices on this switch remain available with no issue when the SB dies-in fact, I have setup a ubuntu laptop on said switch with an x10 serial connection to bounce the SB remotely when this happens.

I've found one other thread which discusses this claim. Frankly, it smells of support monkey grabbing at straws(having spent 2 years at Apple's escalation support desk, I saw a lot of those), which was the general consensus of the other thread. But I'm willing to give the benefit of doubt here, hence this thread. So, what's the story? Is this an offical SlingMedia position? Or is this folk wisdom and waving of a dead chicken?

Here's the other thread on this for posterity's sake:

http://www.slingcommunity.com/forum/thread/11724/maximum-ethernet-cable-run/

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

July 7, 2008 8:15 PM

Does it do it when you're viewing on the LAN or just remote viewing?

My opinion is the distance of the run isn't a problem. I'm sure plenty of people are using at least that long of a run, not to mention powerline ethernet and wireless.

Here are some things I would try. Connect the 50' run directly to the SlingBox or run a 2nd temporary run to verify the switch. Maybe buy another cheap switch and change it out.

Could be the router itself too..

Slinging Tivo Series 2, Tivo HD, and TW cable from a Pro. Slinging Tivo HD from a Solo, Slinging Humax DRT800, and TW cable from a Classic to Sprint Mogul, AT&T SX66, N62, 8525, and Dell Inspiron 8600 with Sprint EVDO over Windstream DSL.

July 7, 2008 8:37 PM

Irrespective of location, unit just completely drops off the network-I figured it out by nmapping the entire subnet; after failure the SB disappears and nothing new shows up. In unix terms, ifconfig down. Pretty sure it was tested with a direct run (I'm remote so not 100% sure on that front). It would seem rather odd to me that the router could do something which would knock the SB offline while leaving the laptop and tivo that are on the same switch alone. Though perhaps some sort of buggy network code on the SB could do it. Still, length of cable to switch feels very much like a red herring...

July 7, 2008 8:45 PM

ehintz,

Another consideration is to look into your current power management. Sometimes the power supply/outlet/CB can be overloaded or unstable due to several issues, as an example:

- Number of concurrent power hungry devices connected into same power supply, outlet and/or circuit breaker

- Voltage spikes, unstable power source, etc.

Every equipment manufacturer has different levels of tolerance and vary by design how they react, some devices will shut down for overload protection or perform inconsistently

I would try connecting the Slingbox in another circuit breaker and/or use a power management system protecting all your electronics (plasma, stereo, etc.)

July 7, 2008 8:46 PM

Hm, interesting suggestion, I'll have a look at that.

July 8, 2008 12:27 AM

It's also possible the unit is having problems due to overheating. You didn't say where you have the Slingbox, but if it's in an enclosed location or near other hot devices, it might be good to move it somewhere open and see if that helps.

July 8, 2008 1:03 AM

Well, it is potentially subject to some heat. But, virtually all the times it's failed have been between 0000-0400 localtime; coolest part of the day. Meanwhile at 1500 or so it's been chugging away fine, when I know that heat is a potential issue, so that seems pretty doubtful. Good thought though, thanks for that.

July 8, 2008 9:52 AM

In the distant past, when one of my ethernet ports was going bad, it got flakey like that. Any chance you could get it plugged into a different port and have it run for a while?

Discussion:    Add a Comment | Back to Top | Comments 1-7 of 7 | 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