0 Replies Latest reply: Oct 6, 2014 6:20 AM by PG3575 RSS

    W109 response

    PG3575

      Hi,

       

      Have a Pro-HD slingbox that I'm able to view fine when not on my work corporate network, but get the following message when trying to view the output on the corporate network:

       

      "We detected very poor Internet connectivity or a loss of Internet connection. Please verify that your Internet connectivity is working fine before retrying."

       

      All other websites resolve OK, and the rest of the sling website reolves OK, just the embedded video player that fails with this error. This happens on Chrome, Firefox and IE browsers on Windows 7 OS.

       

      Our corp firewall is allowing all traffic to and from  analytics.sling.com and newwatch.slingbox.com on ports 5001, 5002, 8080, or 443 as previously advised by a another question I asked. But I'm still getting the  above message and not the video stream in the browser.

       

      Some example http headers in case this helps:

       

      Initial request:

      GET /analytics.gif?table_name=watch&uiAnalyticsEvent=onWatchStart&appname=MAINWATCH&app_version=4.1.2.1g&local_event_begin_time=Mon%20Oct%2006%202014%2014:01:08%20GMT+0100%20(GMT%20Daylight%20Time)&finder_id=DD24B09DB41F1242834E7A956D9D87C9&product_id=8&plugin_session_id=NAV&box_session_id=NAV&session_id=440043be-716b-45d4-8010-ede4e8fef5e9&user_type=admin&browser=chrome&browser_version=37&OS=win&env=prod&flashEnabled=NAV¤t_locale=en_UK&flashVersion=NAV&wbsp_version=2.4.0.63&analyticsType=transition&startState=connecting&nextState=connecting&rnd=0.4145677948836237 HTTP/1.1

      Host: analytics.sling.com

      Accept: image/webp,*/*;q=0.8

      Accept-Encoding: gzip,deflate,sdch

      Accept-Language: en-US,en;q=0.8,en-GB;q=0.6

      Cookie: slingboxLocale=en_UK; sacticket=e6542b98-a168-41ea-9a40-bcc3a3fb6f58-prod; sacidentity=6184004; BCSI-CS-11aba555c86f05d5=2

      DNT: 1

      Referer: http://newwatch.slingbox.com/?ticket=e6542b98-a168-41ea-9a40-bcc3a3fb6f58-prod

      User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36

       

      Initial response

      HTTP/1.1 200 OK

      Age: 0

      Connection: Keep-Alive

      Content-Length: 43

      Content-Type: image/gif

      Date: Mon, 06 Oct 2014 13:01:08 GMT

      Last-Modified: Mon, 28 Sep 1970 06:00:00 GMT

      Proxy-Connection: Keep-Alive

      Server: nginx/1.5.8

       

      Follow up request (with 109 error):

      GET /analytics.gif?table_name=watch&uiAnalyticsEvent=onWBSPError&appname=MAINWATCH&app_version=4.1.2.1g&local_event_begin_time=Mon%20Oct%2006%202014%2014:04:44%20GMT+0100%20(GMT%20Daylight%20Time)&finder_id=DD24B09DB41F1242834E7A956D9D87C9&product_id=8&plugin_session_id=NAV&box_session_id=NAV&session_id=440043be-716b-45d4-8010-ede4e8fef5e9&user_type=admin&browser=chrome&browser_version=37&OS=win&env=prod&flashEnabled=NAV¤t_locale=en_UK&flashVersion=NAV&wbsp_version=2.4.0.63&analyticsType=transition&startState=connecting&nextState=connecting&error_code=W109&wbsp_error_code=15&rnd=0.4834348279982805 HTTP/1.1

      Host: analytics.sling.com

      Accept: image/webp,*/*;q=0.8

      Accept-Encoding: gzip,deflate,sdch

      Accept-Language: en-US,en;q=0.8,en-GB;q=0.6

      Cookie: slingboxLocale=en_UK; sacticket=e6542b98-a168-41ea-9a40-bcc3a3fb6f58-prod; sacidentity=6184004; BCSI-CS-11aba555c86f05d5=2

      DNT: 1

      Referer: http://newwatch.slingbox.com/?ticket=e6542b98-a168-41ea-9a40-bcc3a3fb6f58-prod

      User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36

       

      Follow up response:

      HTTP/1.1 200 OK

      Age: 0

      Connection: Keep-Alive

      Content-Length: 43

      Content-Type: image/gif

      Date: Mon, 06 Oct 2014 13:04:46 GMT

      Last-Modified: Mon, 28 Sep 1970 06:00:00 GMT

      Proxy-Connection: Keep-Alive

      Server: nginx/1.5.8

       

       

      Can you advise why I'm getting this W109 error?

       

      Are there any other domains/subdomains that need allowing access for the service to work?

       

      Any help appreciated.

       

      Many thanks

      Paul