|
APCO 2P011 Lab 10
|
|
Objective
In this lab you will focus on learning the primary component
surrounding local area network. A portion of the lab will focus on
learning to trouble shoot the hardware and software components of a
LAN.
Introduction & Startup (5 min)
Set up your Dell machines and boot into windows.
Exercise 1 (30 min)
Complete Exercise 9.1
Exercise 2 (40 Min)
Complete Exercise 10.1
Exercise 3 (20 Min)
In this lab you will be required to create your own patch cable Exercise 10.3. Creating a patch cable is
not difficult, once 1 is created the process becomes more smooth.
Your instructor will demonstrate how to assemble a RJ45 connector.
After the demonstration each person of the team will be required to
create 1 cable.
After the demonstration, create a patch cable with the materials
provided. Once complete test the cable using your multi-meter.
Your instructor has a neat gadget called a cable tester, borrow it,
and test your cable.
Plug your cable into your dell machine and the network jack on you
work table.
Exercise 4 (30 min)
Install WinIPConfig software. It can be used in conjunction with or
a substitute to some of the tools listed in the book. It is a
graphical version of the ipconfig utility mentioned in the lab.
Find the values for the following:
MAC:
IP:
GateWay:
DNS:
DHCP:
Determining who owns that IP address. A utility which is part of Win
7 is nslookup (name server lookup). You can use the command line
version of Win 7 or an online version http://www.zoneedit.com/lookup.html.
Using either source determine the name of 139.57.100.6? Like wise
you can reverse the process and extract an IP from the name. Try it.
Exercise 5 (10 min)
Examining your network using netsh. What is netsh? it is the network
shell program which allows an interface to to your networking
configuration on the machine. A common problem with many windows
machines is the loss of, or a corrupt TCP/IP stack. Using a netsh
command, the stack can be restored,often saving a reinstall of the
OS.
Open a command window, Start -> run -> cmd
type
the following: netsh int ip reset resetlog.txt
This tells netsh to look at the interface
ip which is the tcp/ip stack
and reset it. Output of the command is sent to a log file
resetlog.txt. This command can often save hours.
Explore netsh by just typing in netsh. You will get a prompt
netsh>. A ? will list the available commands. For example typing
interface and then ? or help will list all the interfaces which
netsh can communicate with.
See what ipv4 interfaces your machine has. Start netsh by typing
netsh. Type interface, to see what the interface command can
do type a ?, this will list a series of command. The ipv4 command is
one of these, type ipv4. By now you should see the following on your
screen.
netsh interface ipv4>
show addresses then lists all ipv4 configurations you machine
has. Try it.
Exercise 6 (20 min)
Find the ip address of Vaxxine.com, use nslookup.
Use tracert to trace the network response to Vaxxine.com. Did it
work, why not?
Try tracert on a local machine, such as 139.57.100.62
Try ping on Vaxxine.com, then on 139.57.100.62, which one worked and
why?
Is it wise to assign an IP address manually, at Brock or at Home?
Why?