08-16-2006 08:04 PM - edited 03-03-2019 01:41 PM
A normal tracert would be as follows..
Tracing route to dlp6248.cts.com [10.238.25.254]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.236.140.2
2 <1 ms 2 ms <1 ms 10.224.1.5
3 3 ms 2 ms 2 ms 10.224.1.18
4 3 ms 2 ms 3 ms 192.168.1.2
5 11 ms 6 ms 9 ms dlp6248.cts.com [10.238.25.254]
Trace complete.
But i have another trace which has the third column of seconds as * Is there any particular reason for this ? I am troubleshooting one connectivity and have come accross this.
Please help..
Tracing route to ibp6151.cts.com [10.238.25.111]
over a maximum of 30 hops:
1 <1 ms <1 ms * 10.236.140.2
2 <1 ms <1 ms * 10.224.1.5
3 2 ms 2 ms * 10.224.1.10
4 9 ms 2 ms * 192.168.1.2
5 8 ms 2 ms * ibp6151.cts.com [10.238.25.111]
Trace complete.
08-16-2006 08:08 PM
It means that every 3rd packet of the traceroute (or its reply) is getting dropped.. I suspect some connectivity problems along the way. Try and ping each of the addresses in the trace individually to see if all of them make it through.
Paresh
08-17-2006 04:37 AM
Hi
I do belive you can fiddle the tracert command - but before we go through that - try tracing from a terminal connected into the server.
Using windows try tracert or linux use tracert - check if that fails first.
then switch on
debug ip packet detail
run your ping or trace route again and check .
This will show you packet info
check this out for details
http://www.cisco.com/warp/public/63/ping_traceroute.html
Cheers
Malcolm
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: