tracert times out

  • Thread starter Thread starter Ritter 197
  • Start date Start date
R

Ritter 197

I want to do a tracert on comcast.net (my ISP) and it always times out, yet
I can get e-mail and see newsgroups.

What does it mean then and what to do to do a tracert?
 
I use TREND MICRO Pro. Ping always times out. Time out is 2 seconds.
I do not know where to increase the time out period. When I go into the
TREND Micro database and search for "ping" or "timeout" it finds nothing.
 
Ritter said:
yes, mine times out. have tried it now many times.
I've been *told* that a single hop timeout is not an issue. Especially
if it gets to the end of the route.
 
Ritter said:
ALL hops timed out. 30 of them.

There is some background information on traceroute here.

http://en.wikipedia.org/wiki/Tracert

What if an important port number was blocked by Comcast
for their own customers ? That might mean the difference
between a Comcast customer running the test, and those
of us outside the Comcast network running the test.
I didn't have any problem running traceroute here,
against either www.comcast.net or just comcast.net,
and I'm outside Comcast.

Maybe you can make enough sense out of that Wikipedia
article, to come up with another test. Perhaps your
own firewall is the reason the test failed.

Comcast had some issues just recently, and may have
made adjustments to their network in an effort to
figure out the problem. And in any case, like any
ISP, if you phone up and ask them a question, you'll
get that "we're innocent" routine. Tech support will
never admit to any filtering, even if it is for good
and logical reasons.

http://www.dailytech.com/article.aspx?newsid=11925

Paul
 
yes, mine times out. have tried it now many times.

Most of the Comcast servers will not respond to a tracert probe. It's
normal and not under your control. Many ISPs to it to limit traffic
during high traffic times and/or to prevent probes from internet static.
Nothing you can do about it.
 
It is possible that one of the routers (probably the one you connect
through) has been set to not reply to Pings. Tracert uses ICMP pings to
work it way through, and if pings are being blocked it will not work,
and timeout.

Oviraptor
 
I've run into the same issue with tracert and the TrendMicro Firewall. If your Firewall is set to any level above MINIMUM, tracert doesn't work to any IP. Set your firewall to minimum and it will probably work.
 
I was trying to get ping and tracert to work with Trend Micro's Firewall set to Maximum and discovered the fix.

In the advanced settings of the Firewall, add both programs as allowed. Then go to the Network Control Protocol window and add two rules. One to allow Outgoing ICMP (this opened up PING) and another to allow Incoming ICMP (this fixed TRACERT).

I still show up as fully stealthed even in the DMZ on my router with Trend's firewall at low.

YMMV
 
'Jeff Cook[_2_ said:
;3153001']I was trying to get ping and tracert to work with Trend
Micro's Firewall set to Maximum and discovered the fix.

In the advanced settings of the Firewall, add both programs as allowed.
Then go to the Network Control Protocol window and add two rules. One to
allow Outgoing ICMP (this opened up PING) and another to allow Incoming
ICMP (this fixed TRACERT).

I still show up as fully stealthed even in the DMZ on my router with
Trend's firewall at low.

YMMV

If you notice your tracert may no be going to comcast at all. I just
did this one and...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Admin>tracert www.comcast.net

Tracing route to a1526.g.akamai.net [70.183.191.137]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 7 ms 6 ms 6 ms 10.71.128.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6

Tke DNS took me to akamai, but then I hit ping blocking.

If I did the correct address I get

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Admin>tracert comcast.net

Tracing route to comcast.net [63.240.76.72]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.2.1
2 7 ms 7 ms 7 ms 10.71.128.1
3 * *


Ping blocking still gets in the way though.

So you do have to be very careful what address you are actually using.
 
Back
Top