Tracert

[HowTo]

Hi All

Need to understand why this happens.
Since the upgrade all is ok, but when using tracert I get this result.
Use different router all with the same result. No speed issue.
Happens with local and international tracert results.
Anybody that could comment on Hop 2.
Used different routers all do the same. Why does hop 2 not reply.
Any body that is on a MSAM that get the same results?


C:\Windows\system32>tracert -d axxess.co.za

Tracing route to axxess.co.za [197.242.150.113]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 13 ms 12 ms 12 ms 41.181.178.18
4 12 ms 11 ms 11 ms 41.181.178.17
5 38 ms 11 ms 11 ms 41.181.165.115
6 11 ms 47 ms 11 ms 196.31.180.4
7 13 ms 13 ms 12 ms 196.44.0.224
8 12 ms 12 ms 11 ms 196.44.31.99
9 12 ms 12 ms 11 ms 196.31.220.6
10 12 ms 12 ms 12 ms 196.31.220.23
11 11 ms 12 ms 11 ms 196.31.63.206
12 12 ms 16 ms 11 ms 196.30.42.133
13 12 ms 12 ms 12 ms 197.242.150.113

Trace complete.

Anybody that wants to comment.
Did not happen before the upgrade. This is what I noticed.

 

[TEXTILE GUY]

Hi All

Need to understand why this happens.
Since the upgrade all is ok, but when using tracert I get this result.
Use different router all with the same result. No speed issue.
Happens with local and international tracert results.
Anybody that could comment on Hop 2.
Used different routers all do the same. Why does hop 2 not reply.
Any body that is on a MSAM that get the same results?


C:\Windows\system32>tracert -d axxess.co.za

Tracing route to axxess.co.za [197.242.150.113]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 13 ms 12 ms 12 ms 41.181.178.18
4 12 ms 11 ms 11 ms 41.181.178.17
5 38 ms 11 ms 11 ms 41.181.165.115
6 11 ms 47 ms 11 ms 196.31.180.4
7 13 ms 13 ms 12 ms 196.44.0.224
8 12 ms 12 ms 11 ms 196.44.31.99
9 12 ms 12 ms 11 ms 196.31.220.6
10 12 ms 12 ms 12 ms 196.31.220.23
11 11 ms 12 ms 11 ms 196.31.63.206
12 12 ms 16 ms 11 ms 196.30.42.133
13 12 ms 12 ms 12 ms 197.242.150.113

Trace complete.

Anybody that wants to comment.
Did not happen before the upgrade. This is what I noticed.

Just guessing - it could well be that the ping info request is being denied at the MSAN gateway on hop 2.
That would explain why all routers would show the same, but speed is no issue??

 

[Pada]

It is nothing to be concerned about. The PPPoE gateway or something is just not sending an ICMP reply when the TTL value has been reached.

Tracert works by sending ICMP packets with incrementing TTL values (amount of hops before the packet should expire).
So it would start off with one with TTL=1, and then the first hop (10.0.0.2) would reply saying that the TTL has expired.
Then tracert would send one with TTL=2, then the second hop (the router's PPPoE connection's gateway) would normally reply with the TTL that has expired - but in your case it simply does not reply.
Tracert then sends an ICMP packet with TTL=3, ..., until it reached the final destination or exceeded the maximum amount of hops, which is typically 32 hops.

 

[HowTo]

Hi All

Did some more searching and found this.
The new CMTS does not respond to ICMP, hence you see a time out.

Don't know if this applies to MSAN?