Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Troubleshooting this 'TTL:Expired in transit' message

Imagine from my internal network I ping a client IP on a DSL line, on the Internet. Then my ping reply is:

ping 192.168.0.3

Reply from 145.19.7.3:TTL expired in transit.

What would be the best way to troubleshoot this? Is safe to assume that the target 192.168.0.3 is not receiving my ping, correct?

6 REPLIES

Re: Troubleshooting this 'TTL:Expired in transit' message

It basically tells you the packet didn't get to the destination after maximum the hop count has reached. Do a traceroute and see whether the packets are looping around somewhere or it indeed cross the maximum # of hops?

HTH

Sundar

Community Member

Re: Troubleshooting this 'TTL:Expired in transit' message

Hi, your ping packets have reached the hop limit and expired. You can increase the TTL by using the ping -i command that might solve your problem since you didn't receive host destination host unreachable massage or ping timed out which usually means there is nothing connected on the other end.

DW

Community Member

Re: Troubleshooting this 'TTL:Expired in transit' message

Yes, there is a loop somewhere in this path. I did ping -i 255 and tracert expired because at certain it reached a routing loop, right? I will just notify folks responsible for that target network about the problem. Thanks guys!!

edited output of tracert 192.168.0.3

(...)

13 222 ms 225 ms 222 ms 136.195.33.110

14 221 ms 224 ms 223 ms 136.195.33.109

15 228 ms 269 ms 229 ms 136.195.33.110

16 228 ms 229 ms 237 ms 136.195.33.109

17 234 ms 243 ms 249 ms 136.195.33.110

18 237 ms 250 ms 237 ms 136.195.33.109

19 240 ms 240 ms 239 ms 136.195.33.110

20 310 ms 241 ms 242 ms 136.195.33.109

21 244 ms 245 ms 244 ms 136.195.33.110

22 244 ms 257 ms 244 ms 136.195.33.109

23 298 ms 250 ms 255 ms 136.195.33.110

24 251 ms 253 ms 251 ms 136.195.33.109

25 258 ms 257 ms 275 ms 136.195.33.110

26 376 ms 272 ms 318 ms 136.195.33.109

27 261 ms 265 ms 262 ms 136.195.33.110

28 269 ms 270 ms 262 ms 136.195.33.109

29 268 ms 269 ms 273 ms 136.195.33.110

30 441 ms 386 ms 480 ms 136.195.33.109

Trace complete.

Community Member

Re: Troubleshooting this 'TTL:Expired in transit' message

There's a routing loop. Router with IP 136.195.33.110 thinks the next hop address for destination 192.168.0.3 is 136.195.33.109 and 136.195.33.109 thinks the next hop address for destination 192.168.0.3 is 136.195.33.110. The packet keeps bouncing back and forth between these routers until the TTL reaches 0 then it's discarded and you receive the ICMP time exceeded message.

Community Member

hi all,

hi all,

I have one same kind of case where there is no lopp.. but tracert end on a point. this results in management issue only. not service issue. the node can not be managed

Community Member

Dear 

Dear 

I Have The Same Issue So Could You Please Provide The Solution. There's a Routing Loop 

75704
Views
0
Helpful
6
Replies
CreatePlease to create content