Invisible§niper Posted February 20, 2006 Report Share Posted February 20, 2006 Does anyone know a good explanation of the tracert command's results?Thanks Quote Link to comment Share on other sites More sharing options...
andsome Posted February 20, 2006 Report Share Posted February 20, 2006 Plenty of explanations HERE! Quote Link to comment Share on other sites More sharing options...
homecomputeraid Posted February 20, 2006 Report Share Posted February 20, 2006 Tracert simply shows the hops (routers) between you and the address you're tracerouting to. Bear in mind that network devices are often configured not to reply, so results can be sketchy. Quote Link to comment Share on other sites More sharing options...
Invisible§niper Posted February 21, 2006 Author Report Share Posted February 21, 2006 Tracert simply shows the hops (routers) between you and the address you're tracerouting to. Bear in mind that network devices are often configured not to reply, so results can be sketchy.When an asterix appears in a tracert result does can this mean that the node is behind a firewall? It's just that I tried to do a tracert for www.commonwealthbank.com.au and the last 15 results timed out. Here is what I got:Tracing route to www.commonwealthbank.com.au [203.17.185.190]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.254 2 37 ms 37 ms 39 ms CAI22605-5.gw.connect.com.au [210.9.87.65] 3 38 ms 38 ms 38 ms bay.bne.nq.net [210.11.152.1] 4 41 ms 43 ms 41 ms r50.zebra.cns.nq.net [202.4.31.50] 5 38 ms 41 ms 41 ms garnet-ge1.getonit.net.au [202.47.112.1] 6 39 ms 39 ms 41 ms fasterthernet3-1-515.cor1.for.connect.com.au [203.63.65.194] 7 41 ms 40 ms 40 ms gigabitethernet0-1.bdr2.for.connect.com.au [203.63.176.114] 8 41 ms 41 ms 45 ms ge-0-1-1.dst1.for.connect.com.au [203.63.217.254] 9 41 ms 41 ms 42 ms so-2-0-0.cre1.for.connect.com.au [202.10.0.105] 10 71 ms 42 ms 42 ms so-3-0-2.cre1.bri.connect.com.au [202.10.0.56] 11 58 ms 58 ms 58 ms so-4-0-1.cre1.syd.connect.com.au [202.10.0.33] 12 58 ms 58 ms 57 ms so-0-0-0.dst1.syd.connect.com.au [202.10.0.112] 13 59 ms 61 ms 58 ms gigabitethernet0-2.cor1.syd.connect.com.au [203.63.170.245] 14 60 ms 59 ms 62 ms cba133716-7.gw.connect.com.au [210.8.7.165] 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.Trace complete. Quote Link to comment Share on other sites More sharing options...
homecomputeraid Posted February 21, 2006 Report Share Posted February 21, 2006 I can think of 3 possibilities. 1. It could be behind a firewall.2. It could be a router which is programmed not to respond to ICMP Echo Requests (pings).3. It could be broken or offline. If you can get to the device using HTTP or FTP (or whatever protocol is allowed), but can't ping it, or tracert to it, it's probably behind a firewall. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.