Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm tracing some server between tracert(Windows) and traceroute(linux) in the same network.
But the output is different.
tracert can trace the target server.
But traceroute can't. The traceroute output is below(Some asterisk omit).

traceroute to xxx.com (112.125.57.195), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  1.347 ms  0.729 ms  1.083 ms
 2  113.109.124.1 (113.109.124.1)  6.519 ms  5.903 ms  6.368 ms
 3  183.56.38.137 (183.56.38.137)  6.094 ms  37.891 ms  5.314 ms
 4  58.61.243.129 (58.61.243.129)  7.002 ms  8.967 ms  7.673 ms
 5  61.144.3.22 (61.144.3.22)  6.169 ms  6.147 ms  5.359 ms
 6  202.97.34.117 (202.97.34.117)  40.194 ms  532.342 ms  536.089 ms
 7  220.181.16.54 (220.181.16.54)  578.522 ms  586.950 ms  627.117 ms
 8  220.181.70.150 (220.181.70.150)  607.408 ms  681.635 ms  671.447 ms
 9  182.92.255.228 (182.92.255.228)  760.188 ms  766.492 ms  399.930 ms
10  * * *
11  * * *

That can't not trace the target server. And all the output is asterisk.

share|improve this question

1 Answer 1

Most flavours of traceroute in *NIX default to sdending UDP packets (though there is usually an option to change this), Windows will default to using ICMP echo requests.

share|improve this answer
    
means that the UDP packets is dropped? –  Magic May 3 '12 at 4:12

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.