- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ping package drop on certain website (Godaddy, Verizon), fine on others. Help
Tracing route to www.google.com [64.233.176.99]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
Also, The support chat is not working for me...
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If your trace looks like that, it suggests a firewall may be to blame and is not allowing ICMP Echo packets to be returned. Check to see if the Firewall on your computer and router is set to reject this kind of traffic.
Note that a firewall can be to blame for lousy speeds if control data is being blocked. ICMP is especially important with IPv6, something Verizon hasn't implemented on FiOS yet.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Timeouts on traceroutes are normal and don't mean much. The reason is many servers are configured not to reply to ping packets.
Yet something looks wrong with the trace route you posted. You should at least see your own IP address, 192.168.1.1, as the first step and probably a Verizon server or two as the next couple of steps.
Do I understand correctly that with other sites traceroutes are normal, but not with the Google IP you posted?
FWIW, here's what I get when I trace to that same IP:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\xxx>tracert 64.233.176.99
Tracing route to 64.233.176.99 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 7 ms L100.NYCMNY-VFTTP-119.verizon-gni.net [71.241.153.1]
3 9 ms 9 ms 10 ms G0-11-1-5.NYCMNY-LCR-21.verizon-gni.net [130.81.188.78]
4 * * * Request timed out.
5 9 ms 19 ms 9 ms 0.ae3.XL3.NYC1.ALTER.NET [140.222.226.31]
6 8 ms 10 ms 9 ms 0.xe-10-0-0.GW13.NYC1.ALTER.NET [152.63.18.110]
7 9 ms 9 ms 10 ms google-gw.customer.alter.net [204.148.18.206]
8 9 ms 10 ms 9 ms 209.85.247.7
9 8 ms 9 ms 10 ms 209.85.252.242
10 19 ms 17 ms 17 ms 209.85.249.11
11 31 ms 29 ms 30 ms 64.233.174.9
12 34 ms 34 ms 34 ms 216.239.48.40
13 35 ms 34 ms 35 ms 64.233.175.12
14 * * * Request timed out.
15 29 ms 26 ms 27 ms 64.233.176.99
Trace complete.
C:\Users\xxxf>
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If your trace looks like that, it suggests a firewall may be to blame and is not allowing ICMP Echo packets to be returned. Check to see if the Firewall on your computer and router is set to reject this kind of traffic.
Note that a firewall can be to blame for lousy speeds if control data is being blocked. ICMP is especially important with IPv6, something Verizon hasn't implemented on FiOS yet.