57 Replies Latest reply: May 4, 2011 11:56 AM by chakkarinen RSS

    Unable to detect internet connection

    pac33 Newbie

      I have a Dell laptop using Windows XP.  My Slingplayer has worked in the past overseas until lately it is now saying it can't connect to my slingbox, there's no internet connection and so forth.  Any ideas?

        • Re: Unable to detect internet connection
          eferz Expert

          If you're using Slingplayer 2.0 it could be an issue with DNS resolution or connection issue.

           

           

          analytics.sling.com

          autoupdate.sling.com

          ms.sling.com

          secure.sling.com

          services.sling.com

          sparcs.slingmedia.com

           

          I would recommend pinging each of above addresses to make sure you have connectivity.

          example, "ping services.sling.com"

           

          Then I would recommend doing a nslookup for each of the addresses

          example, "nslookup services.sling.com"

           

          ...and then compare your results by checking with this site (http://www.ipchecking.com)

           

          Esentially, we want to make sure that you can connect to the respective server, and that it is not being misdirected or blocked somehow.

            • Re: Unable to detect internet connection
              pac33 Newbie

              When I pinged all your suggestions I was taken to a Google search results page in which the first link was to the slingbox forum.  Is this ok or a bad misdirection?

               

              Still having same problmes and cannot connect.  Getting error: 0x8007274C

               

              Please continue to help.  I leave for S.E. Asia in less than 48 hours and I really need this working.

                • Re: Unable to detect internet connection
                  eferz Expert

                  I'm sorry, you have to do this in the command prompt.

                   

                  (Start | Accessories | Command Prompt )

                   

                  cmd.jpg

                   

                  So, in the above screenshot, I pinged services.sling.com but I didn't get a response from services.sling.com.

                   

                  That gets me worried, a699.b.akamai.net (206.0.59.74) is responding instead of the services.sling.com

                   

                  So, I use nslookup to hopefully figure out why....

                   

                  I then see that a699.b.akamai.net is an alias for services.sling.com and that might be cool.

                   

                  You can further verify the information from (http://www.ipchecking.com/)

                    • Re: Unable to detect internet connection
                      pac33 Newbie

                      Here are the results:

                      Microsoft Windows XP [Version 5.1.2600]
                      (C) Copyright 1985-2001 Microsoft Corp.

                       

                      F:\>C:

                       

                      C:\>ping services.sling.com

                       

                      Pinging services.sling.com [69.31.116.129] with 32 bytes of data:

                       

                      Reply from 69.31.116.129: bytes=32 time=58ms TTL=58
                      Reply from 69.31.116.129: bytes=32 time=56ms TTL=58
                      Reply from 69.31.116.129: bytes=32 time=70ms TTL=58
                      Reply from 69.31.116.129: bytes=32 time=58ms TTL=58

                       

                      Ping statistics for 69.31.116.129:
                          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                      Approximate round trip times in milli-seconds:
                          Minimum = 56ms, Maximum = 70ms, Average = 60ms

                       

                       

                      So, what next?

                        • Re: Unable to detect internet connection
                          eferz Expert

                          All of them (both ping and nslookup) for each of the URLs below.

                           

                          analytics.sling.com

                          autoupdate.sling.com

                          ms.sling.com

                          secure.sling.com

                          services.sling.com

                          sparcs.slingmedia.com

                           

                          I would  recommend pinging each of above addresses to make sure you have  connectivity.

                          example, "ping services.sling.com"

                           

                          Then I would  recommend doing a nslookup for each of the addresses

                          example,  "nslookup services.sling.com"

                           

                          ...and then compare your results by checking  with this site (http://www.ipchecking.com)

                           

                          Esentially,  we want to make sure that you can connect to the respective server, and  that it is not being misdirected or blocked somehow.

                          • Re: Unable to detect internet connection
                            eferz Expert

                            pac33 wrote:

                             

                            C:\>ping services.sling.com

                             

                            Pinging services.sling.com [69.31.116.129] with 32 bytes of data:

                             

                            Reply from 69.31.116.129: bytes=32 time=58ms TTL=58
                            Reply from 69.31.116.129: bytes=32 time=56ms TTL=58
                            Reply from 69.31.116.129: bytes=32 time=70ms TTL=58
                            Reply from 69.31.116.129: bytes=32 time=58ms TTL=58

                             

                            Ping statistics for 69.31.116.129:
                                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                            Approximate round trip times in milli-seconds:
                                Minimum = 56ms, Maximum = 70ms, Average = 60ms

                             

                             

                            So, what next?

                             

                            uhh... do a nslookup with that address and give me your results.  It looks like you're being hijacked.

                             

                            dns.jpg

                            It doesn't appear to be a Slingbox affilate.

                            • Re: Unable to detect internet connection
                              pac33 Newbie

                              Microsoft Windows XP [Version 5.1.2600]

                              (C) Copyright 1985-2001 Microsoft Corp.

                               

                              F:\>C:

                               

                              C:\>ping analytics.sling.com

                               

                              Pinging analytics.sling.com [70.42.244.146] with 32 bytes of data:

                               

                              Reply from 70.42.244.146: bytes=32 time=68ms TTL=244
                              Reply from 70.42.244.146: bytes=32 time=119ms TTL=244
                              Reply from 70.42.244.146: bytes=32 time=78ms TTL=244
                              Reply from 70.42.244.146: bytes=32 time=59ms TTL=244

                               

                              Ping statistics for 70.42.244.146:
                                  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                              Approximate round trip times in milli-seconds:
                                  Minimum = 59ms, Maximum = 119ms, Average = 81ms

                               

                              C:\>ping autoupdate.sling.com

                               

                              Pinging autoupdate.sling.com [69.31.116.106] with 32 bytes of data:

                               

                              Reply from 69.31.116.106: bytes=32 time=62ms TTL=58
                              Reply from 69.31.116.106: bytes=32 time=58ms TTL=58
                              Reply from 69.31.116.106: bytes=32 time=59ms TTL=58
                              Reply from 69.31.116.106: bytes=32 time=58ms TTL=58

                               

                              Ping statistics for 69.31.116.106:
                                  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                              Approximate round trip times in milli-seconds:
                                  Minimum = 58ms, Maximum = 62ms, Average = 59ms

                               

                              C:\>ping ms.sling.com

                               

                              Pinging ms.sling.com [70.42.244.150] with 32 bytes of data:

                               

                              Reply from 70.42.244.150: bytes=32 time=63ms TTL=244
                              Reply from 70.42.244.150: bytes=32 time=65ms TTL=244
                              Reply from 70.42.244.150: bytes=32 time=59ms TTL=244
                              Reply from 70.42.244.150: bytes=32 time=62ms TTL=244

                               

                              Ping statistics for 70.42.244.150:
                                  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                              Approximate round trip times in milli-seconds:
                                  Minimum = 59ms, Maximum = 65ms, Average = 62ms

                               

                              C:\>ping secure.sling.com

                               

                              Pinging secure.sling.com [70.42.244.144] with 32 bytes of data:

                               

                              Reply from 70.42.244.144: bytes=32 time=65ms TTL=244
                              Reply from 70.42.244.144: bytes=32 time=59ms TTL=244
                              Reply from 70.42.244.144: bytes=32 time=63ms TTL=244
                              Reply from 70.42.244.144: bytes=32 time=58ms TTL=244

                               

                              Ping statistics for 70.42.244.144:
                                  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                              Approximate round trip times in milli-seconds:
                                  Minimum = 58ms, Maximum = 65ms, Average = 61ms

                               

                              C:\>ping services.sling.com

                               

                              Pinging services.sling.com [69.31.116.129] with 32 bytes of data:

                               

                              Reply from 69.31.116.129: bytes=32 time=58ms TTL=58
                              Reply from 69.31.116.129: bytes=32 time=63ms TTL=58
                              Reply from 69.31.116.129: bytes=32 time=76ms TTL=58
                              Reply from 69.31.116.129: bytes=32 time=64ms TTL=58

                               

                              Ping statistics for 69.31.116.129:
                                  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                              Approximate round trip times in milli-seconds:
                                  Minimum = 58ms, Maximum = 76ms, Average = 65ms

                               

                              C:\>ping sparcs.slingmedia.com

                               

                              Pinging sparcs.slingmedia.com [70.42.244.147] with 32 bytes of data:

                               

                              Reply from 70.42.244.147: bytes=32 time=64ms TTL=244
                              Reply from 70.42.244.147: bytes=32 time=71ms TTL=244
                              Reply from 70.42.244.147: bytes=32 time=62ms TTL=244
                              Reply from 70.42.244.147: bytes=32 time=74ms TTL=244

                               

                              Ping statistics for 70.42.244.147:
                                  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
                              Approximate round trip times in milli-seconds:
                                  Minimum = 62ms, Maximum = 74ms, Average = 67ms

                               

                              C:\>

                                • Re: Unable to detect internet connection
                                  pac33 Newbie

                                  Microsoft Windows XP [Version 5.1.2600]
                                  (C) Copyright 1985-2001 Microsoft Corp.

                                   

                                  F:\>C:

                                   

                                  C:\>nslookup services.sling.com
                                  Server:  etisrv.etitulsa.com
                                  Address:  192.168.131.2

                                   

                                  Non-authoritative answer:
                                  Name:    a699.b.akamai.net
                                  Addresses:  98.174.28.49, 98.174.28.83
                                  Aliases:  services.sling.com, services.sling.com.edgesuite.net

                                   


                                  C:\>nslookup analystics.sling.com
                                  Server:  etisrv.etitulsa.com
                                  Address:  192.168.131.2

                                   

                                  *** etisrv.etitulsa.com can't find analystics.sling.com: Non-existent domain

                                   

                                  C:\>nslookup autoupdate.sling.com
                                  Server:  etisrv.etitulsa.com
                                  Address:  192.168.131.2

                                   

                                  Non-authoritative answer:
                                  Name:    a691.b.akamai.net
                                  Addresses:  98.174.28.67, 98.174.28.58
                                  Aliases:  autoupdate.sling.com, autoupdate.sling.com.edgesuite.net

                                   


                                  C:\>nslookup ms.sling.com
                                  Server:  etisrv.etitulsa.com
                                  Address:  192.168.131.2

                                   

                                  Non-authoritative answer:
                                  Name:    ms.sling.com
                                  Address:  70.42.244.150

                                   


                                  C:\>nslookup analytics.sling.com
                                  Server:  etisrv.etitulsa.com
                                  Address:  192.168.131.2

                                   

                                  Non-authoritative answer:
                                  Name:    analytics.sling.com
                                  Address:  70.42.244.146

                                   


                                  C:\>nslookup secure.sling.com
                                  Server:  etisrv.etitulsa.com
                                  Address:  192.168.131.2

                                   

                                  Non-authoritative answer:
                                  Name:    secure.sling.com
                                  Address:  70.42.244.144

                                   


                                  C:\>nslookup services.sling.com
                                  Server:  etisrv.etitulsa.com
                                  Address:  192.168.131.2

                                   

                                  Non-authoritative answer:
                                  Name:    a699.b.akamai.net
                                  Addresses:  98.174.28.49, 98.174.28.83
                                  Aliases:  services.sling.com, services.sling.com.edgesuite.net

                                   


                                  C:\>nslookup sparcs.slingmedia.com
                                  Server:  etisrv.etitulsa.com
                                  Address:  192.168.131.2

                                   

                                  Non-authoritative answer:
                                  Name:    sparcs.slingmedia.com
                                  Address:  70.42.244.147

                                   


                                  C:\>

                                    • Re: Unable to detect internet connection
                                      eferz Expert

                                      These appear to be good:

                                       

                                      analytics.sling.com [70.42.244.146] (good)

                                      Pinging ms.sling.com [70.42.244.150] (good)
                                      secure.sling.com [70.42.244.144] (good)

                                      sparcs.slingmedia.com [70.42.244.147] (good)

                                       

                                      The information from http://www.ipchecking.com  is  as followed.

                                       

                                      Internap Network Services Corporation PNAP-09-2005 (NET-70-42-0-0-1) 
                                      70.42.0.0 - 70.42.255.255
                                      Sling Media, Inc. INAP-SJE-SLINGMEDIA-13498 (NET-70-42-244-0-1)
                                      70.42.244.0 - 70.42.247.255

                                      CustName:   Sling Media, Inc.
                                      Address:    1051 East Hillsdale Blvd., Suite 500
                                      City:       Foster City
                                      StateProv:  CA
                                      PostalCode: 94404
                                      Country:    US
                                      RegDate:    2007-04-06
                                      Updated:    2007-04-06

                                      NetRange:   70.42.244.0 - 70.42.247.255
                                      CIDR:       70.42.244.0/22
                                      NetName:    INAP-SJE-SLINGMEDIA-13498
                                      NetHandle:  NET-70-42-244-0-1
                                      Parent:     NET-70-42-0-0-1
                                      NetType:    Reassigned
                                      RegDate:    2007-04-06
                                      Updated:    2007-04-06

                                       

                                       

                                      However, you're being hijacked on autoupdate.sling.com and services.sling.com

                                       

                                      Notice the curtains don't match the carpet.

                                       

                                      That's to say the nslookup gives you one address, but the ping gives you another.

                                       

                                      autoupdate.sling.com [69.31.116.106] (hijacked)

                                       

                                      C:\>nslookup autoupdate.sling.com
                                      Server:  etisrv.etitulsa.com
                                      Address:   192.168.131.2

                                       

                                      Non-authoritative  answer:
                                      Name:    a691.b.akamai.net
                                      Addresses:  98.174.28.67,  98.174.28.58
                                      Aliases:  autoupdate.sling.com,  autoupdate.sling.com.edgesuite.net

                                       

                                      services.sling.com [69.31.116.129] (hijacked)

                                       

                                      C:\>nslookup services.sling.com
                                      Server:  etisrv.etitulsa.com
                                      Address:   192.168.131.2

                                       

                                      Non-authoritative  answer:
                                      Name:    a699.b.akamai.net
                                      Addresses:  98.174.28.49,  98.174.28.83
                                      Aliases:  services.sling.com,  services.sling.com.edgesuite.net

                                       

                                      It seems both of those addresses are being misdirected.

                                       

                                      The information from http://www.ipchecking.com  is as followed.

                                       

                                      OrgName:    nLayer Communications, Inc.
                                      OrgID:      NLAYE
                                      Address:    209 W. Jackson Blvd
                                      Address:    Suite 700
                                      City:       Chicago
                                      StateProv:  IL
                                      PostalCode: 60606-6936
                                      Country:    US

                                      NetRange:   69.31.0.0 - 69.31.143.255
                                      CIDR:       69.31.0.0/17, 69.31.128.0/20
                                      OriginAS:   AS4436
                                      NetName:    NLYR-ARIN-BLK2
                                      NetHandle:  NET-69-31-0-0-1
                                      Parent:     NET-69-0-0-0-0
                                      NetType:    Direct Allocation
                                      NameServer: NS1.CACHENETWORKS.COM
                                      NameServer: NS2.CACHENETWORKS.COM
                                      RegDate:    2003-03-17
                                      Updated:    2008-07-07
                                        • Re: Unable to detect internet connection
                                          pac33 Newbie

                                          Interesting, so, what do I do to correct this?

                                            • Re: Unable to detect internet connection
                                              eferz Expert

                                              Well, first lets see if we can apply a little bypass.  Just so you can get your Slingplayer working again.

                                               

                                              What you would do, is edit your "host" file and add each the IP address  to DNS name listing.  It should be in "C:\Windows\System32\drivers\etc".   If you find that the folder is blank, go to Organize Folder and Seach Options | View Tab  under Files and Folders  | Hidden files and  Folders click the radio button for Show hidden files  and folders.  You should then see five files, "hosts",  "lmhosts.sam", "networks", "protocol", and "services".  Open the "hosts"  file with notepad,  This is what the file should look like.

                                               

                                              That's what it should look like.

                                               

                                              host-orig.jpg

                                               

                                              We want to append two lines at the bottom.

                                               

                                              "98.174.28.49 services.sling.com
                                              98.174.28.67 autoupdate.sling.com"

                                               

                                              This what it will look like

                                               

                                              host-new.jpg

                                               

                                              This will make windows use the above addresses when referring to one of the respective URLs.

                                                • Re: Unable to detect internet connection
                                                  pac33 Newbie

                                                  # Copyright (c) 1993-1999 Microsoft Corp.
                                                  #
                                                  # This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
                                                  #
                                                  # This file contains the mappings of IP addresses to host names. Each
                                                  # entry should be kept on an individual line. The IP address should
                                                  # be placed in the first column followed by the corresponding host name.
                                                  # The IP address and the host name should be separated by at least one
                                                  # space.
                                                  #
                                                  # Additionally, comments (such as these) may be inserted on individual
                                                  # lines or following the machine name denoted by a '#' symbol.
                                                  #
                                                  # For example:
                                                  #
                                                  #      102.54.94.97     rhino.acme.com          # source server
                                                  #       38.25.63.10     x.acme.com              # x client host

                                                   

                                                  127.0.0.1       localhost

                                                   

                                                  98.174.28.49    services.sling.com
                                                  98.174.28.67    autoupdate.sling.com

                                                   

                                                   

                                                   

                                                  Ok, I got it in.  Verify that this is correct.  I will try connecting in the meantime.

                                • Re: Unable to detect internet connection
                                  pac33 Newbie

                                  Need help again.

                                    • Re: Unable to detect internet connection
                                      pac33 Newbie

                                      Somebody, I need help again.  I've had a good connection for the last 4 weeks.  No issues, great connection and then it just stops connecting.  HELP!

                                        • Re: Unable to detect internet connection
                                          igolf4fun

                                          Same issue, had been working fine now cant get connection. Power light on no network light. Attempted to reset hold for 5 seconds still no network light, na da nothing.

                                           

                                          Thanks

                                            • Re: Unable to detect internet connection
                                              chakkarinen Apprentice

                                              I don't know if this answer will  help you or not.  But I also started having problems connecting to my  Slingbox (located about 1,000 miles away from my primary residence  inside my second home) about 3 months after I installed it.   I would  get error messages that Sling Player on my laptop computer could not  connect, but I could connect when I was physically inside the second  home.

                                               

                                              I think the fundamental problem may be that your Slingbox is not being assigned a static IP address by your router.   Without a static IP address, your Slingbox could get assigned a new IP address at some future time by your router.   This is most likely to occur if, for example, you have a power outage in your home.   When the power comes back on, your router will re-assign IP addresses to all devices in its network, and your Slingbox may be given a different address than before.   Assigning a static IP address to the Slingbox assures that it will always have the same IP address whenever your router (or Slingbox) gets reboooted.

                                               

                                              To solve my problem, I  finally decided to assign a static IP address to my Slingbox, following  the instructions that came with my router, and then forwarding the port  number 5001 to that static IP address (also following the instructions  that came with my router).   I made these changes last week while  visiting the second home -- for security reasons, I have set up the  router in my second home so that it can be logged in to ONLY when inside  the second home's local area network.   After that, connections between  the laptop computer and the Slingbox have worked great, and the speed  of transfer seems even to have improved somewhat.   And I verified that  the laptop's Sling Player worked well when connecting from other  locations in the neighborhood of the Slingbox -- such as the free Wi-Fi  at the local Mickey D's and grocery store.

                                               

                                              Now  that I back at my primary residence 1000 miles away, I have verified  that the Slingbox connection works for all of my other computers in my  home -- although not on the first try for some.   In those cases, I had  to re-enter my login ID and password, but then the Slingbox immediately  appeared as an option, and once I clicked the "Connect" choice on the  dropdown menu, I was back in business with THAT computer, and  connections have been maintained since.

                                               

                                              The  next test will be when electrical outages from the frequent summer  thunderstorms at the second home begin to happen, and whether the remote  connection to the Slingbox can be easily restored after each such  outage.