Router question... Why is this happening?

[Ray Miller]

Hi. I have a new Network Everywhere Linksys Router. Model NR041.

This is a copy of a tracert command from a system behind the router:

Tracing route to yahoo.com [66.218.71.198]
over a maximum of 30 hops:

1 * * * Request timed out.
2 14 ms 11 ms 11 ms 10.116.48.1
3 13 ms 12 ms 12 ms 24-116-200-229.cpe.cableone.net
[24.116.200.229]
4 21 ms 28 ms 20 ms 12.124.58.25
5 24 ms 22 ms 35 ms gbr5-p80.attga.ip.att.net [12.123.21.74]
6 39 ms 23 ms 21 ms tbr1-p013501.attga.ip.att.net
[12.122.12.21]
7 37 ms 38 ms 37 ms tbr2-cl1.wswdc.ip.att.net [12.122.10.69]
8 36 ms 60 ms 36 ms ggr2-p390.wswdc.ip.att.net [12.123.9.85]
9 40 ms 37 ms 39 ms so-2-0-0.edge1.Washington1.Level3.net
[209.244.219.141]
10 37 ms 39 ms 37 ms so-5-0-0.gar2.Washington1.Level3.net
[209.244.11.13]
11 95 ms 94 ms 96 ms unknown.Level3.net [64.159.1.133]
12 98 ms 99 ms 99 ms gige9-0.ipcolo3.SanJose1.Level3.net
[64.159.2.9]
13 96 ms 95 ms 101 ms unknown.Level3.net [64.152.69.30]
14 99 ms 100 ms 100 ms w1.rc.vip.scd.yahoo.com [66.218.71.198]

Trace complete.



Why is line one timing out like that? This happens when the trace is run
from either of my two systems behind the router. If I trace to 192.168.1.1
(the router's gateway address on my internernal network) the trace is very
fast and I get this:

Tracing route to 192.168.1.1 over a maximum of 30 hops

1 1 ms 1 ms 2 ms 192.168.1.1

Trace complete.


Also if I trace to the public side of the router, it responds very quickly
and I get:

Tracing route to 24-117-77-123.cpe.cableone.net [24.117.77.123]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 24-117-77-123.cpe.cableone.net
[24.117.77.123]

Trace complete.


But if I run a trace to any, and I mean ANY address farther away than that,
I get that annoying timeout on line one. Somebody please explain this to
me. I can't figure it out.

Best Regards

 

[LGJ]

But if I run a trace to any, and I mean ANY address farther away than that,
I get that annoying timeout on line one. Somebody please explain this to
me. I can't figure it out.

Best Regards

did you have a better experience with another router? is this a big
problem? i see that it allways finishes the trace with no errors, it's
just looking for a route to the server over all the routers on the
internet that may be down at any given point for an unspecified amount
of time, it tries one router, then another, until one is available.

is your internet slower because of this? why do you have to tracert so
much as to become an anoyance?

--LGJ

 

[Ray Miller]

"Ray Miller" <[email protected]> wrote in message

did you have a better experience with another router? is this a big
problem? i see that it allways finishes the trace with no errors, it's
just looking for a route to the server over all the routers on the
internet that may be down at any given point for an unspecified amount
of time, it tries one router, then another, until one is available.

is your internet slower because of this? why do you have to tracert so
much as to become an anoyance?

--LGJ

No the internet is not slow, and I don't have another router to try.
Actually I got a response in another group that makes a lot of sense and
that is that many ISPs turn off ICMP at their gateway for performance or
security reasons. That makes sense to me as any trace that goes beyond my
ISPs gateway gives me these results. I don't ever remember a trace doing
this when I was using ICS as my router, but maybe so.

If anybody else has any ideas, I'd like to hear them.

At any rate, I only ran trace so much because 1) my router is new and 2) I
have just completed Network+ and am going for i-Net+, so I was experiement
with my new router for educational purposes.

Thanks.