After visiting how it works.com to find out about traceroute, I started with the first part of the excercise which was to traceroute from centralops.net to curtin.edu.au.
I have listed the results below:
Tracing route to curtin.edu.au [134.7.179.10]...
hop rtt rtt rtt ip address
1 0 0 0 70.84.211.97
2 0 0 0 70.84.160.129
3 1 0 0 70.85.127.105
4 0 0 0 70.87.253.5
5 0 0 0 157.238.225.5
6 1 0 0 129.250.3.121
7 8 15 15 129.250.4.71
8 41 50 47 129.250.4.112
9 41 41 41 129.250.3.159
10 41 41 41 198.172.90.102
11 197 197 197 202.158.194.153
12 209 209 209 202.158.194.33
13 218 218 218 202.158.194.17
14 245 245 245 202.158.194.5
15 245 245 245 202.158.198.178
16 246 246 246 202.158.198.186
17 246 246 246 134.7.250.18
18 246 246 248 134.7.248.65
19 246 246 246 134.7.179.10
All up there were 19 hops.
The average time in milliseconds from the tools site to cutin was 246 milliseconds.
Cutins' IP address is: 134.7.179.10
Part 2
Not having had any experience with pinging or traceroute I decided to download the A-Toolbar from www.tucows.com to learn more about the process.
The A-Toolbar had heaps of features, most of which I will never use but most importantly it had the ping and traceroute functions which were both presented with an easy to use interface.
To start off with I 'pinged' the curtin site from my computer using the A-Toolbar. The reults were slightly quicker than 'pinging' from centralops. The average time to ping from centralops was 246 ms but from my own computer it was 225 ms. I believe this is because 'pinging' from my computer is a more dirrect route.
To confirm the results I also 'pinged' curtain from the ms-dos window on my computer.
Here are the results:
The results match up pretty closely. Slight variations could be caused by the fact that I did them at differnent times, meaning there could have been slightly more or less internet traffic.
Part 3
Using my A-Toolbar I also performed the traceroute operation from my computer to the curtain site. Here are the results:
I had exactly the same number of hops from centralops to curtin as I did with my computer to curtin.
I also backed up my results by performing the traceroute task from the ms-dos window on my computer to curtains site. The results once again were the same:
I encountered one small problem along the way, in that I inadvertantly entered the curtin.edu.au adress incorrectly into the ms-dos wind. As a result my computer kept telling me that it was unable to resolve the target system name.
I soon discovered the way around this was to simply enter the IP address: 134.7.179.10, and the treaceroute operation was sucessfully performed.
Conclusions
Traceroute and pinging are operations which are an asset to anyone working in the IT field.
In fact later on in the afternoon, I was notified that a printer in the office had apparently 'broken down'. I was out of the office at the time and my first reaction was that it had probably come off line. I realized that the ideal way to check this would be to ping it from my laptop. I simply entered the printers IP address (192.168.1.5) into my ms-dos window and performed the ping operation. Sure enough the reults came back positive! No question about the printer not being online, and a very handy diagnostic tool to have when you are in a remote location.
I also found the centalops.net website very handy. Its probably the most convienient way to assertain an IP address that I know of.
No comments:
Post a Comment