[NTLUG:Discuss] MS Windows vs. Linux Trace Route

[Rick Renshaw]

>----- Original Message ----
>From: Carl Haddick <sysmail at glade.net>
>To: NTLUG Discussion List <discuss at ntlug.org>
>Sent: Thu, June 24, 2010 12:22:09 PM
>Subject: Re: [NTLUG:Discuss] MS Windows vs. Linux Trace Route

>-----Original Message-----
>From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org] On Behalf
>Of Jay Urish
>Sent: Thursday, June 24, 2010 10:23 AM
>To: NTLUG Discussion List
>Subject: Re: [NTLUG:Discuss] MS Windows vs. Linux Trace Route

>On 6/24/2010 9:24 AM, Dennis Rice wrote:
>> At the school that I am now teaching Linux at has a situation that I 
>> have not seen before.
>>
>> Using a M$ Windows system I am able to perform a tracert from the 
>> command line in the lab.  When I use the Linux (Fedora 12) system, 
>> traceroute does not work beyond the internal routers, but mtr does.  I 
>> typically do a tracert to yahoo.com.
>>
>> Anyone have thoughts on why?
>>
>> Dennis

>You might try traceroute -I www.yahoo.com.

>Traceroute by default uses UDP packets, the -I switch causes it to use pings
>(ICMP).

>No telling what Winders uses, and it could be the traceroute UDP is being
>blocked at your router.

>Good luck,

>Carl

According to http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/tracert.mspx?mfr=true MS tracert uses ICMP echo request packets, which is a ping.