Child Item

Site Totals

61368 Questions Answered 267 Categories

Tracert incorrect response

On all of my home Windows PCs - wireless, XP, and Vista - when i do a tracert, it looks like the response is as expected except instead of showing the IP or name of the node at which TTL expired it shows the IP or name of the site I am tracerting to. Even in the sniff, to every ping starting with TTL of 1 someone is putting the tracert destination IP in the Time-to-live exceeded response message. I'm guessing it is the Verizon router but why and how do you fix it.

I see the response time gradually increase as the hops get further away and the tracert termiantes normally, but each line always says the name of the final destination, not the name or IP of each hop as TTL expires.

HELP.

Comments

dslr595148

Huh?

Do you posting an example of what you expected to see, and an example of what you see?

--

The text file from it...

As need be, see

http://www.more.net/technical/pingtrace.html

rdrombosy

here is a typical response from my new home FIOS network:

H:\Users\rdvista>tracert fubar.com

Tracing route to fubar.com [66.238.90.231]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
2 5 ms 4 ms 6 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
3 4 ms 4 ms 5 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
4 11 ms 11 ms 11 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
5 13 ms 14 ms 13 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
6 14 ms 14 ms 14 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
7 14 ms 16 ms 14 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
8 15 ms 16 ms 15 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
9 84 ms 85 ms 85 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
10 86 ms 86 ms 85 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
11 85 ms 85 ms 85 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
12 99 ms 97 ms 95 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]
13 88 ms 88 ms 88 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]

Trace complete.

Wierd huh? Sniff/wireshark capture shows the time to live exceeded is always 66.238.90.231, from the first probe with TTL = 1 until the end. Someone (the router?) has to be changing the value of the source of the time exceeded packet. Why? How can it be fixed?

FYI FIOS phone support does not know what a traceroute is. Perhaps there is someone on this forum from Verizon who can help.

(for completeness, here is a tracert to the same site from other than my FIOS home network.)

Tracing route to fubar.com [66.238.90.231]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms vl10.eh-core-2.gw.xxx.edu [136.142.xxx.yyy]
2 <1 ms <1 ms <1 ms te1-1.cl-core-2.gw.xxx.edu [136.142.xxx.yy]
3 <1 ms <1 ms <1 ms ge-2-0-0-712.externals-cl.gw.xxx.edu [136.142.x.yyy]
4 <1 ms <1 ms <1 ms car-mi.xxxx.net [147.73.16.172]
5 * * 28 ms cbr-mi-core-ge-0-1-0-16.xxxx.net [147.73.xyx.yyx]
6 4 ms 3 ms 3 ms ge-3-3-0.405.ar2.cle1.gblx.net [208.49.224.197]

7 11 ms 12 ms 57 ms te9-2-10G.ar2.CHI2.gblx.net [67.17.109.114]
8 12 ms 12 ms 12 ms 206.111.2.13.ptr.us.xo.net [206.111.2.13]
9 13 ms 13 ms 15 ms 207.88.12.141.ptr.us.xo.net [207.88.12.141]
10 13 ms 13 ms 13 ms ge7-0-0d0.rar1.chicago-il.us.xo.net [65.106.1.41
]
11 64 ms 76 ms 36 ms p6-0-0.rar2.denver-co.us.xo.net [65.106.0.25]
12 37 ms 36 ms 37 ms p0-0-0d0.RAR1.Denver-CO.us.xo.net [65.106.1.73]

13 72 ms 72 ms 72 ms p6-0-0.rar1.sanjose-ca.us.xo.net [65.106.0.21]
14 73 ms 72 ms 72 ms p0-0-0.MAR1.Fremont-CA.us.xo.net [65.106.5.134]

15 72 ms 72 ms 73 ms p0-0.chr1.fremont-ca.us.xo.net [207.88.80.178]
16 80 ms 80 ms 191 ms 207.88.3.230.ptr.us.xo.net [207.88.3.230]
17 73 ms 72 ms 72 ms 66.238.90.231.ptr.us.xo.net [66.238.90.231]

Trace complete.

dslr595148

I searched with Google for fios trace route

And this was one of the results that came back.

http://www.dslreports.com/forum/remark,16508717

DSLR (dslreports.com) Forums » US Telco Support » Verizon » Verizon Fiber Optics » [new technologies] New ActionTec Router breaks Traceroute

--

I have to wonder if it the same issue...

Child Item