Anyone know why the first hop in a test trace route always times out?
I believe this problem has just started, I don't remember seeing this issue before when I did trace routes. Is comcast having problems with a router at the moment?
C:\>tracert www.comcast.net
Tracing route to www.comcast.net
over a maximum of 30 hops:
1 * * * Request timed out.
2 8 ms 22 ms 22 ms 12.244.24.241
3 11 ms 25 ms 26 ms 12.244.72.210
4 10 ms 12 ms 25 ms gbr5-p40.sffca.ip.att.net
5 12 ms 12 ms 25 ms tbr1-p013501.sffca.ip.att.net
6 55 ms 53 ms 50 ms tbr1-cl1.cgcil.ip.att.net
7 73 ms 71 ms 72 ms tbr1-p013601.n54ny.ip.att.net
8 69 ms 70 ms 70 ms gbr1-p10.n54ny.ip.att.net
9 71 ms 70 ms 69 ms gar1-p360.n54ny.ip.att.net
10 70 ms 73 ms 70 ms mdf1-gsr12-2-pos-7-0.nyc3.attens.net
11 76 ms 72 ms 75 ms sccsbix11-1-6.attbi.com
12 71 ms 73 ms 73 ms 192.168.201.11
13 73 ms 74 ms 71 ms www.comcast.net
Those are normal ping times coast-to-coast. I wouldn't worry about it, the first hop is to a local subnet IP and may not respond to ICMP. You might try pinging your default gateway which should respond to pings. That is your first hop. If you always get those ping times to comcast.net, you're fine.
