• Home
  • Southern New Hampshire University
  • Network Defense CYB-310-T5690
  • Network Troubleshooting

Network Troubleshooting

Walter Lawrence CYB 310 -- Network Defense Southern New Hampshire University Professor Ostering October 6, 2022 Network Evaluation Report To analyze networks properly we need to figure out what devices are not working or functioning. There are multiple ways to troubleshoot the issues. The most basic troubleshooting we can do is to look at the physical connection. Most of the times if issues pertain to connection issues a wire or cable might be loose. With loose connections nothing will work. This is the easiest first step to start with as it could ultimately fi the issue right away. If cables are not compatible with a certain device that could also pose an issue as well. For example, if the cable doesn't fit right and the tech forces it to fit the connection won't connect right. Other issues could stem from the cable being too small which could cause it to be loose or fall out constantly dropping the connection. Another object to troubleshoot would be the firewall and network configurations. If the network is connected and the firewall is connected but both are not configured right, they also could be the factors in why the network or workstation is not connecting right. For the first challenge Network_1 segment needs to have all access to the Network_3 segment. With looking at the sample network map that was provided to us, there could be multiple reasons behind the cause of network_1 segment's connection to fail when trying to access network_3 segment. I was able to trace the connection between network_1 and network_3 and saw that some of the physical connections need to be looked at. The connection does not seem to be working properly at each connection port host in network_1. I can see that the connection to the switch on network_1 is working correctly, which means the ethernet cable that is used is fine. I will be examining the ethernet connections. Next, I then looked at the connection between network 1 switch, and the main switch and that connection seems to be working properly as well. Continuing my triage path, I then moved onto looking at the connection between the main switch and network 3 router which appears there is an issue at the network_3 router. It appears that the physical connection between the router and network switch seems to be broken which is stopping the data flow. I noticed that the hosts on network_3 seem to have the exact same issue as the hosts on network_1. I will be checking the physical connections of each host. I kept following the data's path from host connections on network_1 to the host connections on network_3 and I can determine that the connection disruption due to physical broken connection is the cause of the data loss between the router and switch on network 3 and is the cause of why network 1 can't communicate with network 3 segment. To get this issue resolved and the connection back up and running, the ethernet cable