I can't connect to http://www.tyt888.com/en/?mod=download on the verizon network fios and wireless both fail. I am able to connect to this server thru a VPN. Please fix I need to get firmware updates for my radio.
Ah yes. I forgot to mention that ICMP Traceroute is broken on FiOS. Windows' built in utility uses ICMP and I'm not sure if Microsoft has a UDP Traceroute utility built into Windows. If you have a Mac or Linux system around, try using the `traceroute` command available on those machines for that site.
You're talking to other users here. If you want to reach Verizon, you'll need to contact them by phone, chat or Twitter support.
I have the same problem, any luck??
Warren
Can you provide a traceroute to the website? Let's see where it is failing to move further. Here's a guide:
https://www.siteground.com/kb/how_to_perform_traceroute_checks_in_windows_linux_and_macos/
That site appears to be hosted in China, FYI. Verizon appears to have issues with sites hosted in China from time to time.
I ran a traceroute myself from a non-Verizon connection, and I see it is getting pretty far - well off of the ISP's network.
Tracing route to www.tyt888.com [103.45.249.244] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms USG [192.168.1.1] 2 7 ms 14 ms 11 ms 142.254.216.197 3 22 ms 24 ms 32 ms agg63.ntnwny1702h.northeast.rr.com [24.58.216.93] 4 11 ms 8 ms 8 ms agg37.lncsnycd02r.northeast.rr.com [24.58.38.106] 5 19 ms 21 ms 15 ms be29.rochnyei01r.northeast.rr.com [24.58.32.62] 6 34 ms 23 ms 38 ms bu-ether13.tustca4200w-bcr00.tbone.rr.com [66.109.6.2] 7 79 ms 79 ms 79 ms bu-ether11.snvacaid17w-bcr00.tbone.rr.com [66.109.6.14] 8 84 ms 79 ms 79 ms bu-ether11.snjucacl67w-bcr00.tbone.rr.com [66.109.6.8] 9 75 ms 74 ms 74 ms 0.ae1.pr0.sjc10.tbone.rr.com [66.109.6.137] 10 73 ms 78 ms 79 ms 218.30.54.178 11 78 ms 79 ms 78 ms 202.97.50.73 12 242 ms 238 ms 236 ms 202.97.90.217 13 248 ms 249 ms 249 ms 202.97.12.49 14 256 ms 260 ms 255 ms 202.97.34.73 15 253 ms 252 ms * 202.97.80.218 16 * * 274 ms 219.148.216.150 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 *
When I traceroute from my phone, the traceroute stops as soon as it hits the AS701 (UUNet/MCI/Verizon Business) backbone.
bash-5.0$ traceroute www.tyt888.com 1?: [LOCALHOST] pmtu 1428 1: 79.sub-66-174-10.myvzw.com 40.582ms 1: 79.sub-66-174-10.myvzw.com 47.618ms 2: no reply 3: no reply 4: 194.sub-69-83-5.myvzw.com 61.225ms asymm 3 5: no reply 6: 52.sub-69-83-3.myvzw.com 57.898ms asymm 5 7: 52.sub-69-83-3.myvzw.com 60.441ms asymm 8 8: 73.sub-69-83-3.myvzw.com 50.214ms asymm 6 9: no reply 10: no reply 11: no reply 12: no reply 13: no reply 14: no reply 15: no reply 16: no reply 17: no reply 18: no reply 19: no reply 20: no reply 21: no reply 22: no reply 23: no reply 24: no reply 25: no reply 26: no reply 27: no reply 28: no reply 29: no reply 30: no reply Too many hops: pmtu 1428 Resume: pmtu 1428
It connects in one jump. Weird. I would have expected a lot more, especially since the destination IP address is in China. I cannot access from any device on my home network. Only when using cell phone (no wifi) can I access the webpage.
C:\Users\USER>tracert tyt888.com
Tracing route to tyt888.com [103.45.249.244]over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Router [192.168.0.1]2 1 ms 3 ms 1 ms 103.45.249.244
Trace complete.
No luck. I have to browse the webpage using cell phone, download what I need to the phone, then switch phone on to wifi and transfer the files to my NAS drive to get them inside my network.
I cannot ping it though.
C:\Users\USER>ping tyt888.com
Pinging tyt888.com [103.45.249.244] with 32 bytes of data:Request timed out.Request timed out.Request timed out.Request timed out.
Ping statistics for 103.45.249.244:Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
If you download Portable Opera browser https://www.opera.com/computer/portable you can turn on the built in VPN and then access tyt888.com. That works for me.
@Smith6612 wrote: Ah yes. I forgot to mention that ICMP Traceroute is broken on FiOS. Windows' built in utility uses ICMP and I'm not sure if Microsoft has a UDP Traceroute utility built into Windows. If you have a Mac or Linux system around, try using the `traceroute` command available on those machines for that site.
That is correct.
For Windows an example of how to do that, I point to https://www.namecheap.com/support/knowledgebase/article.aspx/9777/2194/how-to-use-tcp-traceroute/ which uses third party software.
