I'm trying to figure out what happened to the Slingbox Pro we have here at home. It's a bit long and complicated, so bear with me...
For a few months, the Slingbox has been serving HD content to the home network, until a few weeks ago where it "fell off" the network. For whatever reason, the Slingbox is not finishing the DHCP handshake (http://en.wikipedia.org/wiki/Dhcp). I've confirmed this via server logs:
Sep 26 19:07:14 nat dhcpd: DHCPDISCOVER from (My Slingbox) via eth1
Sep 26 19:07:14 nat dhcpd: DHCPOFFER on 192.168.0.240 to (My Slingbox) via eth1
And a packet sniffer:
89.905160 0.0.0.0 -> 255.255.255.255 DHCP DHCP Discover - Transaction ID 0x387503b6The Slingbox will repeat this sequence until I pull the plug. However, it apparently works if I connect it to a crappy 10 MBit hub I had lying around.
Sep 25 20:09:39 nat dhcpd: DHCPDISCOVER from (My Slingbox) via eth1
Sep 25 20:09:40 nat dhcpd: DHCPOFFER on 192.168.0.240 to (My Slingbox) via eth1
Sep 25 20:09:40 nat dhcpd: DHCPREQUEST for 192.168.0.240 (192.168.0.1) from (My Slingbox) via eth1
Sep 25 20:09:40 nat dhcpd: DHCPACK on 192.168.0.240 to (My Slingbox) via eth1
This is obviously not acceptable as the hub can't even sustain streaming regular tv antenna shows (let alone the HD content it was bought for).
My setup is not the "Average Joe" setup, but it's not particularly odd either. I have a dual interface Linux box that NATs (http://en.wikipedia.org/wiki/Network_address_translation) traffic to/from the internet and runs a DHCP server (ISC v3.0.4) for the internal network. It is connected to a Netgear switch (http://www.netgear.com/Products/Switches/DesktopSwitches/GS605.aspx) along with a couple of computers and the Slingbox Pro in question.
What I have tried so far:
That list is in no particular order, and I probably forgot a few things. I think it's also worth noting that the other six or so computers on the network have no issues. I found a thread via Google (http://ask.metafilter.com/41279/Slingbox-wont-get-IP-Address-from-DHCP-server) that describes a similar situation with no resolution. I also read a similar thread somewhere on this forum a few weeks ago, but can't seem to find it again (at least I think it was this forum).
I can try to RMA/replace it if necessary, but Sling support gave me some BS about "Linux" not being a supported router in whatever application they were using (also WTF). Anyone have any ideas?
* If this belongs in a different section, let me know and I'll post there. *
I have the exact same problem. Started after power was removed and restored.
It was getting an IP address from a linksys router but now, no more. Doesn't sound like the linux box is the problem.
Ethereal/wireshark show the exact same thing:
DHCP Discover then a DHCP Offer over and over again.
Did you resolve this?
I have a network with a Microsoft SBS 2003 R2 server which allocates IP addresses to all devices on the LAN side. I have reserved a ststic IP address for the slingbox by supplying the MAC adderss to the DHCP server on the 2003 R2 box but every time the slingbox powers up the IP address is shown as "inactive" on the server. Until I get the server to recognise the device it won't work on the LAN.
I am experiencing very similar problems. I cannot get the slingbox to pull a DHCP at all, just a continuous stream of DHCPDISCOVERY and DHCPOFFER. I was able to determine this from my linux router.
I also tried connecting the slingbox directly to a linksys router, with similiar results. Has anybody found a solution to this? I would love to simply set a static IP and be done with it, but I am unable to communicate with the slingbox.
Are firmware updates automatic? Numerous people on the internet are experiencing the same problem, I feel like slim media pushed a firmware update that broke the DHCP client.
Advice?
Moderator
Arizona, United StatesWhat I do, before I even plug the slingbox in, is setup a static address for it. I use the MAC address on the bottom of the box, set it up, then plug in the box and run the setup wizard.
Give that a shot, but be sure to reset your slngbox before doing so.
Have a Sansa device or MP3 player, then check out The latest!
Follow Me on Twitter
I am having the same problem. Does anybody have any other advice than a static route with the slingbox mac address?
I RMA'd the box, although I don't think it is a hardware issue. At least if we make it expensive enough for sling media they will investigate the issue. I was unable to get the arp trick to work.
As was said earlier, you solve almost all your problems by just giving your box a staic IP. It takes a few mins but after that everything should work. With DHCP your box will keep having to try and update it's IP. You will also lose track of your box and can't set up remote viewing if you have to use an IP address to assign the open port to.
Slingbox ProHD Slinging Comcast cable and HD via Comcast HSI using AirLink Powerline adapters; Slingbox Pro and Classic Slinging Sunddenlink Cable and D* HR21 via Sunddenlink HSI, using Linksys Gaming adapter. 2 Slingcatchers set up to use Slings.
How is one able to give the box a static IP? I think most of us are unable to communicate with the box at all. I spent all day with several routers trying to get it to initially pull an IP so that I could assign it a sttatic IP. I even tried faking the ARP tables to talk to it.
Brandon C. said: What I do, before I even plug the slingbox in, is setup a static address for it. I use the MAC address on the bottom of the box, set it up, then plug in the box and run the setup wizard. Give that a shot, but be sure to reset your slngbox before doing so.Are you talking about a static IP via DHCP. I have tried this, and it does not work if the slingbox is unable to complete the DHCP handshake.
Brandon C. said: What I do, before I even plug the slingbox in, is setup a static address for it. I use the MAC address on the bottom of the box, set it up, then plug in the box and run the setup wizard. Give that a shot, but be sure to reset your slngbox before doing so.Are you talking about a static IP via DHCP. I have tried this, and it does not work if the slingbox is unable to complete the DHCP handshake.
Go through the set up again, start over. If needed push the reset button on the back of your slingbox. Then you'll get the option of assigning a static ip to your Sling.
Slingbox ProHD Slinging Comcast cable and HD via Comcast HSI using AirLink Powerline adapters; Slingbox Pro and Classic Slinging Sunddenlink Cable and D* HR21 via Sunddenlink HSI, using Linksys Gaming adapter. 2 Slingcatchers set up to use Slings.
I have reset the slingbox several times. In order for it to communicate with the computer it needs to pull an IP from the DHCP server. As demonstrated before, it never sucesfully completes the handshake, never returning a DHCPACK. I even spoke to tech support and humored their suggestions.
Without being able to talk to the slingbox at all, it is impossible to assign it a static address. There is no physical interface to the device.
Hey! Bump from the dead. To all: this was never directly resolved, but I really wish it had been. We ended up borrowing someone else's nat device and played dumb with Sling support to finally get them to RMA it.
I'm quite certain it's not a firmware version issue. Firmware updates are manual, and ours stopped working randomly after it was working fine for a month or so.
I did try configuring dhcpd(8) to assign a specific IP to the slingbox (by MAC address), with several different IPs within the /24. Someone suggested the slingbox only supported certain ranges. I also tried configuring the slingbox to use a true static IP in the configuration software. Also no success there. What really stumped me was the fact that it worked with the hub Have you tried using a crossover cable to connect directly to the slingbox?
Knock-on-wood, but it's been working ok since the RMA...
I'm having this exact problem on the second Slingbox. The first had this, and they RMA'ed it and the second is having this. At first it would get an IP address, but now its not. The DHCP log shows this for the Slingbox:
DHCP Server sending DHCPOFFER for IP 172.30.14.140 to Client 00:13:b6:03:72:5f via vl0.
Repeatedly, but the Slingbox never accepts that IP address.
This all worked fine up until about 2 months ago and then nothing.
I have a Netgear FVS124G router. This happens when directly connected to the Netgear.
I am embarrassed to admit that for me it was a hardware issue I should have recognized. My original power supply was lost so I bought a replacement with the wrong power capacity. After taking a closer look, I got the right one and everything works fine.
So I'm wondering if this is a problem with my router? It worked until a recent update. I'm going to try with a different brand of VPN router than Netgear (Dlink or Netscreen?)
If other computers/devices can dynamically acquire an IP address from the router, it's most likely not the problem. Wouldn't hurt to try another ethernet cable and/or port on the router though to rule that out. DHCP is not a terribly complex protocol, I still can't figure out why the crappy hub made it "work".
In my case, it was only the Slingbox that had issues, the other 5-7 computers were fine. And with no other changes, the RMA replacement magically worked fine...
Same problem with a brand new router as well. No DHCP acquisition by the slingbox, but every other device works fine.
This is using an Airport Express N as a bridge to a gigabit switch in my entertainment cabinet. Receiver, DIrectTV, MacMini, TV all get IP's fine.
Hey Slingers I just bought a new Slingbox Solo from PC World in UK and at home I just decided to use my Linksys BEFSR41 (10/100 LAN ROUTER/4-PORT SWITCH) and the Solo does not get an IP, I checked all ports and tested cables, all working with my PC and laptop, no problems with my setup. - 'Setting up your Slingbox is pretty darn easy' - Not when it doesn't get an IP it's not lol.
Anyway check this out, I download a little Win DHCP Server (Tiny, get here: http://www.softcab.com/dhcp-server/index.php) run it and reboot the SlingBox, did nothing else (SlingBox still connected to switch and router) and I get the DHCP request from the MAC address of the SlingBox on this Win DHCP Server, so I fill in the info relevant to my LAN and voilla, SOLID NETWORK LIGHT AND PING FROM SlingBox works.
Now to give it a Static IP and be done with it.
Copyright © 2009
Capable Networks LLC.. All Rights Reserved.
RSS |
Privacy Policy |
Advertise With Us |
Terms of Use |
About Us |
Contact Us |
Site Map
Our Capable Community Network:
Drobo Space |
DVR playground |
MediaSmart Home |
MotoDash |
My DigitalEntertainer |
My Open Router |
Robo Community |
Sansa Community |
Sling Community |
TechLore |
TiVo Community |
TouchSmart Community
Slingbox™ is a trademark of Sling Media, Inc. SlingCommunity.com is not affiliated with Sling Media, Inc.
This Week: Do you use the SlingPlayer 2.0 Electronic Program Guide?
Did you forget your password?
You can also log in using OpenID.
Previous Thread
