Hi, Tony.

This shows that there is a router in the chain (likely one of the routers on the return path) that down-prioritizes ICMP TTL Expired packets. Unfortunately, this situation masks the fact that things are working pretty well through these hops. We discuss a similiar situation in our knowledgebase at:

http://www.nessoft.com/esupport/?_a=knowledgebase&_j=questiondetails&_i=2

Always remember that if you're not seeing packet loss or latency problems at the final destination, then any of this data in any of the intermediate hops is a priorization / configuration decision that has been made by some router some place in the route. It is only affecting the data reported on intermediate hops, though, and you're not trying to get to the intermeidate hops - you're trying to get to the final destinatino, which is working fine.