I hope this helps. If the gateway,or router is offline, my experiance has shown that the ping will result in "expired in transit." If the end device is offline, the result is "request timed out."
Expired in transit (wierd way of saying it, you must be using a MS programme) means that there were more hops to the destination than the time to live field was set to (i.e. TTL=17 but 19 routers to the dest. or something like that).
Cheers Henrik Morsing
IBM Certified AIX 4.3 Systems Administration
Heya Lisa,
Was just going through these forums and came across your post. I am having the same problem that you described above and am not knowledgable enough to know how to fix it. I have a remote site that we connect to via a point to point with Intel 9525 routers on each side. On the CO side, we have a Cisco 2611 connected to the internet via a frame-relay. I have several of these remote sites set up so far but this one is puzzling me. When I attempt to ping the LAN address of the remote router I get:
Reply from 63.145.200.1 TTL expired in transit
Reply from 63.145.200.4 TTL expired in transit
When I do a tracert to the remote address , it just bounces back and forth between these two routers.
If you are bouncing back and forth between two routers you probably have a routing loop problem. Router A thinks the best path is thru router B... router B thinks best path is thru router A... so on and so on until the TTL value decreases to 0. I would look at the routing tables on the two questionable routers to try to figure out why this is happening.
Are you using static routing or some routing protocol like RIP? Depending on the version, RIP can be prone to routing loops.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.