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?

"Ritter 197" wrote in
<news:A2AD317C-94C4-4238-9DEB-A9D25023900B@microsoft.com>:

Note: This is not a hardware issue. microsoft.public.windowsxp.hardware
was removed from my reply.

Have you tried upping the timeout? It's a command-line parameter to
'tracert'. If you are using a firewall, did it allow both TCP *and* UDP
traffic for that application? Some firewall are screwed up as delivered
at install-time by blocking ALL ping requests, including the return from
tracert (Comodo v3 was like that and I don't know if they fixed it).

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.

"VanguardLH" <V@nguard.LH> wrote in message
news:HY6dnWBuVaABSd3VnZ2dnUVZ_t3inZ2d@comcast.com. ..

So when you type "tracert www.comcast.net" into a command prompt window it
times out, I've just tried it and it's ok in 9 hops.
Neil
"Ritter 197" <Ritter197@comcast.net> wrote in message
news:A2AD317C-94C4-4238-9DEB-A9D25023900B@microsoft.com...

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

"neil" <neilp67_@_hotmail.com> wrote in message
news:RQz0k.10559$yb3.4637@newsfe18.ams2...

Ritter 197 wrote:
if it gets to the end of the route.

ALL hops timed out. 30 of them.

"Big Al" <BigAl@nowhere.com> wrote in message
news:nXG0k.1093$jX.28@trnddc04...

Ritter 197 wrote:
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

How about firewall interference?

Ritter 197 wrote:

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


Ritter 197;3130667 Wrote:



--
Oviraptor