Encounter reply From:ttl expired in transit._ router, switch

TTL expired in transit
It was a strange thing in the early morning. The other side can not connect to the local host remotely, both ADSL access to the Internet, the network status of all normal. Using the ping command test, the test results are as follows:

C:\ Ping 58.33.46.92

Pinging [58.33.46.92] with bytes of data:

Reply from 61.152.81.25:ttl expired in transit.

Ping statistics for 58.33.46.92:

Packets:sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trips times in Milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

What does it mean that the TTL expired in transit represents the TTL (lifecycle) to expire during the transfer process? Let me explain!
There are two reasons why this problem occurs:

1 TTL value is too small! The TTL value is less than the number of routers you have passed between you and the other host.

2 The number of routers is too many, after the number of routers is greater than the TTL value!

Next, to find out where the problem is, use the tracert command to view the routed route, and the test results are as follows:

C:\ >tracert-d 58.33.46.92

Tracing route to [58.33.46.92]

Over a maximum of hops:

1 6 ms 5 ms 5 ms 192.168.0.1

2 ms 6 ms 5 ms 192.168.0.251

3 245 MS 131 ms 146 MS 61.129.99.217

4 ms Ms 202.101.63.13

5 ms Ms 61.152.81.14

6 ms Ms Ms 61.152.81.5

7 ms Ms 61.152.81.6

8 ms Ms 61.152.81.25

9 ms Ms 61.152.81.26

Ms Ms 61.152.81.5

Ms Ms 61.152.81.6

Ms Ms Ms 61.152.81.25

Ms Ms Ms 61.152.81.26

Ms Ms 61.152.81.5

Ms Ms 61.152.81.6

Ms Ms Ms 61.152.81.25

Ms Ms 61.152.81.26

Ms MS-MS 61.152.81.5

Ms MS-MS 61.152.81.6

Ms MS-MS 61.152.81.25

Ms Ms 61.152.81.26

Ms Ms Ms 61.152.81.5

Ms Ms 61.152.81.6

Ms Ms 61.152.81.25

Ms Ms 61.152.81.26

Ms Ms 61.152.81.5

Ms Ms 61.152.81.6

Ms Ms 61.152.81.25

Ms Ms Ms 61.152.81.26

Ms Ms Ms 61.152.81.5

Trace complete.

By monitoring, it is clear that routing generates loops, which cannot be 61.152.81.5,61.152.81.6,61.152.81.25,61.152.81.26 between the four routes. Therefore, the TTL expired in transit is caused. Because from the 192.168.0.1 (gateway) out, to the 192.168.0.251 (local route), then to the 61.129.99.217 (special line off the net), the last to go out 202.101.63.13-"61.152.81.14 (telecommunications routing) Everything is more normal, Stating that the problem is not local, so it should be the telecommunications problem.

Call Telecom to repair a bit, the business people do not know what is going on about a lot of, he is not very clear, had to say is called a technology to call again, after a while telecommunications technicians call to ask the situation, professionals in the end is not the same, one said to know what the problem, I put the IP newspaper to him, Again in which several routes generated loop also reported, he went to check, a while the problem is resolved, and then ping test to see:

C:\ >ping yurenliang.vicp.net

Pinging yurenliang.vicp.net [58.33.46.92] with bytes of data:

Reply from 58.33.46.92:bytes=32 time=37ms ttl=246

Reply from 58.33.46.92:bytes=32 time=40ms ttl=246

Ping statistics for 58.33.46.92:

Packets:sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trips times in Milli-seconds:

Minimum = 35ms, Maximum = 40ms, Average = 37ms

The problem is solved, but where is the problem? After that, the telecom technician called again to explain. That's the way it turned out. Because this batch of new IP addresses at the beginning of 58 is not optimized, the number of routes that may pass is very much, sometimes may go abroad for a round to return. (Dizzy Oh.) This is the quote from Telecom technology.

There are now two solutions to this problem:

1. When the IP is found to start with 58, redial, it is best to dial to the beginning of 61, so there will be no problem.

2. Like telecom application, replace a port.