NBL.tv Streaming Issues

Connection issues, drop outs or speed related faults for ADSL and ADSL2+ services
Post Reply
ErocK
Posts: 111
Joined: Sun Sep 12, 2004 7:55 pm

NBL.tv Streaming Issues

Post by ErocK » Fri Nov 01, 2013 8:58 pm

I'm having some issues streaming live games from NBL.tv

I have no issues streaming NBA League Pass, you would think that it'd be even better for a service provided in Australia.

I did a tracert and things just don't look right:

Code: Select all

Tracing route to nbl.tv [184.72.43.105]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    30 ms    32 ms    30 ms  210.8.96.58.static.exetel.com.au [58.96.8.210]
  4    34 ms    35 ms    32 ms  129.6.96.58.static.exetel.com.au [58.96.6.129]
  5    32 ms    31 ms    31 ms  161.43.102.1
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    33 ms    34 ms    34 ms  59.154.57.12
 11   152 ms   146 ms   146 ms  syd-brdr-02.inet.qwest.net [63.146.27.141]
 12     *        *        *     Request timed out.
 13   219 ms   219 ms   220 ms  65.113.42.246
 14   190 ms   191 ms   191 ms  205.251.229.179
 15   190 ms   191 ms   191 ms  205.251.229.233
 16   191 ms   198 ms     *     216.182.236.75
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
Any ideas what could be wrong?

User avatar
lasithah
Exetel Staff
Posts: 235
Joined: Mon Sep 05, 2011 5:42 pm
Location: Australia

Re: NBL.tv Streaming Issues

Post by lasithah » Fri Nov 01, 2013 9:28 pm

Hi EroK,

The trace routes will not mean anything if it is not getting completed. I will check whether there could be any issues with the service that maybe contributing to this and will email you with the findings. :)

User avatar
Dazzled
Volunteer Site Admin
Posts: 6002
Joined: Mon Nov 13, 2006 1:16 pm
Location: Sydney

Re: NBL.tv Streaming Issues

Post by Dazzled » Fri Nov 01, 2013 9:48 pm

Windows is your problem. The traceroute completes to 184.72.43.105 if you send TCP packets:

Code: Select all

$ sudo traceroute -T 184.72.43.105
traceroute to 184.72.43.105 (184.72.43.105), 30 hops max, 40 byte packets
 1  Gate.home (192.168.1.1)  2.139 ms  2.502 ms  2.866 ms
 2  * * *
 3  220.8.96.58.static.exetel.com.au (58.96.8.220)  38.231 ms  40.062 ms  41.248 ms
 4  129.6.96.58.static.exetel.com.au (58.96.6.129)  46.306 ms  48.545 ms  48.842 ms
 5  161.43.102.1 (161.43.102.1)  50.384 ms  50.831 ms  52.358 ms
 6  * * *
 7  * * *
 8  * * *
 9  59.154.57.10 (59.154.57.10)  32.835 ms  33.150 ms  34.392 ms
10  59.154.57.12 (59.154.57.12)  35.416 ms 59.154.57.14 (59.154.57.14)  32.747 ms syd-brdr-02.inet.qwest.net (63.146.27.141)  140.740 ms
11  syd-brdr-02.inet.qwest.net (63.146.27.141)  142.525 ms * *
12  * * *
13  205.251.229.179 (205.251.229.179)  194.835 ms 65.113.42.250 (65.113.42.250)  256.600 ms
65.113.42.246 (65.113.42.246)  225.817 ms
14  205.251.229.233 (205.251.229.233)  197.412 ms 205.251.229.179 (205.251.229.179)  199.782 ms
205.251.229.233 (205.251.229.233)  200.921 ms
15  205.251.229.233 (205.251.229.233)  203.500 ms  204.931 ms  224.411 ms
16  216.182.236.111 (216.182.236.111)  207.410 ms 216.182.236.75 (216.182.236.75)  209.865 ms 216.182.236.99 (216.182.236.99)  210.381 ms
17  * * *
18  ec2-184-72-43-105.us-west-1.compute.amazonaws.com (184.72.43.105)  191.939 ms  195.867 ms  193.517 ms
$ 


However, if we use the Exetel DNS, we get a better result

Code: Select all

$ sudo traceroute -T www.nbl.tv
traceroute to www.nbl.tv (220.233.2.210), 30 hops max, 40 byte packets
 1  Gate.home (192.168.1.1)  1.137 ms  1.473 ms  1.818 ms
 2  * * *
 3  212.8.96.58.static.exetel.com.au (58.96.8.212)  38.762 ms  39.175 ms  40.782 ms
 4  129.6.96.58.static.exetel.com.au (58.96.6.129)  42.211 ms  43.333 ms  46.067 ms
 5  www.nbl.tv (220.233.2.210)  47.151 ms  49.090 ms  50.124 ms

ErocK
Posts: 111
Joined: Sun Sep 12, 2004 7:55 pm

Re: NBL.tv Streaming Issues

Post by ErocK » Fri Nov 01, 2013 10:28 pm

^^

I'm not sure what you mean by this.

User avatar
Dazzled
Volunteer Site Admin
Posts: 6002
Joined: Mon Nov 13, 2006 1:16 pm
Location: Sydney

Re: NBL.tv Streaming Issues

Post by Dazzled » Fri Nov 01, 2013 10:46 pm

If I look up nbl.tv from the Google name server using the DNS tool dig, I get:
$dig @8.8.8.8 nbl.tv
....
;; ANSWER SECTION:
nbl.tv. 599 IN A 184.72.43.105


That is the IP you tried to traceroute. It didn't complete only because Windows tracert is deficient. Using a Linux trace and not sending ICMP packets I got all the way.

But for a service provided in Australia, I queried the Exetel server, and got a more interesting result:
$ dig @220.233.0.4 www.nbl.tv

; <<>> DiG 9.4.2-P2.1 <<>> @220.233.0.4 www.nbl.tv
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1743
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 8, ADDITIONAL: 8

;; QUESTION SECTION:
;www.nbl.tv. IN A

;; ANSWER SECTION:
www.nbl.tv. 30 IN CNAME www.nbltv.performgroup.com.edgesuite.net.
www.nbltv.performgroup.com.edgesuite.net. 17332 IN CNAME a1254.g2.akamai.net.
a1254.g2.akamai.net. 20 IN A 220.233.2.210
a1254.g2.akamai.net. 20 IN A 220.233.2.203

;; AUTHORITY SECTION:
g2.akamai.net. 16585 IN NS n0g2.akamai.net.
g2.akamai.net. 16585 IN NS n7g2.akamai.net.
g2.akamai.net. 16585 IN NS n6g2.akamai.net.
g2.akamai.net. 16585 IN NS n5g2.akamai.net.
g2.akamai.net. 16585 IN NS n2g2.akamai.net.
g2.akamai.net. 16585 IN NS n4g2.akamai.net.
g2.akamai.net. 16585 IN NS n3g2.akamai.net.
g2.akamai.net. 16585 IN NS n1g2.akamai.net.

;; ADDITIONAL SECTION:
n0g2.akamai.net. 16897 IN A 220.233.2.199
n1g2.akamai.net. 25363 IN A 88.221.81.194
n2g2.akamai.net. 26376 IN A 203.206.129.51
n3g2.akamai.net. 3377 IN A 203.206.129.53
n4g2.akamai.net. 31757 IN A 220.233.2.199
n5g2.akamai.net. 24100 IN A 203.206.129.53
n6g2.akamai.net. 16533 IN A 220.233.2.204
n7g2.akamai.net. 25363 IN A 203.206.129.52

;; Query time: 36 msec
;; SERVER: 220.233.0.4#53(220.233.0.4)
;; WHEN: Fri Nov 1 22:39:56 2013
;; MSG SIZE rcvd: 424

Note the alias -- the site is actually located on a fast Akamai server with an Exetel address, which should give excellent results if your computer uses the Exetel DNS. Otherwise check you included the www

Post Reply