Quote:
Originally Posted by khandman
[You must be logged in to view images. Log in or Register.]
Firewalls and even policy rules that blocks the command can return a timeout. The timeout does not mean you've been blocked or that hop is the cause.
|
This is true. Some routers may be set to ignore pings and traces, therefore getting the time out. If there was a problem at that node, the trace would likely hang on that node with repeated time outs until 30 hops (or tries) were done. The fact the trace made it to the destination means something else is going on, unless that node is having intermittent issues.