Post Reply
Is there any problem for Connection with Colombia?
|
Hi,
I'm having trouble with CR in My Viera, The CR is very slow and freeze a lot of times when I'm playing. Do you know if it's a connection problem? I have Netflix on the TV and it's working fine without freeze. Thanks, Keitaro |
|
|
|
|
Customer Support Manager
|
Spoiler Alert! Click to show or hide keitaronjz wrote: Hi, I'm having trouble with CR in My Viera, The CR is very slow and freeze a lot of times when I'm playing. Do you know if it's a connection problem? I have Netflix on the TV and it's working fine without freeze. Thanks, Keitaro Can you run the following tests and email me? (Use the contact us link at the bottom of the page.) http://www.crunchyroll.com/help?topic=video#5.1 Rather than : cp150757.edgefcs.net Can you please use : v1.lln.crunchyroll.com |
|
Catching up. Please be patient.
|
|
|
Thanks for the instruction I'm checking it and seems latency problem... today is buffering a lot.. so it's some issue may be with my Internet carrier.
Thanks a lot Sidekick C:\Users\robertot>nslookup v1.lln.crunchyroll.com Server: ns1.etb.net.co Address: 200.75.51.132 Non-authoritative answer: Name: crunchy.vo.llnwd.net Addresses: 68.142.101.7 68.142.101.254 Aliases: v1.lln.crunchyroll.com C:\Users\robertot>ping v1.lln.crunchyroll.com Pinging crunchy.vo.llnwd.net [68.142.101.7] with 32 bytes of data: Reply from 68.142.101.7: bytes=32 time=159ms TTL=58 Reply from 68.142.101.7: bytes=32 time=202ms TTL=58 Reply from 68.142.101.7: bytes=32 time=276ms TTL=58 Reply from 68.142.101.7: bytes=32 time=180ms TTL=58 Ping statistics for 68.142.101.7: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 159ms, Maximum = 276ms, Average = 204ms C:\Users\robertot>tracert v1.lln.crunchyroll.com Tracing route to crunchy.vo.llnwd.net [68.142.101.7] over a maximum of 30 hops: 1 23 ms 4 ms 4 ms 192.168.0.1 2 39 ms 35 ms 36 ms 10.32.0.46 3 132 ms 207 ms 306 ms corporat201-2441005.sta.etb.net.co [201.244.1.5] 4 76 ms 77 ms 77 ms so-0-3-0.usa.nam-core02.columbus-networks.com [63.245.47.25] 5 242 ms 80 ms 80 ms ge-1-1-0.usa.nam-core01.columbus-networks.com [63.245.5.81] 6 77 ms 74 ms 75 ms xe-1-0-0.usa.brx-teracore02.columbus-networks.com [63.245.5.106] 7 92 ms 103 ms 96 ms e1-3.fr1.mia1.llnw.net [198.32.124.145] 8 * 346 ms 294 ms cdn-68-142-101-7.mia1.llnw.net [68.142.101.7] Trace complete. C:\Users\robertot>ping v1.lln.crunchyroll.com Pinging crunchy.vo.llnwd.net [68.142.101.7] with 32 bytes of data: Reply from 68.142.101.7: bytes=32 time=355ms TTL=58 Reply from 68.142.101.7: bytes=32 time=86ms TTL=58 Reply from 68.142.101.7: bytes=32 time=87ms TTL=58 Reply from 68.142.101.7: bytes=32 time=135ms TTL=58 Ping statistics for 68.142.101.7: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 86ms, Maximum = 355ms, Average = 165ms |
|
|
|
|
Customer Support Manager
|
Spoiler Alert! Click to show or hide keitaronjz wrote: Thanks for the instruction I'm checking it and seems latency problem... today is buffering a lot.. so it's some issue may be with my Internet carrier. Thanks a lot Sidekick C:\Users\robertot>nslookup v1.lln.crunchyroll.com Server: ns1.etb.net.co Address: 200.75.51.132 Non-authoritative answer: Name: crunchy.vo.llnwd.net Addresses: 68.142.101.7 68.142.101.254 Aliases: v1.lln.crunchyroll.com C:\Users\robertot>ping v1.lln.crunchyroll.com Pinging crunchy.vo.llnwd.net [68.142.101.7] with 32 bytes of data: Reply from 68.142.101.7: bytes=32 time=159ms TTL=58 Reply from 68.142.101.7: bytes=32 time=202ms TTL=58 Reply from 68.142.101.7: bytes=32 time=276ms TTL=58 Reply from 68.142.101.7: bytes=32 time=180ms TTL=58 Ping statistics for 68.142.101.7: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 159ms, Maximum = 276ms, Average = 204ms C:\Users\robertot>tracert v1.lln.crunchyroll.com Tracing route to crunchy.vo.llnwd.net [68.142.101.7] over a maximum of 30 hops: 1 23 ms 4 ms 4 ms 192.168.0.1 2 39 ms 35 ms 36 ms 10.32.0.46 3 132 ms 207 ms 306 ms corporat201-2441005.sta.etb.net.co [201.244.1.5] 4 76 ms 77 ms 77 ms so-0-3-0.usa.nam-core02.columbus-networks.com [63.245.47.25] 5 242 ms 80 ms 80 ms ge-1-1-0.usa.nam-core01.columbus-networks.com [63.245.5.81] 6 77 ms 74 ms 75 ms xe-1-0-0.usa.brx-teracore02.columbus-networks.com [63.245.5.106] 7 92 ms 103 ms 96 ms e1-3.fr1.mia1.llnw.net [198.32.124.145] 8 * 346 ms 294 ms cdn-68-142-101-7.mia1.llnw.net [68.142.101.7] Trace complete. C:\Users\robertot>ping v1.lln.crunchyroll.com Pinging crunchy.vo.llnwd.net [68.142.101.7] with 32 bytes of data: Reply from 68.142.101.7: bytes=32 time=355ms TTL=58 Reply from 68.142.101.7: bytes=32 time=86ms TTL=58 Reply from 68.142.101.7: bytes=32 time=87ms TTL=58 Reply from 68.142.101.7: bytes=32 time=135ms TTL=58 Ping statistics for 68.142.101.7: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 86ms, Maximum = 355ms, Average = 165ms I'm not too familiar with the settings on a Viera. Do you have the ability to set the DNS on it? |
|
Catching up. Please be patient.
|
|
|
Yes I can set DNS manually on Network Settings I guess, But know it's working but very slow... Now I realize that sometimes the latency also make Netflix to flick some black screens when it's playing or the video take a lot of time to load.
Thanks a lot. If you need some information that I can help as Viera user just let me know. |
|
|
|
|
Customer Support Manager
|
Spoiler Alert! Click to show or hide keitaronjz wrote: Yes I can set DNS manually on Network Settings I guess, But know it's working but very slow... Now I realize that sometimes the latency also make Netflix to flick some black screens when it's playing or the video take a lot of time to load. Thanks a lot. If you need some information that I can help as Viera user just let me know. Well, for us you're being directed towards a server in Arizona. Can you try changing the DNS to Google's DNS - 8.8.8.8 or 8.8.4.4 ? And then let me know how playback is? |
|
Catching up. Please be patient.
|
|
|
Sure If Viera cannot set DNS I'll set on my router just to test.
Thanks a lot |
|
|
|
|
With DNS 8.8.8.8 is better, it's more stable and dont stop too much when I play.
Thanks a lot |
|
|
|
|
Customer Support Manager
|
Spoiler Alert! Click to show or hide keitaronjz wrote: With DNS 8.8.8.8 is better, it's more stable and dont stop too much when I play. Thanks a lot I'm happy to hear that helped some! |
|
Catching up. Please be patient.
|
|
Popular Shows |
Platforms and Devices |
Premium MembershipsLanguage
|
Support |
Crunchyroll |