The forums are a place where you can ask a question, get answers from the Community, and chit-chat with other community members. Use the links below to begin exploring the various topics and find the answers you seek!
New to our Forums? Please review our Posting Guidelines and Forum Policy prior to posting.
July 17, 2012
Problems slinging TCP connection from Japan to US. UDP seems to be working great but I have a Slingcatcher at home which I was hoping to use . From what I’ve read, it will not work without the TCP (port forwarding) working.
The internet speed at the Japan location seems to be great. About 20/20 Mbps. In the US, I have Fios 20 down/ 5 up. And this would be a good time to mention that I’m already slinging via TCP from my home in the US to Japan without any problems. Now, I’m just trying set it up in the opposite direction.
When I try to start the stream from home, it shutters and chugs and finally gives me a W202 “poor internet connection” I’m inclined to believe it because my network trace on the PC always shows the TCP connection starts out good and then skips a bunch of packets and cannot recover. But that’s what you get with TCP (more later).
I get it to work again by disabling the TCP either by removing the port forwarding or blocking it completely. Then, I get a high quality picture about at about 2.5-3.0 Mbps. My hopes of getting the Slingcatcher set up… smashed.
So what’s up with this? I thought it might be an MTU issue. But I can’t see that packets are being fragmented. I’ve tried two buffalo AP/routers. Both show the same behavior.
Sounds like the dreaded latency problem with TCP forwarding. There may be nothing you can do to help the SlingCatcher if that is the case.
July 17, 2012
Thanks Brandon. I'm not suspecting this is a latency issue. I wish I could take a network trace on the slingbox side to see what he's sending.
However, I discovered that I can stream from our IPad to our AppleTV. Works pretty nicely so this may relieve my need of the Slingcatcher. I forced it to use UDP for a test. So I'm assuming this will also work when I get home.
May 3, 2010
July 17, 2012
I only mentioned the UDP because I wasn’t able to get port forwarding to work on my Slingbox located in Japan. Blocking UDP is not a requirement. I was just trying to verify posts which stated TCP is a requirement for remote viewing with the IPad.
But I think it will work in either case because:
1) I’m able to use my IPad to remotely connect to a Slingbox which has port-forwarding enabled. I was able to stream it to the AppleTV.
2) My mom was able to connect with here IPad to a Slingbox which does not have port-forwarding enabled. She doesn’t have an AppleTV to test but I can’t see a reason why it would not work the same.
I was even able to use my son’s ITouch to stream to the AppleTV. The Slingbox app got about 1800 Kbps while I was using Airplay. I think the picture the IPad produced on the AppleTV was better.
An IPad is certainly much more versatile than a Slingcatcher.
July 29, 2012
Exactly the same problem I'm facing.
The following video presen show "iPad/iPhone", "Android", "Windows Phone 7" and "SlingCatcher". http://support.slingbox.com/get/network-assistant.html
I dropped an e-mail to support@E-frontier in Japan, asking why my HD-Pro doesn't display "SlingCatcher" as one of players. It could be just because in Japan they don't support SlingCatcher, so they intentionally removed it, I hope. I still believe that there should be no technically reasons not to support.
Before I got the SlingCatcher, I tried the iPad+Airplay solution too. It wasn't too bad but after some comparison, we've noticed that decoding perfomance on iPad might have some bottleneck. So I still wanted to pursue the SlingCatcher solution because I want to watch on my 46inch TV.
Please post if you find the solution to make the SlingCatcher to work.
July 17, 2012
Here is what I’ve noticed.
While I was in Japan, I was able to watch my US Slingbox without any issues. I’ve had this set up for years and it works nicely. In the past, I had lugged around the Slingcatcher. But because of the amount of devices we took, two computers, two IPads, an ITouch and an AppleTV, it was starting to get a little crazy.
Additionally, I took a new, Slingbox HD that I bought in the US. When I set it up in Japan, it seemed to work well on the local network. I called someone in the US to briefly test it remotely. It seemed to be working fine.
However, that was before I configured port forwarding on the router. I had read this was a requirement for the Slingcatcher. After enabling port-forwarding, it completely stopped working for any remote viewing. But locally, it continued to work well via TCP. I ended up having to remove the port-forwarding to restore the remote viewing.
Then I tried the AirPlay option and this is what I observed:
In Japan, using AirPlay (streaming to AppleTV) worked well with the IPad while watching my US Slinbox remotely. It would get about 1800 – 2000 Kbps throughput.
I also tried my son’s ITouch. It seemed to work very well for SD programs. If you tried to stream an HD broadcast, the picture wasn’t very clear. It normally had about 800 to 1400 Kbps.
I also tested the Japan Slingbox from another city in Japan (about 500 miles away.) Using the IPad, quality would fluctuate often. I could get above 2000 Kbps but at times it would be stuck at 500 Kbps. Sometimes the connection would drop completely. But from this location, my US Slingbox performed consistently.
Okay, now I’m back in the US. Here’s what I’ve noticed.
As expected, the Slingcatcher cannot make a connection to the Japan Slingbox. I just had to test for myself!
On both Mac computers, I get a great picture and rates about 2500 Kbps. My IPads gives the same results as in Japan: the quality fluctuates and connection disconnects.
I just installed the Mountain Lion OS that allows you to use AirPlay from your Mac computer. It works great! Nice picture at about 2500 Kbps. HD looks fine on my 55 inch. There were very brief and occasional freezes but acceptable to me.
I believe the major performance consideration between the Japan and US Slingbox while remote viewing is based on the protocol used. The US Slinbox uses TCP because port-forwarding is working correctly. But the one in Japan must use UDP.
Although TCP cannot attain the same throughput as with UDP, TCP can offer the application a reliable stream of data, in order, complete and error free.
UDP does not do any of that, it merely pushes the data to the Slingplayer and the application must manage it as best as it can. The computers are able to process the data much better than the IPads because their CPU’s can likely handle the extra burden more effectively.
I’m sure if I get port-forwarding to work correctly on the Japan router, my performance will improve on the IPads. But at that point, I back to using my Slingcatcher with the IPad as an option.
Now for your issue:
I believe the link you provided shows how to set up a router for port-forwarding.
We're you successful in that effort? Or like me, after configuration, you were not able to remotely view from any device?
For more regarding TCP and UDP:
May 24, 2011
Hallo…here’s what I’ve noticed. Sometimes the remoteside showed me "SNATT" and after a slingboxreboot it became "TCP"!
Found out when my router (D-Link DWR-923) timerreboots (power off/on) it will take ca. 4 minutes to be back online again. Under this time the slingbox looses the connection too of course, but under this routerreboot it quickly shows me the networklight again before the router comletet it´s reboot. So, my Solo never had a chance to recognize the portforwarding-configuration and shows me "SNATT". To get back to "TCP" I have to shortreset the slingbox or to make another setup within the slingplayer.
The question is… what gives the best performance (stability), "Snatt" or "TCP" and if "TCP", what solution do You recommend to get it work from the remoteside… maybe another timer for the slingbox with a later timesetting?
I use a timer because I don´t trust my router and the 4G-LTE network yet and want to be shure to be online even when I am on holidays in Spain.
July 17, 2012
It's interesting that you used a timer to periodically power on/off your router. I suspecting it’s the type normally used to control a lamp etc… That’s a great idea if you don’t have confidence in your router! You just wait and the problem is eventually resolved?
Here is what I think is going on: When your router reboots, your Slingbox loses its Ethernet link. That condition will likely cause your Slingbox to perform certain tasks once the link has recovered.
I think you are correct in your observation that your router is not yet fully functional before the Slingbox link becomes active. Once the Slingbox thinks his connection has been re-enabled, he likely will try to register with Sling resources on the Internet without delay. I’m guessing your Slingbox is suffering from not completing these conditional tasks in a timely manner.
For the situation you described, I don’t believe the protocol is the issue. Try this: Install an external switch (not a router) between your existing router and your Slingbox. Do not connect this switch to a timer. Then when your router reboots, your Slingbox will NOT lose his Ethernet connection. Of course, it will temporarily have no Internet access but guessing that will not cause your Slingbox to behave in the same manner. Hopefully, it can withstand the brief outage without the need of a reset or re-config.
May 24, 2011
Thank You very much for Your answer! Your solution maybe is a better one, but now I already put another cheap timer between the slingbox and the router with a later timesetting. So, the box now reboots after the router has finnished it´s resetting and it´s working…Stream Type = TCP!
But I still don´t know if "SNATT" or "TCP" is the best choice to get a stable streaming to/in Spain?
Just now my friend has problems over there to stay connected, but that could be another reason! The streaming breaks up after only some minutes, although I have an 9 Mbit/s uploadrate and she has 6 Mbit/s in downloading! That should be more than enough, but I still can´t understand where to search/find her problems. Was in her laptop with "TeamViewer"… can´t see any unusual settings.
I changed the powersupply and even the capacitors inside my Solobox, then tried out everything with my laptop through a different provider/network…works just fine without any hiccups att all.
I am still banned from the slingforum, but I´ve read all those usual standardanswers from their moderators. I don´t think many of these new people are up to date and can give relevant hints or solutions…the setup within the webplayer and Firefox 15.02b f.ex. is not working and the supportpage shows me totaly wrong IP-adresses. Could this be the reason for the streamingfailure in Spain? Don´t think so either, cause I had no problems with my laptop from an out-of-house-connection.
Okay, I will check her issues when I´m down for my "holidays"…could be everything between heaven and earth.
Sorry for my poor english! Greetings from Sweden!
July 17, 2012
In general, I believe that TCP would provide better stability.
That said it would be a mistake to say this is always true. I’m not an expert on Slingbox but I do have experience in analyzing network performance. There many factors outside of the protocol which may be responsible for poor performance.
After connecting to my Slingbox, my Slingplayer shows the bit rate increasing slowly. Since you say the stream breaks up after some minutes, could it be related to the bit rate? If you have your Slingplayer set to auto, you may want to experiment with the quality setting. You may find stability at a lower setting.
Additionally, I’m beginning to observe performance variations on different devices on the same remote network. As in my previous post, I noticed I get a very stable connection when using my computer, but my IPad freezes and drops after some time.
By the way, I don't believe the IP address on the support page is of any consequence. I noticed my IP address and name are incorrect but it works fine.
Enjoy your vacation.