Youtube Not Fully Buffering

Forums › Snap › Youtube Not Fully Buffering

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16

96 posts

Master Geek

Reply # 593848 12-Mar-2012 06:34
AviZ: changed to google dns servers and change the same server in my router bang youtube is now working flawless without buffering Can you please provide a traceroute to cache.l.google.com while using google dns?

networkn

4757 posts

Uber Geek

Trusted

Subscriber

Reply # 593972 12-Mar-2012 10:42
Hi, I am not with Snap, so please excuse my intrusion, but I am having identical problems with my Youtube. I can barely watch a 360p video let alone a 720P, as the speed that it's buffering doesn't keep up with the watching speed. I am with Unleash who have been trying to find the problem. I can watch the same video fine on my phone (VF) or using my ADSL2+ connection at the office and it's buffering super quickly. Seems like some video's are ok, others not so much! I am wondering how I can troubleshoot the problem? I am confident it's not an issue with my PC since I have the same problems on my tablet etc as well. How can I tell which cache my browser is pulling content from when I play videos? Is there a way to hard code to use a specific cache? Is it possible that Unleash are using Snap Caches?

frizianz

96 posts

Master Geek

Reply # 593987 12-Mar-2012 11:06
networkn: How can I tell which cache my browser is pulling content from when I play videos? Is there a way to hard code to use a specific cache? Youtube will do a DNS lookup for cache.l.google. From here the server which is deemed to be closest will be used. This is why Mark has asked for people to provide trace routes to cache.l.google.com as this shows which server it is downloading from and the route there.

networkn

4757 posts

Uber Geek

Trusted

Subscriber

Reply # 593990 12-Mar-2012 11:14
Tracing route to cache.l.google.com [202.124.127.27] over a maximum of 30 hops: 1 2 4 ms 4 ms 4 ms dsl-inet-static-116-90-136-0-25.dsl.unleash.net. nz [116.90.136.126] 3 7 ms 8 ms 8 ms ge-0-0-1-3.rt-1.fed.akl.unleash.net.nz [116.90.1 28.225] 4 8 ms 9 ms 10 ms ge-0-0-0-6.rt-0.gra.akl.unleash.net.nz [116.90.1 30.107] 5 5 ms 5 ms 5 ms snap.ape.net.nz [192.203.154.120] 6 20 ms 21 ms 23 ms 44.17.69.111.static.snap.net.nz [111.69.17.44] 7 26 ms 23 ms 23 ms 45.17.69.111.static.snap.net.nz [111.69.17.45] 8 21 ms 21 ms 22 ms 27.127.124.202.static.snap.net.nz [202.124.127.2 7] Trace complete. Seems to indicate the problem might be the cache server perhaps? For Comparisons sakes: From my VF Connection: Tracing route to cache.l.google.com [203.109.178.26] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 26 ms 27 ms 26 ms 203.109.129.37 3 25 ms 25 ms 25 ms gi1-3.akl-grafton-bdr1.ihug.net [203.109.129.38] 4 26 ms 25 ms 25 ms unassigned.vf.net.nz [203.109.180.225] 5 38 ms 24 ms 24 ms unassigned.vf.net.nz [203.109.180.225] 6 25 ms 25 ms 25 ms 203-109-178-105.dsl.dyn.ihug.co.nz [203.109.178. 105] 7 27 ms 25 ms 25 ms 203-109-178-26.dsl.dyn.ihug.co.nz [203.109.178.2 6] Trace complete.

Napster

202 posts

Master Geek

Reply # 593993 12-Mar-2012 11:21
Snap VDSL here. Tracing route to cache.l.google.com [202.124.127.16] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1] 2 <1 ms <1 ms <1 ms 192.168.178.1 3 39 ms 37 ms 38 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 4 34 ms 34 ms 34 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54] 5 50 ms 49 ms 49 ms 46.17.69.111.static.snap.net.nz [111.69.17.46] 6 50 ms 50 ms 50 ms 47.17.69.111.static.snap.net.nz [111.69.17.47] 7 49 ms 49 ms 49 ms 16.127.124.202.static.snap.net.nz [202.124.127.1 6] Trace complete.

networkn

4757 posts

Uber Geek

Trusted

Subscriber

Reply # 594012 12-Mar-2012 11:38
Napster, are you familar with changing your hosts file? can I recommend you try adding 203.109.178.26 cache.l.google.com to your hosts file and see if that helps. Cheers

Napster

202 posts

Master Geek

Reply # 594027 12-Mar-2012 11:59
Have never played around with the hosts file. This is the location right? C:\Windows\System32\drivers\etc and do i just add "203.109.178.26 cache.l.google.com" at the bottom? EDIT: Ok so this is what i get now. Will do some testing. Cheers Network Tracing route to cache.l.google.com203.109.178.26 [203.109.178.26] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1] 2 <1 ms <1 ms <1 ms 192.168.178.1 3 34 ms 34 ms 34 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 4 41 ms 34 ms 34 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54] 5 34 ms 34 ms 34 ms UNASSIGNED-192-203-154-145.ape.net.nz [192.203.1 54.145] 6 34 ms 34 ms 34 ms lo151.ppnzsky01.akl.vf.net.nz [203.109.180.137] 7 36 ms 35 ms 35 ms cache.l.google.com203.109.178.26 [203.109.178.26 ] Trace complete.

rounder

18 posts

Geek

Reply # 594043 12-Mar-2012 12:18
Trace after changing DNS settings Tracing route to cache.l.google.com [74.125.171.39] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 11 ms 17 ms 11 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 17 ms 11 ms 10 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54] 4 11 ms 11 ms 11 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 5 11 ms 12 ms 11 ms 203.167.233.10 6 136 ms 136 ms 136 ms i-0-0-4-0.tlot-core01.bx.reach.com [202.84.142.1 18] 7 135 ms 135 ms 135 ms i-2-5.tlot03.bi.reach.com [202.84.251.242] 8 186 ms 185 ms 186 ms 72.14.197.53 9 186 ms 185 ms 234 ms 72.14.234.47 10 186 ms 198 ms 186 ms 64.233.174.186 11 185 ms 185 ms 185 ms 64.233.174.179 12 185 ms 207 ms 250 ms 209.85.255.59 13 186 ms 186 ms 186 ms 209.85.241.91 14 185 ms 185 ms 185 ms 72.14.237.41 15 186 ms 186 ms 185 ms 74.125.171.39 Trace complete. Changed back to Automatic DNS and did comparison Tracing route to cache.l.google.com [74.125.171.52] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 11 ms 11 ms 16 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 12 ms 11 ms 11 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54] 4 12 ms 11 ms 11 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 5 11 ms 11 ms 11 ms 203.167.233.10 6 137 ms 152 ms 155 ms i-0-6-4-1.tlot-core01.bx.reach.com [202.84.142.1 14] 7 136 ms 136 ms 136 ms i-1-1.tlot03.bi.reach.com [202.84.251.234] 8 210 ms 186 ms 186 ms 72.14.197.53 9 185 ms 187 ms 186 ms 72.14.234.45 10 185 ms 185 ms 187 ms 64.233.174.192 11 187 ms 186 ms 195 ms 64.233.174.177 12 253 ms 186 ms 187 ms 209.85.255.37 13 186 ms 186 ms 187 ms 209.85.241.91 14 186 ms 187 ms 187 ms 72.14.237.41 15 188 ms 188 ms 186 ms 74.125.171.52 Trace complete.

Napster

202 posts

Master Geek

Reply # 594065 12-Mar-2012 12:38
Youtube is still pulling content from Snaps cache instead of cache.l.google.com203.109.178.26. Did i miss something?

networkn

4757 posts

Uber Geek

Trusted

Subscriber

Reply # 594100 12-Mar-2012 13:02
napster, so you made that change, your hosts file has the changes as I put them to you? How are you determining that it's still pulling from Snaps servers? Was it no better for you? If you ping cache.l.google.com what IP are you getting? In the hosts file is there a space between the ip and host name? Your hosts file could look something like this: # Copyright (c) 1993-2009 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 # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost 203.109.178.26 cache.l.google.com

frizianz

96 posts

Master Geek

Reply # 594144 12-Mar-2012 14:03
Adding stuff to your hosts file will break things more. Most cache's do not have only one IP address as they are a stack of servers not a single server. In summary if you wish to break it more follow the advise of adding the stuff to your hosts file. Its better just to leave it to DNS.

networkn

4757 posts

Uber Geek

Trusted

Subscriber

Reply # 594150 12-Mar-2012 14:12
frizianz: Adding stuff to your hosts file will break things more. Most cache's do not have only one IP address as they are a stack of servers not a single server. In summary if you wish to break it more follow the advise of adding the stuff to your hosts file. Its better just to leave it to DNS. I wasn't suggesting it as a permanent fix, I was simply suggesting it as a testing step to see if it helped and to further narrow down the cause of the problem. At worst it could be a temporary workaround until the full time solution is located.

RalphFromSnap

393 posts

Ultimate Geek

Trusted

Snap Internet

Reply # 594169 12-Mar-2012 14:42
Hi guys, One thing you can try is setting Google's public DNS servers (IP addresses 8.8.8.8 and 8.8.4.4). If you could test Youtube performance using Google's DNS, post the results and some trace routes this would be great. Then we will have a comparison to Snap's DNS. Thanks, snap! 0800 BROADBAND (276 232) www.snap.net.nz @SnapInternet on Twitter Snap Internet on Facebook Our Team: ^MC Michelle Clements ^AL Allan Loveday ^RO Ricky Owens ^ST Sam Taylor

networkn

4757 posts

Uber Geek

Trusted

Subscriber

Reply # 594181 12-Mar-2012 15:21
Hi I have tried changing dns made no difference but changing my hosts file temporarily worked so seems to indicate snap cache I think

Beccara

687 posts

Ultimate Geek

UberGroup

Reply # 594182 12-Mar-2012 15:22
Aren't most GGC's blackbox's as far as the ISP can see and it's operation remains under google's control? All comment's I make are my own personal opinion and do not in any way, shape or form reflect the views of current or former employers unless specifically stated

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16