Many of you may already know this but its common for traceroute to not answer from certain routers even though the connection is fine. This has to do with blocking the TTL expiring ICMP messages generated from the UDP packets sent during a traceroute. In other words, traceroute is a bad tool to use verify connectivity. Ping is better assuming the host isnt firewalling it. When in doubt, use nmap! :) unless, of course, you are scanning my network....then dont use nmap. :) At 04:47 PM 11/9/00 -0600, you wrote: >This is almost as good as my not reading the subject line about beer... > >> bash-2.03$ traceroute goggle.com >> traceroute to goggle.com (216.246.45.18), 30 hops max, 40 byte packets > >That's "Google", not "Goggle" :p > > >-- >Bill Layer >Sales Technician ><b.layer at vikingelectronics.com> > >+----------------------------------+ > Viking Electronics, Inc. > 1531 Industrial St. > Hudson, WI. 54016 - U.S.A > 715.386.8861 ext. 210 > <http://www.vikingelectronics.com> >+----------------------------------+ > >"Telecom Solutions for the 21st Century" > Powered by Slackware Linux 7.1.0 > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org >For additional commands, e-mail: tclug-list-help at mn-linux.org >