Well after some quick panicing and then lots of fiddling i've got my post from last night to now display.... *phew*
I came online to check out (admire) my blog today and realised that my last blog entry from last night was missing. This of course caused immediate panic as it contained information and results that i really didn't want to redo. Once the initial panic died down and the reasoning started to enter i remember reading at the bottom of this entry screen continually "now blogger saves your drafts automatically" so i knew that at least "most" of last nights efforts would be out there in cyber space somewhere and i just had to find them.
First i logged in to the blogger website and found the "manage posts" section and saw that two posts had the options of edit and view whereas the third post could only be edited. Ah ha - the elusive post had been found. I then did a quick check and found that i had lost some initial foratting so i went through and fixed this up and then published. After viewing the post however some of the copy/pasted information had gone haywire! I had no idea how to fix this! I decided to click the scary button of Edit Html to see if i could see here what was going wrong. I am not a html expert by any means but can read and have a vague understand of the tags and see what is happening. For some reason this body of text had an extra "size" tag. Firstly i was going to manually go through and remove these tags, but then i remember that there was a "remove formatting from selection" button in the compose view so i used this to totally clear the formatting and thus the offending tags. I then reformatted and previewed my text again.
The size issue had been repaired, but now the text was skipping some "enters". I went through then and deleted and pressed enter at the end of each line in hope it would make this enter register to the computer and finally after some fiddling around my post is now there and looking its beautiful self.
This i realised was the perfect opportunity to log some problems and learning experiences so here i am!
I have been using colour coding for all my copy/pasted information so far purely to make it stand out as separate from my own writing but now to formalise this a little more...
red: written quotes from online sources
purple: questions from the modules
green: results
Think this is all i'm using!
Signing out for now, Kellie.
Thursday, November 29, 2007
Module 1 - Further Exploration
I decided that although this was more like an extra for the module that anything extra is probably worth exploring!
Firstly i downloaded the A-Tool bar (freeware) which seems to have attached everywhere freeware tool and resource imaginable with it. I did a trace to the webct.curtin.edu.au which took 22 hops at approx 89ms. I then decided to discuss this further with a fellow student Greg.
~~Mekala**Belyssa~~ says: did you use the toolbar to get the trace program installed?
greg says: i actually did, but there is a much easier way, the command is in dos. Are you using win xp?
~~Mekala**Belyssa~~ says: aye
greg says: if you go to the command prompt... hold down the windows key on your keyboard and press 'r' then type 'cmd' and press enter...
~~Mekala**Belyssa~~ says: aye
greg says: type 'tracert'
greg says: gives you a list of your options
~~Mekala**Belyssa~~ says: got that
greg says: type 'tracert' followed by a space then the site, cant remember what it is off the top of my head greg says: and that will give you all the required info
~~Mekala**Belyssa~~ says: cool i know the site on my head ~~Mekala**Belyssa~~ says: sweet! is tracing it now
~~Mekala**Belyssa~~ says: that IS easier!
~~Mekala**Belyssa~~ says: (something else for my learning log)
The result that i got from the command prompt was 21 hops at approx 90ms, however i believe that it timed out before achieving the last hop.
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 251 ms
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 246 ms
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 251 ms
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 250 ms
Average time over 10 pings: 249.8 ms
To check the ping results from my computer to the webct site i firstly used the A-tool bar, which told me that it takes 87ms to ping webct, and i guessed that to use ping in the command bar would be similar to using it for tracing. I guessed that "ping webct.curtin.edu.au" would be the way to go and i was correct. Using the command bar the ping result i got was 87ms and this was averaged over 4 goes.
I notice as i'm writing this that i am not always sure of the correct words to express myself - leaps, jumps, moves, goes, servers, computers, etc! - hopefully this will come as i progress further in this course.
Until Module 2 (or perhaps before)
Kellie.
Firstly i downloaded the A-Tool bar (freeware) which seems to have attached everywhere freeware tool and resource imaginable with it. I did a trace to the webct.curtin.edu.au which took 22 hops at approx 89ms. I then decided to discuss this further with a fellow student Greg.
~~Mekala**Belyssa~~ says: did you use the toolbar to get the trace program installed?
greg says: i actually did, but there is a much easier way, the command is in dos. Are you using win xp?
~~Mekala**Belyssa~~ says: aye
greg says: if you go to the command prompt... hold down the windows key on your keyboard and press 'r' then type 'cmd' and press enter...
~~Mekala**Belyssa~~ says: aye
greg says: type 'tracert'
greg says: gives you a list of your options
~~Mekala**Belyssa~~ says: got that
greg says: type 'tracert' followed by a space then the site, cant remember what it is off the top of my head greg says: and that will give you all the required info
~~Mekala**Belyssa~~ says: cool i know the site on my head ~~Mekala**Belyssa~~ says: sweet! is tracing it now
~~Mekala**Belyssa~~ says: that IS easier!
~~Mekala**Belyssa~~ says: (something else for my learning log)
The result that i got from the command prompt was 21 hops at approx 90ms, however i believe that it timed out before achieving the last hop.
Traceroute from your computer to curtin.edu.au: compare the number of hops with the earlier traceroute.
What sort of differences can you observe?
The main difference is probably the most obvious and links in with the comments below about pinging (yes i have not necessarily done all these activities in the same order as listed) in that the message only needs to travel within australia to get from my computer to webct. When the message traveled from the net tools site it first moved through the server that I'm guessing that the net tools site is attached to, then to another server, before coming over to .au servers. I also could see that when going from my computer that most of the hops were within Telstra servers, first in Brisbane, then to Sydney, Melbourne, Adelaide and finally Perth. Once in Perth in then went over to the curtin.edu.au server. Following through the Telstra servers makes sense as Telstra (bigpond) is my ISP, but i never before thought about the number of servers that Telstra would have!Ping the webct site and compare the time with the time taken to ping from the net tools site. Is it less or more than you expected?
Why?
Firstly i went back and used the net tools site to ping and got the following results:[curtin.edu.au]
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 251 ms
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 246 ms
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 251 ms
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 250 ms
Round trip time to 134.7.179.53: 250 ms
Average time over 10 pings: 249.8 ms
I expected that it would be much quicker to ping to the webct site from my computer then from the net tools site as i figured it would be less "hops". Both my computer server and the webct computer server are in Australia, whereas looking at the net tools site i would say that it has an american server. Although the time that we are talking about is just in ms, it still has a lot further to travel then just across the country.
To check the ping results from my computer to the webct site i firstly used the A-tool bar, which told me that it takes 87ms to ping webct, and i guessed that to use ping in the command bar would be similar to using it for tracing. I guessed that "ping webct.curtin.edu.au" would be the way to go and i was correct. Using the command bar the ping result i got was 87ms and this was averaged over 4 goes.
I notice as i'm writing this that i am not always sure of the correct words to express myself - leaps, jumps, moves, goes, servers, computers, etc! - hopefully this will come as i progress further in this course.
Until Module 2 (or perhaps before)
Kellie.
Wednesday, November 28, 2007
Module 1 - Part 2.....
Well i am back and continuing on my work of the activities for Module one.
My first task for this was to look at the How Stuff Works on Traceroutes. Now i understood what it was saying, while skimming over the technical names for some of the components, but due to the title of the article the link from Mod 1 took me to, I wasn't sure that i was reading the right thing! Before continuing on to the practical side of this activity i decided to do a little more research into "Traceroutes". Using my search engine of choice (google) i entered in a search for "Traceroute explanation". As you are probably all expecting (but i'm not sure that i was!) i had a huge result. I usually choose the link to go to by skimming the little explanation paragraph under each link. Finding one that promised an explanation with diagrams (beauty!) I followed this link, but was disappointingly taken to a forum that required membership (free). So i tried again. Top of the list i followed through this link and got this fantastic description! Things could not be clearer for me now...
Traceroute is the program that shows you the route over the network between two systems, listing all the intermediate routers a connection must pass through to get to its destination. It can help you determine why your connections to a given server might be poor, and can often help you figure out where exactly the problem is. It also shows you how systems are connected to each other, letting you see how your ISP connects to the Internet as well as how the target system is connected.
This quote was taken from here.
I really wanted to see how all this works, so i decided to continue on with the activities. Firstly i used the free tools to traceroute to curtin.edu.au. I was a bit thrown by these sites to begin with - i used the first link first (http://centralops.net/co/) but found that i didn't really know what i was doing. I had a bit more of a look around the internet at various traceroute apps - then reread the instructions for the activity. Opening the second provided link (http://network- tools.com/ ) i decided to go on blind faith and just copy/pasted the curtin server into the box provided and recieved the following results:
The IP address that i traced to for curtin.edu.au was 134.7.179.53 as shown in the above results.
Will be tackling the further explanation later!
Bye for now! Kellie.
My first task for this was to look at the How Stuff Works on Traceroutes. Now i understood what it was saying, while skimming over the technical names for some of the components, but due to the title of the article the link from Mod 1 took me to, I wasn't sure that i was reading the right thing! Before continuing on to the practical side of this activity i decided to do a little more research into "Traceroutes". Using my search engine of choice (google) i entered in a search for "Traceroute explanation". As you are probably all expecting (but i'm not sure that i was!) i had a huge result. I usually choose the link to go to by skimming the little explanation paragraph under each link. Finding one that promised an explanation with diagrams (beauty!) I followed this link, but was disappointingly taken to a forum that required membership (free). So i tried again. Top of the list i followed through this link and got this fantastic description! Things could not be clearer for me now...
Traceroute is the program that shows you the route over the network between two systems, listing all the intermediate routers a connection must pass through to get to its destination. It can help you determine why your connections to a given server might be poor, and can often help you figure out where exactly the problem is. It also shows you how systems are connected to each other, letting you see how your ISP connects to the Internet as well as how the target system is connected.
This quote was taken from here.
I really wanted to see how all this works, so i decided to continue on with the activities. Firstly i used the free tools to traceroute to curtin.edu.au. I was a bit thrown by these sites to begin with - i used the first link first (http://centralops.net/co/) but found that i didn't really know what i was doing. I had a bit more of a look around the internet at various traceroute apps - then reread the instructions for the activity. Opening the second provided link (http://network- tools.com/ ) i decided to go on blind faith and just copy/pasted the curtin server into the box provided and recieved the following results:
134.7.179.53 is from Australia(AU) in region Oceana
TraceRoute to 134.7.179.53 [curtin.edu.au]
| Hop | (ms) | (ms) | (ms) | IP Address | Host name |
| 1 | 0 | 0 | 1 | 66.98.244.1 | gphou-66-98-244-1.ev1servers.net |
| 2 | 0 | 0 | 0 | 66.98.241.13 | gphou-66-98-241-13.ev1servers.net |
| 3 | 0 | 0 | 0 | 66.98.240.5 | gphou-66-98-240-5.ev1servers.net |
| 4 | 1 | 1 | 1 | 129.250.10.189 | ge-1-14.r04.hstntx01.us.bb.gin.ntt.net |
| 5 | 1 | 1 | 1 | 129.250.2.230 | xe-0-1-0.r21.hstntx01.us.bb.gin.ntt.net |
| 6 | 43 | 43 | 43 | 129.250.3.121 | as-1.r21.lsanca03.us.bb.gin.ntt.net |
| 7 | 43 | 43 | 50 | 129.250.3.159 | p16-1-0-0.r02.lsanca03.us.bb.gin.ntt.net |
| 8 | 203 | 202 | 203 | 198.172.90.102 | p4-4-1-0.r02.lsanca03.us.ce.gin.ntt.net |
| 9 | 197 | 198 | 203 | 202.158.194.157 | so-3-3-1.bb1.b.syd.aarnet.net.au |
| 10 | 209 | 215 | 210 | 202.158.194.33 | so-2-0-0.bb1.a.mel.aarnet.net.au |
| 11 | 223 | 219 | 218 | 202.158.194.17 | so-2-0-0.bb1.a.adl.aarnet.net.au |
| 12 | 251 | 245 | 251 | 202.158.194.5 | so-0-1-0.bb1.a.per.aarnet.net.au |
| 13 | 249 | 251 | 249 | 202.158.198.178 | gigabitethernet0.er1.curtin.cpe.aarnet.net.au |
| 14 | 246 | 249 | 252 | 202.158.198.186 | gw1.er1.curtin.cpe.aarnet.net.au |
| 15 | 251 | 246 | 250 | 134.7.16.46 | - |
| 16 | 251 | 250 | 251 | 134.7.248.65 | te1-1.b309-sr.net.curtin.edu.au |
| 17 | 250 | 251 | 250 | 134.7.179.53 | - |
Trace complete
This means that as shown - there was 17 hops to get to curtin.edu.au and it took approx 250ms to get there!The IP address that i traced to for curtin.edu.au was 134.7.179.53 as shown in the above results.
Will be tackling the further explanation later!
Bye for now! Kellie.
Module 1
Today i started working on Module 1 activities.
Firstly i worked out that my computer did in fact have telnet already installed and after a false start (opened up the telnet window without any server address) i got myself hooked in to the library catalogue menu. This was then emailed to my student email account easily.
I have a feeling that i have used telnet before but can't remember when. I did use many computer and internet features with my first IT degree attempt however so figure it is flashes of this coming back to me.
I then downloaded the trial version of the Ipswitch WS_FTP FTP Client. Being lazy i bipassed the manuals to begin with to see if logic would work it out and i was very quickly the curtin recall server. My only hiccup here was with the login but on second attempt i work out that by typing annoymous into the login and bypassing the password i had access.
I originally looked briefly for some type of file search engine, but before i had looked into the option further i had found the needed file and discovered the missing word.
**spoiler here - highlight to see**
CAPITILIZATION
**end spoiler**
Will be back later to complete the final part of the Module 1 questions that are meant for the log. Just wanted to have everything written down while it was fresh for later reference.
Bel (Kellie)
**Everyone needs a good online pseudonym!**
Firstly i worked out that my computer did in fact have telnet already installed and after a false start (opened up the telnet window without any server address) i got myself hooked in to the library catalogue menu. This was then emailed to my student email account easily.
I have a feeling that i have used telnet before but can't remember when. I did use many computer and internet features with my first IT degree attempt however so figure it is flashes of this coming back to me.
I then downloaded the trial version of the Ipswitch WS_FTP FTP Client. Being lazy i bipassed the manuals to begin with to see if logic would work it out and i was very quickly the curtin recall server. My only hiccup here was with the login but on second attempt i work out that by typing annoymous into the login and bypassing the password i had access.
I originally looked briefly for some type of file search engine, but before i had looked into the option further i had found the needed file and discovered the missing word.
**spoiler here - highlight to see**
CAPITILIZATION
**end spoiler**
Will be back later to complete the final part of the Module 1 questions that are meant for the log. Just wanted to have everything written down while it was fresh for later reference.
Bel (Kellie)
**Everyone needs a good online pseudonym!**
Subscribe to:
Posts (Atom)