FINAL LAB

Final Lab- Network troubleshooting

In class we were tasked setting up three networks with the ultimate goal of having the network broken, and getting them back to working condition by troubleshooting the problems created by the instructor.

the quick reference of the networks used in this lab were one half of the hosts are on the 172.16.0.0 network and the other half are on 172.18.0.0 network

First, like previous labs we went through the process of setting up the hosts, by going through the network adapter properties once again and changing the default IP addresses to match the networks we were on, for instance my IP address since i was on the network 172.16.0.0 was 172.16.0.3 and with everything set up for the host we went on to setting up the router.

the network adapter settings which are used via changing the properties to change the default IP address so the computers(hosts) can connect to the network.

Again, like previous labs we set up the router using hyperterminal to talk to the Cisco router we were using and by creating a new connection and giving it a name [172.16.0.1] then connection using COM 3 and setting the bits per second to 9600, additionally setting the flow control to none and hitting the enter key then using the following commands:

  • N – No, we will be manually configuring the router
  • EN
  • Config T
  • INT e0
  • IP add (add the IP address and subnet mask)
  • no shutdown
  • exit
  • router rip (enabling routing protocol)
  • network 172.16.0.0 (CLASS B) the network our hosts are connected to
  • network 172.17.0.0 (CLASS B) the inbetween network
  • exit
  • exit
  • copy run start (saves config)
  • show run(show running config)

Once both sides and the team as a whole has setup both networks a ping is sent from one network to the other and results in a successful reply. Now that both sides are setup and running the team and I leave the class for a couple of minutes while the instructor tries to ding it up and make the network nonfunctional, tasking the team and i with diagnosing the problems and fixing them in a logical manner.

a picture of the host pc i used to troubleshoot the connection between the 172.16.0.0 network and the 172.18.0.0 network by using CMD to ping a host on the other side of the network.

After returning to the class, the instructor informed us that we were left with four hiccups to fix and so off we went.

First we started by looking at all the physical cables the connected all the machines to each other and discovered one of the switches had been disconnected from it power source, after plugging that in we went about finding the next problem.

Secondly we noticed that an interface was shutdown on the 17.18.0.0 networks router as well as the Shutdown being turned on instead of off by going into the config t and typing in e0 as the port and hitting enter the problem was resolved.

the team we had working on setting up the network and fixing it. i unfortunately could not be in the picture as i am the one taking it. during this picture we were diagnosing the problems with the router on the 172.18.0.0 network side

additionally we noticed that two of the network cables on the 17.16.0.0 side had been switched and we promptly corrected that leaving only one mistake left to fix.

A member of the team noticed that there default ip had been manipulated in his network properties on his host computer and after that was fixed a ping was sent from his pc to a host on the other side and yeilded a reply thus fixing completely what had caused our networks not to talk between eachother. and with this all was done, it was a great time.

I bid farewell to my team and farewell to the lab, it was a great time working with my team and other class mates building and destroying networks, so if anyone from my lab happens to see this thank you for making it a wonderful engaging experience and a special thanks to our instructor Dr. Bill Genereux, thank you for shepherding the knowledge of the fundamentals of what a network is and what makes it work.