On Thu, Sep 10, 2009 at 07:07, Jon D wrote:
> I've never paid enough attention. When youguys do a tracert to your
> wan links, is it normal to get a timeout somewhere along the way, like
> maybe right after your border router?
> I'm assuming the answer is 'NO', but I just wanted to verify.
>
> I h
Get pingplotter (www.pingplotter.com). Free eval and nagware after
that. It will do repeated traceroutes and graphs the results over time
(including graphing the intermediate hops if desired).
-Original Message-
From: Jon D [mailto:rekcahp...@gmail.com]
Sent: Thursday, September 10, 200
On Thu, Sep 10, 2009 at 11:02 AM, John Aldrich
wrote:
> You can also use another form of traceroute that does not use ICMP
AFAIK, all traceroute implementations use and depend on ICMP
(Internet Control Message Protocol). Specifically, the ICMP Time
Expired message that proper Internet Protocol
tes or not.
-Original Message-
From: Erik Goldoff [mailto:egold...@gmail.com]
Sent: Thursday, September 10, 2009 10:16 AM
To: NT System Admin Issues
Subject: RE: TraceRoute Timout -- Normal???
timeouts within a traceroute may be caused by security configurations on
devices along the route,
Any device along the chain set to not respond to ICMP ( a common, if
questionable, security practice) will give a timeout. Not to worry as
long as your connectivity is getting past the device.
-sc
> -Original Message-
> From: Jon D [mailto:rekcahp...@gmail.com]
> Sent: Thursday, September
Awesome! Thanks Ben!
On Thu, Sep 10, 2009 at 10:33 AM, Ben Scott wrote:
> On Thu, Sep 10, 2009 at 10:07 AM, Jon D wrote:
>> I've never paid enough attention. When youguys do a tracert to your
>> wan links, is it normal to get a timeout somewhere along the way, like
>> maybe right after your bo
On Thu, Sep 10, 2009 at 10:07 AM, Jon D wrote:
> I've never paid enough attention. When youguys do a tracert to your
> wan links, is it normal to get a timeout somewhere along the way, like
> maybe right after your border router?
It depends.
Traceroute works by crafting packets with a delibe
Gotcha. Thanks!
On Thu, Sep 10, 2009 at 10:15 AM, Erik Goldoff wrote:
> timeouts within a traceroute may be caused by security configurations on
> devices along the route, they will *pass* packets properly as a router, but
> their interfaces will not respond, even to icmp type traffic, making
timeouts within a traceroute may be caused by security configurations on
devices along the route, they will *pass* packets properly as a router, but
their interfaces will not respond, even to icmp type traffic, making them
'stealth' to some scripted attacks that target addresses that respond.
E
