My problems have to do with getting 2 Slingboxe Pros in different locations to stream to a Slingcatcher at a third location. Soft and hard resets of the Slingcatcher have not had any effect on the problems. And no, it does not appear to be a port forwarding problem, because right now, the Slingcatcher is working.
1. Every 12 hours plus 2 minutes, the internet is dropped, and the Mac computer comes back online, but the Slingcatcher does not.
2. This happened both with ADSL and fiber optic internet connections.
3. The internet provider where the Slingcatcher is located claims it is the router.
4. Dropouts seem to be a known problem with Airport Extremes, though no entries on the internet point to dropouts every 12 hours + 2 minutes--rather, those described seem to be random.
5. Trading out the Airport Extreme and substituting a different (non-Apple) router did not change the 12 hour + 2 minute dropouts.
6. For about 2 years, after each dropout, the Slingcatcher would display a message saying that there was a network error. By clicking on that message, on Slingplayer, and on the Slingbox, the Slingcatcher would come right back up.
7. For several months now, the Slingcatcher might or might not reconnect.
8. When the Slingcatcher could not connect, it was not possible to ping the static IP where one of the Slingboxes is located, nor to complete a Traceroute (but twice it did work, and still no Slingcatcher stream).
9. One time, Airport Utility couldn't find Airport Extreme, even on Rescan, but the Slingcatcher continued working
10. When the Slingcatcher cannot stream, TraceRoute seems to hang at atlas.cogentco.com servers
11. Sling seems to route through atlas.cogentco.com, because it always shows up on Traceroute whether the Slingcatcher is working or not (others IPs or websites, for example Google, take a different route).
12. Googling atlas.cogentco.com brings up numerous complaints, particularly from gamers, that there is a lag through the atlas.cogentco.com servers.
13. Restarting the Airport Extreme router by changing the DHCP licence time in the Airport Utility, often multiple times, sometimes works to get the Slingcatcher signal back, but not always.
14. It is maintained that the Sling stream must be TCP. Currently, one Slingbox cannot be reached at all with the Slingcatcher, and on Watch on Slingbox.com, the information shows that that Slingbox is streaming in Relay format.
15. However, the second Slingbox, when it is picked up by the Slingcatcher, appears to be streaming Relay also.
16. Having Slingmedia help with setting up the Slingbox streaming through a static IP again, including the port forwarding, has not helped.
So what is the problem, and how can I fix it??? Any help will be truly appreciated!