11 Replies Latest reply: Jul 3, 2013 2:15 PM by timcowell RSS

    Viewing with IE10 and Firefox 21 stopped working.

    timcowell

      The hardware seems fine because the legacy viewer software works ok.

      I noticed the web site access was bit slow also. I checked my connection and that works fine.

       

      TBH this is what I was afraid of with this device, it needs internet access even for local viewing within my home network.

      I suggest you update your local player software so that local veiwing can be done at the same quality without the need for internet access.

        • Re: Viewing with IE10 and Firefox 21 stopped working.
          Tyler.Sling Novice

          Hello timcowell,

           

          Thanks for posting in the answers forums! I'm sorry to hear you are no longer able to connect to your Slingbox via IE10 and Firefox 21.

           

          Have you tried uninstalling and reinstalling the plug-in to either of these browsers. That usually resolves most issues with the plug-in. If that does not work, could you respond telling me what errors you are getting when you try to connect in both web browsers?

           

          Below is a link to an article that explains how to install and uninstall the plug-in for both Internet Explorer and Firefox:

           

           

          Hope this helps!

           

          Best regards,

          The Sling Moderation Team

          • Re: Viewing with IE10 and Firefox 21 stopped working.
            timcowell

            Did some random ping test:

             

            Microsoft Windows [Version 6.2.9200]
            (c) 2012 Microsoft Corporation. All rights reserved.

            C:\Windows\system32>ping slingbox.com

            Pinging slingbox.com [67.148.153.146] with 32 bytes of data:
            Reply from 67.148.153.146: bytes=32 time=137ms TTL=49
            Reply from 67.148.153.146: bytes=32 time=138ms TTL=49
            Reply from 67.148.153.146: bytes=32 time=138ms TTL=49
            Reply from 67.148.153.146: bytes=32 time=136ms TTL=49

            Ping statistics for 67.148.153.146:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            Approximate round trip times in milli-seconds:
                Minimum = 136ms, Maximum = 138ms, Average = 137ms

            C:\Windows\system32>ping plugin.slingbox.com

            Pinging a1961.b.akamai.net [77.67.96.175] with 32 bytes of data:
            Reply from 77.67.96.175: bytes=32 time=30ms TTL=54
            Reply from 77.67.96.175: bytes=32 time=34ms TTL=54
            Reply from 77.67.96.175: bytes=32 time=33ms TTL=54
            Reply from 77.67.96.175: bytes=32 time=30ms TTL=54

            Ping statistics for 77.67.96.175:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            Approximate round trip times in milli-seconds:
                Minimum = 30ms, Maximum = 34ms, Average = 31ms

            C:\Windows\system32>ping slingmedia.com

            Pinging slingmedia.com [8.7.94.70] with 32 bytes of data:
            Reply from 8.7.94.70: bytes=32 time=143ms TTL=236
            Reply from 8.7.94.70: bytes=32 time=145ms TTL=236
            Reply from 8.7.94.70: bytes=32 time=142ms TTL=236
            Reply from 8.7.94.70: bytes=32 time=143ms TTL=236

            Ping statistics for 8.7.94.70:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            Approximate round trip times in milli-seconds:
                Minimum = 142ms, Maximum = 145ms, Average = 143ms

            C:\Windows\system32>ping sling.com

            Pinging sling.com [174.129.23.207] with 32 bytes of data:
            Request timed out.
            Request timed out.
            Request timed out.
            Request timed out.

            Ping statistics for 174.129.23.207:
                Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

            C:\Windows\system32>ping uk.slingbox.com

            Pinging www.slingbox.com [67.148.153.146] with 32 bytes of data:
            Reply from 67.148.153.146: bytes=32 time=138ms TTL=49
            Reply from 67.148.153.146: bytes=32 time=139ms TTL=49
            Reply from 67.148.153.146: bytes=32 time=140ms TTL=49
            Reply from 67.148.153.146: bytes=32 time=144ms TTL=49

            Ping statistics for 67.148.153.146:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            Approximate round trip times in milli-seconds:
                Minimum = 138ms, Maximum = 144ms, Average = 140ms

            C:\Windows\system32>ping newwatch.slingbox.com

            Pinging a402.b.akamai.net [77.67.96.184] with 32 bytes of data:
            Reply from 77.67.96.184: bytes=32 time=36ms TTL=54
            Reply from 77.67.96.184: bytes=32 time=34ms TTL=54
            Reply from 77.67.96.184: bytes=32 time=33ms TTL=54
            Reply from 77.67.96.184: bytes=32 time=31ms TTL=54

            Ping statistics for 77.67.96.184:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
            Approximate round trip times in milli-seconds:
                Minimum = 31ms, Maximum = 36ms, Average = 33ms

            C:\Windows\system32>

             

            sling.com not working, is this needed for the web player to work?

              • Re: Viewing with IE10 and Firefox 21 stopped working.
                test350 Novice

                Ping is often a meaningless test, because an otherwise functioning and reachable host may block it for security reasons, or give it lowest priority so more resources are available for real traffic.

                 

                If you suspect that a problem with your network or your ISP is preventing the Web player from working, use Wireshark to determine what the player is trying to access when it hangs.  To make sure that you see all the lookups, close all browser windows and do

                ipconfig /flushdns

                before starting the capture and opening your browser.  A quick test with Firefox shows these DNS lookups:

                 

                newwatch.slingbox.com

                newwatchsecure.slingbox.com

                plugin.slingbox.com

                ocsp.digicert.com (possibly from another app)

                accounts.sling.com

                www.slingbox.com

                countryselect.slingbox.com

                support.slingbox.com

                watchhelpus.slingbox.com

                www.slingmedia.com

                services.sling.com

                analytics.sling.com

                sparcs.sling.com

                hbt.sling.com

                 

                (The name sling.com is not looked up.)

              • Re: Viewing with IE10 and Firefox 21 stopped working.
                timcowell

                Ok back to working now, let's see how long it lasts.