Ya shure, U try to tracert through someone's 
else's firewall, da udder guy ain't gonna wanna 
U know his NAT'ed internal IP addresses, 

You betcha.

BT








NNNN
Tracy Johnson
MSI Schaevitz Sensors 

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Jeff Kell
> Sent: Tuesday, June 07, 2005 8:53 PM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] TRACERT Not Working
> 
> 
> donna garverick wrote:
> 
> > www.hp.com is a tough cookie (is that a pun?). if you do a lookup on
> > it, you'll see two ip addresses.  i don't know what that will do to
> > tracert.  given that i can't tracert to jazz, it makes me 
> wonder if hp
> > isn't doing some sort of filtering -- anti-DoS stuff.      - d
> 
> tracert will pick the first one returned.
> 
> As to blocking/not working, it depends on the firewall and 
> depends on the traceroute, and I confess I don't know how the 
> 3000 does it.
> 
> Traceroute works by sending out "a packet" to the target with 
> an incrementing TTL value and looks for responses, generally 
> ICMP unreachable - TTL exceeded on all hops except the last, 
> or an ICMP port unreachable if it made it all the way.
> 
> Traditional traceroutes use a UDP packet to a high-numbered port.
> 
> Windows traceroute uses an ICMP traceroute packet.
> 
> Firewalls may block any of those packets coming or going.
> 
> Jeff
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *