One way we can do this is to test whether each device can reach any other device on the LAN (apart from each other). Now we need to isolate whether the problem is with both devices or just one of them. Note: It is assumed that you have studied the lab setup and that you are familiar with the different IP addresses. In this type of scenario, you usually have access to the computer that is experiencing issues and one of the easiest things to kick your troubleshooting off with is Ping. It is always best not to assume that the user is really experiencing the issue and to see if you can replicate it yourself. When did this problem start? What changed on the network that could have caused the problem? In a real-world scenario, you will want to ask questions such as:

The most basic troubleshooting scenario you will get as a network engineer is that a computer cannot connect to the network e.g., the user is unable to access some company resource or the Internet.

On the other hand, if you are troubleshooting why two routers are not forming EIGRP neighbor adjacency, then you will use another method – one that is specific to EIGRP like checking K-values, and so on. For example, if you are dealing with Layer 3 (IP) forwarding, you probably want to start with understanding the traffic flow: How is traffic supposed to flow from device A to device B? When you’ve got this, then you want to start analyzing why traffic is not flowing that way for those devices and continue drilling down until you find the issue. That being said, there is no one-size-fits-all method for troubleshooting and the method you use will differ from scenario to scenario. As a result, we fumble about with different tools and methods in a brute-force manner instead of taking a step back to understand what is going on. We sometimes make the mistake of jumping into troubleshooting without first trying to understand the problem. Troubleshooting is an art that requires great analytical skills and an understanding of how things work. Trblsht_netwk_conn_final.pkt: This Packet Tracer file contains the lab with the issues resolved.

Packet tracer labs answers