Or there is no route configured for 172.10.254.81's network on your router. your router passes your ping request to its default gateway, and there it gets lost.
that sounds to me like a more possible reason..
Main Topics
Browse All TopicsHello,
Ping response shows "TTL expired in transit". What does it mean and how to troubleshoot this issue? Please explain.
Example:
Pinging 172.10.254.81 with 32 bytes of data:
Reply from 172.16.1.254: TTL expired in transit.
Reply from 172.16.1.254: TTL expired in transit.
Reply from 172.16.1.254: TTL expired in transit.
Reply from 172.16.1.254: TTL expired in transit.
Ping statistics for 172.10.254.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Thanks,
Ashok
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: calvinetterPosted on 2006-11-14 at 20:58:02ID: 17944400
Looks like you've got a routing loop, so you're probably running a routing protocol such as RIP, EIGRP, OSPF, etc ? A loop could be caused by an interface or router going up & down often, misconfigured routes, etc.
Check the routing tables & configs on your routers & layer-3 switches (if present), check for downed links or "flapping" links, ie an interface that persistently keeps going up/down, duplex mismatches on interfaces, etc.
See also the "Impact of Routing Loops..." section on MS's website: http://tinyurl.com/stean
cheers