Topic RSS
Wow you have tried a lot of things. There are a lot of experienced Slingbox users here. Good to hear that this site was recommended to you.
Here is what I would do. I assume you want a router connected to your modem if not then you would be happy connecting the Slingbox directly to it. ![]()
Pick a router and then reset the router and modem to default. Turn off any UPNP that you may may turned on in the router confing.
Then go to watch.slingbox and setup remote viewing. Make sure it says that everything it setup.
What this does is make it so you are not using any tcp/udp port forwarding and basically eliminates any mtu issue.
If it sets up then watch using the browser and see what your speeds are. If ok then you can try the standalone Mac or Windows player but first make sure it works ok in the browser.
2:43 am
January 13, 2012
Brandon C
Thank you for your advice. I have already tried toggling UPNP (forgot about that one!)
I am beginning to suspect my ISP in Australia (remote end) is restricting my connection. Sling support advised me to contact them and ensure that port 5001 is available.
If they are restricting my connection what tests can I perform to check? It doesn't make sense that a direct connection to my modem would by-pass any restriction.
I have tried re-configuring my Slingbox and Router in the UK an opened port 4001. This has no effect.
Are there servers the Sling website/client contacts that my ISP could be restricting?
Sling does use Amazon webservices to help relay some streams that could be something your ISP restricts but hard to tell.
When streaming what does it show you as your connection type? Ctrl-left click in browser, Alt-Shift-I in Windows player. If you have a port open for tcp then it should show tcp. If not then it will show Relay or SNATT.
You can also do a tracert from your computer to the slingbox's WAN IP and see if there are any huge latency issues.
Another quick and easy test to see if you can reach your Slingbox's open tcp port from whare you are is to do a
Telnet WanIpofSlingbox Openport
IE: telnet 123.12.123.123 5001
Since support said they can connect fine there must be something between you and the Slingbox causing the problem but I don't know why using the router would cause a problem and direct connect to the modem doesn't.
Unless there is double NAT problem. You can read more on that here.
1:53 am
January 13, 2012
Thanks Brandon C. I have a few follow up questions.
When I ctrl Left click in the browser I just get 'about'. Where should I click?
PING 86…….. (86……..): 56 data bytes
64 bytes from 86……..: icmp_seq=0 ttl=253 time=103.102 ms
64 bytes from 86……..: icmp_seq=1 ttl=253 time=99.289 ms
64 bytes from 86……..: icmp_seq=2 ttl=253 time=100.121 ms
64 bytes from 86……..: icmp_seq=3 ttl=253 time=95.854 ms
64 bytes from 86……..: icmp_seq=4 ttl=253 time=106.573 ms
— 86…….. ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 95.854/100.988/106.573/3.624 ms
Do these results look acceptable?
Telnet WanIpofSlingbox Openport IE: telnet 123.12.123.123 5001 - Please explain how do I do this?
3:22 am
July 12, 2011
I had a bit of trouble when adding a second slingbox and port forwarding on my virgin media hub.
Eventually I found the slingbox setup software was reporting the slinbox was at a different IP address than it was actually on. I used the Lantricks "Lanspy" software to check its location.
By the way, I opened TCP 500n and not UDP.
Good luck
Phil
You should just click in the video while it is playing.
Those are fairly high ping times but not that bad. Try pinging Google.com to see a comparison.
Re: Telnet, From a cmd window you should be able to type in telnet followed by the WAN ip address of where your slingbox is located and then followed by the port you have opened.
IE
Telnet 123.123.12.123 5001
Must be registered to post


Log In
Register
Forum





Recent Comments