When she does an extended traceroute from Router A it works fine to everywhere! It also works fine if she does a traceroute from the server to 188.8.131.52! All other addresses on the lan report this problem apart from 2 others 184.108.40.206 and 220.127.116.11.
Even worse when she does a recorder ping the packets hits the correct ip first time the same when she does a recorder traceroute.
We have no visibility of the other peering routers so I cannot see the config but I cannot understand why a packet destined for one ip on a lan would be responded to by another and then finally passed on to its final destination. I can't see how it can be a routing issue because an extended traceroute from the lan the server is on works fine?????
Re: Very weird traceroute problem!?!?! (Hair about to be pulled!
The routing tables are going to tell the story on this one. What I would do, is get a copy of the routing table for all hops involved. At the very least the "sh ip route x.x.x.x" for the source and destinations involved. Using this you should be able to tell where the breakdown is.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...