CCN Lab Manual # 1: Networking Basic Commands
CCN Lab Manual # 1: Networking Basic Commands
Objective
Gather information including connection, host name, Layer 2 MAC address and Layer 3 TCP/IP
network address information.
Compare network information to other PCs on the network.
Learn to use the TCP/IP Packet Internet Groper (ping) command from a workstation.
Learn to use the Trace Route (tracert) command from a workstation.
Background
This lab assumes the use of any version of Windows. This is a non-destructive lab and can be done on
any machine without concern of changing the system configuration. Ideally, this lab is performed in a
Computer Lab or other LAN environment that connects to the Internet.
This lab can be done from a single remote connection via a Dial up modem or DSL-type connection.
In the following Lab Manual the lab runs only on Windows NT/2000/XP and up versisons. Extra Steps
should be done on Windows 95/98/ME systems.
The following figure shows the Command screen. Type ipconfig and press the Enter key. The
spelling of ipconfig is critical while case is not. It is short for IP Configuration.
This first screen shows the IP address, subnet mask, and default gateway. The IP address and the default
gateway should be in the same network or subnet, otherwise this host would not be able to
communicate outside the network. In the figure the subnet mask tells us that the first three octets must
be the same to be in the same network.
Note: If this computer is on a LAN, the default gateway might not be seen if it is running behind a Proxy
Server. Record the following information for this computer.
Step 4: Compare the TCP/IP configuration of this computer to others on the LAN
If this computer is on a LAN, compare the information of several machines.
Are there any similarities?____________________________________________________
What is similar about the IP addresses? __________________________________________
What is similar about the default gateways? _______________________________________
The IP addresses should share the same network portion. All machines in the LAN should share the same
default gateway.
Record a couple of the IP Addresses:
________________________________________________________________________
The host name, including the computer name and NetBIOS name should be displayed. Also, the DHCP
server address, if used, and the date the IP lease starts and ends should be displayed. Look over the
information. Entries for the DNS, used in name resolution servers, may also be present.
The previous figure reveals that the router is performing both DHCP and DNS services for this network.
This would likely be a small office or home office (SOHO) or small branch office implementation.
Notice the Physical Address (MAC) and the NIC model (Description).
In the LAN, what similarities about the Physical (MAC) Addresses are seen?
__________________________________________________________________________
While not a requirement, most LAN administrators try to standardize components like NICs.
Therefore, it would not be surprising to find all machines share the first three Hex pairs in the adapter
address. These three pairs identify the manufacturer of the adapter.
Write down the IP addresses of any servers listed:
__________________________________________________________________________
Write down the computer Host Name:
__________________________________________________________________________
Write down the Host Names of a couple other computers:
Look over the results. Notice that the first line of output shows the host name, m450 in the example,
followed by the IP address. This means the computer was able to resolve the host name to an IP
address. Without name resolution, the ping would have failed because TCP/IP only understands valid
IP addresses, not names.
If the ping was successful, it means that connectivity and discovery of IP addresses can be done with
only a hostname. In fact, this is how many early networks communicated. If successful, then ping a
hostname also shows that there is probably a WINS server working on the network.
Note: It would not be uncommon for a Windows 2000 or XP networks to not support this feature.
The first output line shows the Fully Qualified Domain Name (FQDN) followed by the IP address. A
Domain Name Service (DNS) server somewhere in the network was able to resolve the name to an IP
address. DNS servers resolve domain names, not hostnames, to IP addresses.
Fig 2.7 ping failure for Microsoft because some Microsoft routers are configured to ignore ping
Notice that the DNS server was able to resolve the name to an IP address, but there is no response.
Some Microsoft routers are configured to ignore ping requests. This is a frequently implemented
security measure.
ping some other domain names and record the results. For example, ping www.msn.de
tracert is TCP/IP abbreviation for trace route. The preceding figure shows the successful result when
running tracert from Bavaria in Germany. The first output line shows the FQDN followed by the IP
address. Therefore, a DNS server was able to resolve the name to an IP address. Then there are listings
of all routers the tracert requests had to pass through to get to the destination.
tracert uses the same echo requests and replies as the ping command but in a slightly different
way. Observe that tracert actually contacted each router three times. Compare the results to
determine the consistency of the route. Notice in the above example that there were relatively long
delays after router 11 and 13, possibly due to congestion. The main thing is that there seems to be
relatively consistent connectivity.
Each router represents a point where one network connects to another network and the packet was
forwarded through.
Assignment: