Visitor
•
2 Messages
Cannot ping 8.8.4.4, ipv4 is flakey, ipv6 seems to be fine.
I'm able to ping 8.8.8.8 but not 8.8.4.4
tracert over 30 hops doesn't reach the destination for 8.8.4.4, it does for 8.8.8.8 though.
>tracert -4 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.10.1
2 * * * Request timed out.
3 7 ms 7 ms 8 ms 107.3.156.1
4 9 ms 8 ms 8 ms te-0-2-0-10-sur04.santaclara.ca.sfba.comcast.net [162.151.30.129]
5 * * * Request timed out.
6 14 ms 15 ms 14 ms hu-0-3-0-7-ar01.santaclara.ca.sfba.comcast.net [68.87.192.189]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 11 ms 10 ms 10 ms 216.239.50.191
11 9 ms 11 ms 15 ms 216.239.49.95
12 10 ms 9 ms 9 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
>tracert -4 8.8.4.4
Tracing route to google-public-dns-b.google.com [8.8.4.4]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.10.1
2 * * * Request timed out.
3 7 ms 9 ms 8 ms 107.3.156.1
4 8 ms 8 ms 8 ms te-0-2-0-10-sur04.santaclara.ca.sfba.comcast.net [162.151.30.129]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 9 ms 9 ms 10 ms he-0-12-0-0-pe02.529bryant.ca.ibone.comcast.net [68.86.86.166]
9 * * * Request timed out.
10 12 ms 11 ms 12 ms 216.239.50.191
11 11 ms 13 ms 11 ms 216.239.56.145
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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.
Trace complete.
There are no problems with ipv6.
>tracert -6 2001:4860:4860::8888
Tracing route to google-public-dns-a.google.com [2001:4860:4860::8888]
over a maximum of 30 hops:
1 15 ms 16 ms 11 ms 2001:558:5027:6d::1
2 10 ms 11 ms 10 ms te-0-2-0-10-sur03.santaclara.ca.sfba.comcast.net [2001:558:82:2120::1]
3 11 ms 12 ms 9 ms he-0-3-0-4-ar01.santaclara.ca.sfba.comcast.net [2001:558:80:c4::1]
4 * * * Request timed out.
5 9 ms 10 ms 11 ms he-0-11-0-1-pe02.529bryant.ca.ibone.comcast.net [2001:558:0:f5a4::2]
6 22 ms 22 ms 24 ms 2001:559::8ce
7 18 ms 11 ms 11 ms 2001:4860::1:0:7ea
8 53 ms 53 ms 56 ms 2001:4860::8:0:6117
9 36 ms 36 ms 36 ms 2001:4860::8:0:79e5
10 47 ms 47 ms 48 ms 2001:4860::8:0:6999
11 61 ms 53 ms 53 ms 2001:4860::8:0:924a
12 53 ms 53 ms 54 ms 2001:4860::2:0:90fe
13 * * * Request timed out.
14 53 ms 53 ms 53 ms google-public-dns-a.google.com [2001:4860:4860::8888]
Trace complete.
>tracert -6 2001:4860:4860::8844
Tracing route to google-public-dns-b.google.com [2001:4860:4860::8844]
over a maximum of 30 hops:
1 9 ms 10 ms 10 ms 2001:558:5027:6d::1
2 11 ms 14 ms 11 ms te-0-2-0-10-sur03.santaclara.ca.sfba.comcast.net [2001:558:82:2120::1]
3 * 9 ms 9 ms he-0-3-0-5-ar01.santaclara.ca.sfba.comcast.net [2001:558:80:c5::1]
4 * * * Request timed out.
5 10 ms 13 ms 14 ms he-0-12-0-0-pe02.529bryant.ca.ibone.comcast.net [2001:558:0:f5a9::2]
6 14 ms 14 ms 16 ms 2001:559::8ce
7 11 ms 11 ms 14 ms 2001:4860::1:0:7ea
8 58 ms 55 ms 53 ms 2001:4860::8:0:6117
9 37 ms 36 ms 36 ms 2001:4860::8:0:79e5
10 47 ms 47 ms 48 ms 2001:4860::8:0:6999
11 55 ms 55 ms 55 ms 2001:4860::8:0:924b
12 53 ms 54 ms 54 ms 2001:4860::2:0:90ff
13 * * * Request timed out.
14 53 ms 54 ms 63 ms google-public-dns-b.google.com [2001:4860:4860::8844]
Trace complete.
This has been a consistent problem for the last few weeks, internet connections are spotty and there is no clear discernable reason. It seems like ipv6 sites work fine, ipv4 tends to have problems. We have a Netgear CG3000DCR and there aren't many things to play around with inside, when trying to ping from the web control panel, it also fails.
Any ideas?
zzha0
Visitor
•
2 Messages
9 years ago
Still having trouble here.
Here's a tracert to amazon
>tracert amazon.com
Tracing route to amazon.com [54.239.17.7]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.10.1
2 * * * Request timed out.
3 9 ms 9 ms 8 ms 107.3.156.1
4 8 ms 8 ms 7 ms 162.151.30.129
5 * * * Request timed out.
6 12 ms 10 ms 8 ms hu-0-0-0-1-ar01.santaclara.ca.sfba.comcast.net [68.85.57.145]
7 * * * Request timed out.
8 16 ms 18 ms 18 ms be-10915-cr02.losangeles.ca.ibone.comcast.net [68.86.86.98]
9 54 ms 47 ms 48 ms be-11524-cr02.dallas.tx.ibone.comcast.net [68.86.87.174]
10 * * * Request timed out.
11 49 ms 47 ms * 66.208.232.158
12 * * * Request timed out.
13 * * * Request timed out.
14 81 ms 82 ms 81 ms 54.240.229.0
15 86 ms 81 ms 82 ms 54.240.229.168
16 80 ms 80 ms 80 ms 54.240.228.159
17 80 ms 89 ms 84 ms 54.239.108.180
18 * 80 ms 81 ms 54.239.108.201
19 81 ms 82 ms 84 ms 205.251.245.123
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.
Trace complete.
The connection has so far been hugely flakely. Can someone from comcast take a look at what is going on from the other side?
0
0
kraze
Problem solver
•
305 Messages
9 years ago
Can you clarify on what issues you're specifically seeing and when they start? Overall, ICMP not responding generally isn't a huge deal and can be caused by a few things.
If you haven't, I'd also recommend taking a look at this guide as it contains useful information that you can post for us to help you dig into your problem.
http://forums.businesshelp.comcast.com/t5/Connectivity/Connection-Troubleshooting-Tips/m-p/25861#U25861
0
0