Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What would be reasons for blocking trace route functionality for clients on a corporate network?

share|improve this question
up vote 3 down vote accepted

Tracert is typically blocked by Sysadmins / Network admins to prevent a mechanism with which one could potentially map the resources on your network.

You should also note that trace route can use different protocols, they may not all be blocked.

share|improve this answer
are you talking about different ports? Care to list them? – GregC Jul 13 '12 at 20:25
Not ports, but protocols. Trace route is capable of using TCP / UDP or ICMP. Windows can only use ICMP but Linux can use TCP and UDP as well. – DKNUCKLES Jul 13 '12 at 20:28

It would make it more difficult to map the architecture of the LAN from the inside. This helps security but hinders troubleshooting. It's up to the people running the show to determine the balance between those two needs.

share|improve this answer

If you must, you can trace the network hops in different ways. Hping3 has many methods for tracing hops in the network. Give it a whirl. However you may anger you networks gods if they have tight/paranoid security.


is a little easier to use, and can give realtime feedback on networks stats.

It has a number of detection methods, however it's not as cool as hping.

hope this helps

share|improve this answer

Your Answer


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.