Ping and Tracert Presentation

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I am going to do a presentation on the above to my fellow IT techs within my team, and have to make it into a "dummies guide", as i dont really want <plonker user> to feel left out aswell, as this help those who are uncertain about what the commands are.

I will basically break down what

• Ping is
• Tracert is
• What replies are, when pinging
• What Hops are within Tracert
• WINS - hows IP address and Domain names work

The audience are 1st Line, i know a few would know what i am referring to, and we have some new members within the team, and hope that they know what i will be referring to...

Can anyone think if anything else that i may add, without going to complex relating to ping and tracert.

It will be done over a powerpoint presentation (notes) and myself explaining what each item is, and the presentation should last around 30-45 mins (without the q&a session at the end).

I could talk slowly, but i get rather nervous when talking to a group, and when i do get nervous, i tend to talk really fast...

Any tips?

 

Thats the bugger! I knew WINS were one of them, but couldn't remember ghe other one Cheers Sparky! I'll be changing that to DNS...

Any other tips anyone could help me with?
Anyone? SHould be uploaded the ppt next week for a review of what you chaps think....

 

Shouldn't you really be doubling the amount of time the presentation takes with <plonker user> in attendance?

 

You could talk about TCP/IP in general as that is the subject at hand so it seems and maybe mention the loopback address 127.0.0.1

See http://en.wikipedia.org/wiki/Loopback

 

Considering you've got at least one <plonker>, you might have to explain what the heck an IP address is.

 

OSI model? Might be usefull for troubleshooting for the techs to have a basic understanding of the OSI model.

How about self help options such as Technet?

 

As Bluerinse mentioned, it may be better to give a grounding in TCP/IP troubleshooting altogether. This KB Article from Microsoft outline the steps for troubleshooting TCP/IP which includes using Ping and Tracert (I think they have it down as PathPing which is redundant).

It would be more beneficial if they knew the whole process of troubleshooting TCP/IP and the associated problems rather than just knowing how to use a couple of the tools.

HTH

 

For the XP exam one also needs to know something about IP, but there is not that much info in the MOC. For this reason I give a IP-break-out lasting 2.5 to 3 hours.
I start with a sketch of the complete IP list (just a square). I divide this in two equal parts. On a other portion of the board I write down the first 16 binairy numbers (0000 to 1111). I divide those to in two equal parts (0000 to 0111 and 1000 to 1111).
They will see easy that the only difference between the two parts is the first bit. So I return to the sketch and point out that the first bit pins down the first half in a simple but efficient way. I then divide the remainder again in two equal parts and point out B-class. So on with C-class, D and E-class.
I also keep reffering to the telephone network as a model (area code = network ID).
In this way I slowly build up a decent base for the rest.
In these few hours I give them a tour throu IP-land.
Most students find it an eye opener.

 

Might be an idea to explain what the different type of command you can use in the Command prompt and why use them such as

What if you get a limited on no connectivity displayed on the system tray of the network icons??

Using the commands:

ipconfig/all

ipconfig/release
ipconfig/renew

Ping

Also are you using a pinger and cat5e cabel to demonstrate how to test a port or going through a PC?

Maybe you should also explain about dummy IP address such as 169.??

 

I wouldn't call 169 addresses "dummy" addresses as they are perfectly valid just a private address when no other address can be obtained.

 

Yup, APIPA is the magic acronym but it's 169.254.x.x

 

will be looking in ipconfig command briefly

Will go into apipa breifly, and talk very briefly about DHCP

thats what im scared of!

Cheers for your suggestions so far...

 

basically the page with the picture is what i will show, and i will explain what each item is, the next page with the break-down should reiliterate what i just was on about... obviously, with more words...

What you guys reckon?

 

Looks good to me

You might want to explain why google.com is returning what appears to be a private IP 10.10.144.22

Source http://www.faqs.org/rfcs/rfc1918.html

 

i changed the ip address myself, and also google.com...

 

looks good Cheek, basic information presented in a user friendly way.

 

looks fine to me.