CoreNetworkZ.com

Search This Blog

TTL Expired in Transit — Reason and Solution

TTL Expired in Transit is one of the common error messages you may receive while you ping a remote host. This tutorial explains what does this error message «TTL Expired in Transit» actually means and how to solve it.

In simple words, TTL Expired in Transit tells the Time To Live value set for the ping packets reduced to zero while traveling through the network before reaching the destination. Let us check the reasons for this issue and how to fix it.

TTL value set on a packet in a way to reduce it by one when the packet passes through a hop in the network.

For example, if the Time To Live value on a packet is 3, it will pass through 3 hops. In the third hope, the TTL value reduces to become zero.

So, what happens when TTL expires? The packet will not travel to the next hop.

This procedure helps to avoid the infinite looping of packets.

Possible Reasons for TTL Expired in Transit
Let us check the reasons for receiving the ping reply TTL Expired in Transit.

Faulty Routing loop due to wrong network settings

TTL Value of a packet is set very low

How to Solve TTL Expired in Transit
To fix this issue, we need to find the reason behind this error message. The step by step solution provided in this article will help you solve this issue.

Use the Tracert to Check the actual location of the error

The first step is to perform a tracert test and check the actual location of the error.

On Windows Platform
Open the command prompt on your Windows computer. Type tracert www.corenetworkz.com and press the enter button.

On Linux Platform
Open the Linux terminal and type traceroute www.corenetworkz.com and press enter key.

If you are not sure about the working of this command, you may visit the link below.
How to Use the Tracert command

Check the Routing Table for an infinite loop
In most of the scenarios, the reason behind receiving the TTL Expired in Transit is a misconfigured router and a routing loop.

We need to correct the router configuration and make sure that there is no routing loop.

We can check the routing table on a computer by using the command prompt command provided below.

This command will show the routing table stored on your PC.

If you receive TTL Expired in Transit error on Cisco devices, you need to use a different command to fix it.

For Cisco, the command to display the Routing table is show ip route .

If you have Juniper devices on your network, you should use show route table command.

You need to delete the wrong entry in the routing table to resolve TTL Expired in Transit error.

To delete a wrong entry on your routing table, use the route delete command.

Increase the Time To Live value of a packet

We also need to make sure that the Time To Live value set for the packet is reasonable.

You can increase the TTL value of a packet by using the -i parameter with the ping command.

I hope this tutorial helped you to identify and rectify the ping reply TTL Expired in Transit error. Destination Host Unreachable and Destination Net Unreachable are the other two important ICMP error messages I faced before.

Ttl expired in transit windows

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I’m having a small issue with my Windows Server 2012 R2

I have a Network setup here at the Hotel I work for, and our CCTV contractors didn’t do half of what they were suppose to do with having Network accessible for the MileStone Xprotect software, however they got the Software up and running and displaying all cameras and installed Mobile Client and Remote Client, now I have the Windows 2012 Server with nothing installed on it beside MySQL for the MileStone Software.

I have my Core Switch running as an IP of 10.2.100.1 and Users Network as 10.2.18.1, and couple other guest networks and TV network and Phone network, all that work with no problem, using HP Switches, so my problem here falls as the following, I added a VLAN on the switch 10.2.25.250 and I gave the Windows Server 2012 Static IP of 10.2.25.100, and configured the DNS, now my problem here is that I can’t see anything on the Network from my Windows Server Machine, and I can’t ping that IP range from any other User on the network, I keep getting TTL expired in transit, and tracert keep looping same IP address of 10.2.18.1. infinite looping, now my problem here is that I don’t know where this loop is coming from, and when I setup the Network as Automatic on Server 2012, I get internet connection and can see the Network (reads as 10.2.18.x but when I setup IP 10.2.25.100 (which what I want it to be) I cant see anything and when I troubleshoot the problem with Windows troubleshoot, I get «Gateway not found» so how to fix this problem where I can have this Server accessible on the network where I can view the cameras from other User PCs within the Network?

TTL Expired In Transit Error and Solution

TTL is the short code for Time To Live. TTL is located in IP packets where it is used to hold the count of intermediate hops. TTL is value is set by source host. Windows operating system set it to 64 where Linux operating systems set to 128. Every router or intermediate host the packet pass will decrease the TTL value of the IP packet.

TTL generally used with different network troubleshooting tools like tracert, ping etc. TTL value provides the intermediate host counts.

Trace To Google

In this part we will trace to the google.com where there is no TTL related restriction for IP packet transfer. We will use tracepath command with the remote host name which is google.com .

Trace To Google

Too Many Hops

Now we will set very low TTL value where it will reach 0 in 4. hop. We will use -m with the 4 which is TTL.

Too Many Hops

Solution or Fix – Increase The TTL Value

We will change the TTL value to the 255 which is the maximum and works like a charm. If it is not working there is loop in the network between source and destination.

Increase The TTL Value

Ttl expired in transit windows

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

i ping my dsl ip 203.115.130.8 -t and after 20 request time out it has reply 121.96.1.106 TTL expired in transit

and then i typed netstat -rn in ping

C:\Users\user>netstat -rn
===========================================================================
Interface List
12. 00 26 2d 9b 81 00 . Broadcom NetLink (TM) Gigabit Ethernet
11. 78 e4 00 18 b6 ea . Atheros AR5B93 Wireless Network Adapter
1. Software Loopback Interface 1
42. 00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
39. 00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
41. 00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 20
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.2 276
192.168.1.2 255.255.255.255 On-link 192.168.1.2 276
192.168.1.255 255.255.255.255 On-link 192.168.1.2 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.2 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.2 276
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
41 58 ::/0 On-link
1 306 ::1/128 On-link
41 58 2001::/32 On-link
41 306 2001:0:9d38:6ab8:3418:d8c6:3428:8bf2/128
On-link
11 276 fe80::/64 On-link
41 306 fe80::/64 On-link
41 306 fe80::3418:d8c6:3428:8bf2/128
On-link
11 276 fe80::f80d:1df:ae07:d292/128
On-link
1 306 ff00::/8 On-link
41 306 ff00::/8 On-link
11 276 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

——————after that i trace the route

Tracing route to 203.115.130.8 over a maximum of 30 hops

Ttl expired in transit windows

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I’m having a small issue with my Windows Server 2012 R2

I have a Network setup here at the Hotel I work for, and our CCTV contractors didn’t do half of what they were suppose to do with having Network accessible for the MileStone Xprotect software, however they got the Software up and running and displaying all cameras and installed Mobile Client and Remote Client, now I have the Windows 2012 Server with nothing installed on it beside MySQL for the MileStone Software.

I have my Core Switch running as an IP of 10.2.100.1 and Users Network as 10.2.18.1, and couple other guest networks and TV network and Phone network, all that work with no problem, using HP Switches, so my problem here falls as the following, I added a VLAN on the switch 10.2.25.250 and I gave the Windows Server 2012 Static IP of 10.2.25.100, and configured the DNS, now my problem here is that I can’t see anything on the Network from my Windows Server Machine, and I can’t ping that IP range from any other User on the network, I keep getting TTL expired in transit, and tracert keep looping same IP address of 10.2.18.1. infinite looping, now my problem here is that I don’t know where this loop is coming from, and when I setup the Network as Automatic on Server 2012, I get internet connection and can see the Network (reads as 10.2.18.x but when I setup IP 10.2.25.100 (which what I want it to be) I cant see anything and when I troubleshoot the problem with Windows troubleshoot, I get «Gateway not found» so how to fix this problem where I can have this Server accessible on the network where I can view the cameras from other User PCs within the Network?