Again for lack of other software knowledge I first used the suggested traceroute tool Centalhops.
RESULT:
Tracing route to curtin.edu.au [134.7.134.47]...
hop rtt rtt rtt ip address domain name
1 1 0 0 70.84.211.97 61.d3.5446.static.theplanet.com
2 0 0 0 70.84.160.130 vl1.dsr02.dllstx5.theplanet.com
3 0 0 0 70.85.127.109 po52.dsr02.dllstx3.theplanet.com
4 0 0 0 70.87.253.17 et3-2.ibr03.dllstx3.theplanet.com
5 0 0 0 208.172.139.129 dcr2-ge-4-0-0.dallas.savvis.net
6 1 0 0 204.70.193.210 dpr1-so-2-3-0.dallasequinix.savvis.net
7 1 1 1 208.173.178.134
8 4 32 22 144.232.20.80 sl-bb20-fw-6-0.sprintlink.net
9 2 28 2 144.232.11.218 sl-bb21-fw-14-0.sprintlink.net
10 31 32 31 144.232.20.131 sl-bb22-ana-12-0.sprintlink.net
11 76 32 129 144.232.1.150 sl-bb24-ana-8-0.sprintlink.net
12 31 73 32 144.232.1.50 sl-gw28-ana-1-0.sprintlink.net
13 32 46 32 144.232.1.50 sl-gw28-ana-1-0.sprintlink.net
14 197 47 197 202.158.194.77 so-3-1-0.bb1.b.syd.aarnet.net.au
15 209 * 209 202.158.194.33 so-2-0-0.bb1.a.mel.aarnet.net.au
16 218 218 210 202.158.194.33 so-2-0-0.bb1.a.mel.aarnet.net.au
17 219 245 245 202.158.194.5 so-0-1-0.bb1.a.per.aarnet.net.au
18 246 246 246 202.158.198.178 gigabitethernet0.er1.curtin.cpe.aarnet.net.au
19 245 245 245 202.158.198.186 gw1.er1.curtin.cpe.aarnet.net.au
20 246 245 246 202.158.198.186 gw1.er1.curtin.cpe.aarnet.net.au
21 246 245 245 134.7.248.65 te1-1.b309-sr.net.curtin.edu.au
22 246 246 246 134.7.134.47 prodweb2.curtin.edu.au
Trace complete
-- end --
URL for this output return to CentralOps.net
I tried it using the alternative traceroute suggested (Network tools) and surprised to find a different result:
TraceRoute to 134.7.134.47 [curtin.edu.au]
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 66.98.244.1 gphou-66-98-244-1.ev1servers.net
2 0 0 0 66.98.241.16 gphou-66-98-241-16.ev1servers.net
3 0 0 0 66.98.240.14 gphou-66-98-240-14.ev1servers.net
4 1 1 1 129.250.11.141 ge-1-12.r04.hstntx01.us.bb.gin.ntt.net
5 2 1 1 129.250.2.230 xe-0-1-0.r21.hstntx01.us.bb.gin.ntt.net
6 1 1 1 129.250.3.62 xe-0-0-0.r20.hstntx01.us.bb.gin.ntt.net
7 37 37 37 129.250.4.112 p64-1-3-0.r21.lsanca03.us.bb.gin.ntt.net
8 37 75 37 129.250.3.159 p16-1-0-0.r02.lsanca03.us.bb.gin.ntt.net
9 199 199 198 198.172.90.102 so-2-1-0.a00.lsanca02.us.ce.verio.net
10 195 195 195 202.158.194.77 so-3-1-0.bb1.b.syd.aarnet.net.au
11 207 207 207 202.158.194.33 so-2-0-0.bb1.a.mel.aarnet.net.au
12 216 216 216 202.158.194.17 so-2-0-0.bb1.a.adl.aarnet.net.au
13 243 243 243 202.158.194.5 so-0-1-0.bb1.a.per.aarnet.net.au
14 244 243 243 202.158.198.178 gigabitethernet0.er1.curtin.cpe.aarnet.net.au
15 244 244 244 202.158.198.186 gw1.er1.curtin.cpe.aarnet.net.au
16 243 243 244 134.7.250.18 -
17 244 243 243 134.7.248.65 te1-1.b309-sr.net.curtin.edu.au
18 244 243 244 134.7.134.47 prodweb2.curtin.edu.au
Trace complete
Depending on the internet tool used I get 22 or 18 hops and 246 or 244 ms. Both highlighted the ISP for curtin as 134.7.134.47, which was different to the answer in the self test, however reading posts on the discussion boards from students way ahead of me - I understand that this result is correct.
Whilst I cut and pasted an answer into my offical learning log online - I find it easier to use a blog to record details. I have posted a question as to if we need to maintain both or if results in a blog will suffice.!?
More, more, more I say(!).....so I downloaded the Two Cows freeware A-toolbar to see the traceroute from my computer to curtin and received a much shorter result. 19 hops in 242 ms.
Thursday, 7 December 2006
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment