dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
11396
share rss forum feed

Cronk

join:2005-07-16

Tracert "request timed out"

When I open a cmd prompt and execute tracert, it connects ok to my router on the first hop, then the next 14 or 15 hops are all "request timed out", then the final entry shows that it reaches the domain successfully. I get this result when I run tracert to google.com, to yahoo.com, and to comcast.net.

I've called Comcast and they say they can see no problem. My internet is working but it is sluggish. Any ideas?

Thanks


Bink
Villains... knock off all that evil

join:2006-05-14
Castle Rock, CO
kudos:4

Your router/firewall is mucking things up.



Napsterbater
Meh
Premium,MVM
join:2002-12-28
Milledgeville, GA

or the ISP


supergeeky

join:2003-05-09
United State
kudos:3
reply to Cronk

your router must be blocking "ICMP" or has "disable anonymous Internet request" enabled.

Not all hops may respond, as in my example below the 2nd hop never responds but subsequent ones usually do.

I have verified that it is possible to traceroute to google.com, yahoo.com, and to comcast.net from a Comcast connection...

Example of what a good output is:

C:\Documents and Settings\User532>tracert google.com
 
Tracing route to google.com [74.125.95.103]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     9 ms  te-6-3-ur08.mtprospect.il.chicago.comcast.net [68.86.114.141]
  4    10 ms    11 ms    11 ms  be-50-ar01.area4.il.chicago.comcast.net [68.87.230.53]
  5    13 ms    11 ms    12 ms  pos-1-13-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.49]
  6    13 ms    12 ms    13 ms  pos-0-3-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.158]
  7    13 ms    11 ms    11 ms  as15169-1.350ecermak.il.ibone.comcast.net [75.149.230.198]
  8    12 ms    11 ms    18 ms  209.85.250.239
  9    24 ms    23 ms    23 ms  209.85.241.22
 10    22 ms    23 ms    24 ms  209.85.241.37
 11    27 ms    35 ms    30 ms  72.14.239.193
 12    23 ms    23 ms    23 ms  iw-in-f103.1e100.net [74.125.95.103]
 
Trace complete.
 

korstj

join:2000-08-26
San Diego, CA

It sounds to me like either Comcast's gateway router or your router is blocking inbound ICMP TTL Exceeded packets. The final destination generates a response in tracert because it is sending back an ICMP echo response packet, which is different than all of the other hops in a trace. (the same as pinging it directly)

To test to see which is blocking it, connect a PC directly to the modem (bypassing your router) and try it again. If you get the same thing, then it's Comcast's router (your first hop, not their entire network, necessarily). If the trace goes through completely, then you know your router is to blame.



Napsterbater
Meh
Premium,MVM
join:2002-12-28
Milledgeville, GA
Reviews:
·Windstream

said by korstj:

It sounds to me like either Comcast's gateway router or your router is blocking inbound ICMP TTL Exceeded packets. The final destination generates a response in tracert because it is sending back an ICMP echo response packet, which is different than all of the other hops in a trace. (the same as pinging it directly)

To test to see which is blocking it, connect a PC directly to the modem (bypassing your router) and try it again. If you get the same thing, then it's Comcast's router (your first hop, not their entire network, necessarily). If the trace goes through completely, then you know your router is to blame.
That would be a good test.

Alltel now Windstream used to do this only the first or second hop of theirs would respond then the rest timed out unless you used a UDP traceroute.
--
ASUS M4A79T Deluxe | AMD Phenom II x3 720 BE AM3 w/4 Cores @ 3.41Ghz(OC) | 4Gb DDR3 Memory @ 1600mhz | Sapphire ATI HD4870 1GB 800mhz/1000mhz(OC) | 2x500GB HDD's Raid 0 | Windows 7 Ultimate x64 Build 7600 (RTM) | Windstream DSL 12m (14.9m Sync)/766k