HI,
I'm facing a peculiar situation, the trace below can be completed until 190.90.15.3 (destination IP address) but at the same time, I don't have HTTP (80) access to this.
C:/cmd>tracert s.yimg.com
Trace to fo-coa-s.aycs.b.yahoodns.net [190.90.15.3]
1 94 ms 90 ms 87 ms 201.x.x.x
2 92 ms 92 ms 85 ms 172.x.x.x
3 83 ms 76 ms 75 ms 10.x.x.x
4 60 ms 64 ms 64 ms 10.x.x.x
5 110 ms 80 ms 80 ms 10.x.x.x
6 135 ms 141 ms 146 ms 213.248.89.153
7 226 ms 167 ms 138 ms 213.155.130.240
8 142 ms 146 ms 144 ms 62.115.138.25
9 165 ms 165 ms 157 ms 62.115.141.71
10 164 ms 167 ms 173 ms 62.115.33.22
11 202 ms 208 ms 215 ms 200.16.69.61
12 209 ms 196 ms 205 ms 200.16.70.174
13 * * * Request timed out.
14 * 189 ms * 190.90.11.134
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 238 ms 236 ms * 190.90.15.3
19 * * * Request timed out.
20 * * * Request timed out.
21 239 ms * * 190.90.15.3
22 * * * Request timed out.
23 * * * Request timed out.
24 216 ms * 199 ms 190.90.15.3
Trace complete.
What I see (and the reason why I'm asking here) is a kind of loop behavior in the last jump, as is visible the destination IP address is bounding 3 times.
I'm not passing through a firewall or any kind of restriction in my way to the router, so I wondering why this behavior and if it is due the routing tables outside my network.
I'm using a cisco 12406 IOS v12, is it possible to test [ip.dest:80] inside the router, to check if this port is reachable from the router or at least packets are leaving on a interface, So how can I do it?
C:/cmd>nc -vv 190.90.15.3 80 ... (9 sec) Connection timeout
Any help/opinion/light will be welcome.
