| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 48445 | 2004-08-23 06:24:00 | Pings, tracerts and No Response on First Hop | Jester (13) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 264521 | 2004-08-23 06:24:00 | Hi Some advice please. Whenever I do a tracert the first hop is always timed out. I am using a router which has an ip of 192.168.1.2 and I think that for some reason the router is not responding to the initial tracert pings. From then it carries on as normal (well, as normal as I can get it at the moment - I am having problems with Jetsurf). Is it something to do with the internet gateway or something? Here's an example: Tracing route to pcworld.co.nz [210.48.100.12] over a maximum of 30 hops: 1 * * * Request timed out. <<< Here 2 78 ms 77 ms 78 ms 210-55-64-96.adsl.netgate.net.nz [210.55.64.96] 3 94 ms 93 ms 93 ms 192.168.253.1 4 94 ms 93 ms 93 ms 202.50.119.153 5 94 ms 93 ms 93 ms iconz1.ape.net.nz [192.203.154.44] 6 94 ms 93 ms 93 ms ae-01a.akl.iconz.net [202.14.100.20] 7 94 ms 93 ms 93 ms e0-0.core3.akl.iconz.net.nz [202.14.100.220] 8 94 ms 93 ms 93 ms ip-210-48-113-34.iconz.net.nz [210.48.113.34] 9 81 ms 79 ms 81 ms ip-210-48-100-12.iconz.net.nz [210.48.100.12] Trace complete. |
Jester (13) | ||
| 264522 | 2004-08-23 08:05:00 | Routers can be programmed to filter traffic based on ICMP requests - tracert being one. It is probably blocking the TTL reply, the one that yells at you when the TTL runs out on the way somewhere. It could also be filtering the SYN ACK signal. |
Growly (6) | ||
| 1 | |||||