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

 
Learn about scoring Forum's Raw Score: 83465.6
October 15, 2006 08:09 AM

Categories: PC

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

Member Avatar

lucky43210

Member
Joined: 12/17/2005

I'm having an unusual problem. 
I have the sling software installed on several machines (my laptop, my desktop at home, desktop at work, my son's laptop at his school and a friend's laptop as well).
I upgraded to 1.3.0.176 on all machines.  I also upgraded the sling firmware last week.
The laptop at home works fine (wireless).  The desktop at work works fine.  The friend's laptop works fine.
My son's laptop at school and my desktop at home both receive the dreaded error 0x8007274C.
When I first received the error on my desktop at home, I realized I hadn't upgraded to 1.3.0.176 on it.  I installed it and received the error message again.
One other thing.  My son's laptop worked fine on Friday, and that was after the firmware upgrade.  Problem began for him Saturday night.
Since my friend's laptop is on the WAN, the problem does not appear to be on the Slingside. 
Suggestions?

Discussion:    Comments 1-7 of 7 | Latest Comment

October 15, 2006 10:57 AM

Ok lets break it down.  You have (correct me if I get something wrong):

Laptop - LAN - Wireless - Works

Desktop - LAN - Wired (I assume) - Does not work

Desktop at work - WAN - Works

Friends Laptop - WAN - Works

Son's Laptop at School - WAN - Worked, but now does not

How is your Slingbox connected to your home network (wired or wireless).  This could be key to your issue at home.  It is not unusual for wireless routers to by default block all traffic between the wired LAN and the wireless LAN.  Or depending on the exact configuration of your home network (how many routers including broadband modem, what is plugged into what, and what subnets you might have) it is possible that the Slingbox and wireless laptop just happen to be on the same LAN subnet but your desktop is on a different LAN subnet and does not know how to "get to" the Slingbox.

Your Son's laptop is a tougher one.  The fact that it worked and now does not obviously means something changed/broke along teh data path.  I am assuming that your home router firewall allows ALL incomming traffic to the Slingbox port.  If you set it up to only allow certain IP address, then your Son's IP address may have changed.

More likely is that the school may have noticed the high traffic that Slinging creates and blocked it.  You could try switching to a common port 80 or 443 and see if that works.  You have to change the port in the Slingbox network setup, on your port forwarding etc.

 

October 15, 2006 11:34 AM

You have it right. 

The Slingbox is connected directly (wired) into the Zyxel Router.  The only things plugged into the router are the Slingbox and the internet connection.  

The home desktop is not on a LAN (i.e. not through the router) at home but has it's own direct connection to the internet modem.  (I'm on VDSL)

No, I never did anything special for my son's laptop.  He just plugged in at school and was good to go.  I doubt the ISP saw high traffic (Sling-wise) since he moved into a frat this semester.  They have Directv there and he hasn't been slinging heavily.  He just watches New York Islanders hockey.

Thanks for the input.  I'm going to piggyback on a neighbor's wireless and see if the laptop works on a WAN.

More info shortly... 

 

 

 

 

 

October 15, 2006 11:40 AM

Well, the laptop connects just fine using a 'borrowed' WAN connection...

October 15, 2006 1:32 PM

Obviously since you can connect both localy and over the WAN, your basic setup is correct.  The problem at home as got to be an IP/routing one.  Your Zyxel LAN and WAN conenction work since this is where both your wireless LAN Sling conenction work and your various WAN accesses work (other than your Son's).  The problem at home has to be with your Desktop connection.  Although I assume you did double/triple check that you entered the Finder ID correctly in the Desktop Slingplayer.

I am a little confused though on exactly how you home is set up.  Is your Zyxel that the Slingbox is plugged into a wireless router and the same one your home laptop connects to?  When you say internet connection in plugged into the Zyxel, do you mean your VDSL line (your Zyxel is alo a DSL modem) or do you mean an ethernet port out of your intenet DSL modem plugs into your Zyxel.

Your desktop is not connected to your router, but is directly connected to your internet modem.  Is this the same internet modem that the Zyxel is connected to or do you have two diffferent internet connection (VDSL and something else) or two different DSL modems (one would be the Zyxel above)connected to the same VDSL?.

What about public IP addresses?  How many do you have and what device has it/them?

Again it sounds like your problems are network ones, not Sling ones really.  So the only way to help is to understand in detail your network setup.

October 15, 2006 2:07 PM

My home setup is fairly complex but it has worked perfectly for 18 months without a glitch.

I live in a community with internet delivered by NXCONN Wireless.  They deliver the signal to the clubhouse from where it is transmitted wirelessly to the community.  I have a Zyxel Prestige 84 VDSL wireless modem in my basement which then breaks off into a DLink DSS -8+ Router to the various terminals inside the house.  My desktop accesses the modem directly in that fashion. 

The Slingbox resides in my son's bedroom.  It connects to a Zyxel X-550 router which is connected directly into a terminal in his room.  The only other thing connected to that router is the internet cable.

fyi: I just ran a speedtest and got 12mbps Down and 9 mbps Up on my desktop.

I know this sounds complicated but I swear it has worked perfectly and continues to function perfectly on the machines I mentioned earlier.

Thanks for taking an interest. 

If you are a slingmedia employee, I'll be happy to provide you with my finder ID.

October 15, 2006 5:37 PM

OK first I am not  a Sling Media employee and I dont think your Finder ID would help anyway since we know it works over the WAN.

I understand your set up for the most part, it is similar to mine.  I am going to make the assumption that you are using double NAT.  That is that your DLINK router is using a private IP address range on the LAN side.  Since your Desktop and x-550 (wireless router) both are conencted to the DLINK (if I understand you description correctly) they should be on the same sub-net (same address range).  The x-550 is likely also set up to use NAT and has a different private address range it is using on its LAN side (hence your double NAT situation).  Since the Slingbox is connected to the x-550 it is on a different sub-net then your desktop.

My understanding of how the Slingplayer works it it first looks for a Slingbox on the same LAN as the player being used.  If it does not find one it uses the Finder ID to get the PUBLIC address of your outer most router.  This is the first router configured to portforward all sling traffic towards the slingbox.  It then sends the "are you there" (or something like that) over the designated port (default 5001)  to your PUBLIC IP address.  Your router (DLINK) knows to forward that to the slingbox (or actually in your case to the x-550 which in turns sends it to the slingbox).  Now the slingbox replies on the same port back to your PUBLIC IP address.  Now that router gets confused.  On one hand this is a reply from another address on the other hand it is supposed to send all traffic on that port to the slingbox.  I think you can see the issue.  I suspect it is a infinite loop kind of thing.

One thing I would try is on your desktop, go into the Slingplayer and then slingbox properties (edit when slingbox directory window pops up).  Under direct connection click on "For remote connection I prefer to use...IP adress...",  enter in the slingbox's actual private IP address.  I think using a direct internal IP may bypass the DLINK's port forwarding since the traffic should never hit teh WAN side.  I THINK it should pass through the x-5500 ok also, but maybe not.  I am not that much of an expert to be sure.  the port forwarding on the x-550 might still cause an issue.

If that does not work the only other thing I can think of is reconfigure your home network to all be on the same subnet.  That would mean disabling NAT on the x-550 and using it as a regular router.  While not exactly hard to do, it can be fairly involved and requires a fair understanding of IP addressing and sub-nets as well as router setup, DHCP passthrough, or static IP addressing etc depending on exactly how your routers work.  Its would be too much to try to describe here.  Between your x-550 deocumentation and/or some research on the internet you might be able to set it up.

Or conenct the slingbox directly to the DLINK.  Get ethernet switch and connect it to the terminal in your son's room.  Connect both the Slingbox and the x-550 to the switch.  This would put the slingbox on the same subnet as the desktop.  You would need to change the Slingbox network settings as its IP address would change, and you would need to change the DLINK portforwarding to point to teh new address and delete the x-550 portforwarding.  You might (porbably will) have a problem connecting using your wireless home laptop now.  If so, go to the "For remote connection I prefer to use...IP adress...",  on the laptop and enter in the slingbox's new private IP address.  That should work as the notebok traffic will only go through the x-550 which no longer has any port forwarding conflicts.

October 15, 2006 8:27 PM

Thanks for the heavy thought you put into this...  I'll try to post a resolution when it happens.  Thanks again!

Discussion:    Back to Top | Comments 1-7 of 7 | Latest Comment

Thread is locked, no more posts may be added.

 
 

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