Troubleshooting Network Problems


Troubleshooting your network includes a methodology that starts with cabling and works through the OSI model to the application layer. Network devices have a network cable that ends with a wired adapter. Cables are the source of many network problems.

The key to troubleshooting is to identify what has changed. Sometimes the hardware is not working or some changes have been made such as new software, configured equipment, or additional staff stressing the network. It could be a specific problem or several problems. Start with the client adapter, identify the specific symptoms and go from there.

Here are a series of questions that can be used as a guide during the troubleshooting process:

1. Can you ping the IP address of the switch?

2. Can you ping the router?

3. Can you ping the DHCP server?

4. Does the desktop client get an IP address?

5. Is a WAN circuit available?

6. Is new software installed on the client or server?

7. Do all customers face the problem?

8. Is it random or a pattern?

9. Is the problem server specific or application specific?

10. Is the DNS server IP address setting correct?

11. Is there a firewall that filters traffic?

12. Run the trace and check the routing behavior?


1) Windows Control Panel displays network adapter settings, firewall configuration, etc.

2) Ping and traceroute will verify that the network routing is working.

3) Examine the ARP table on the desktop, switch, and router to confirm the presence of the MAC address of the device.

4) Network packet sniffers check packet information such as protocols, filtered programs, or errors in applications.

5) Verify change management activities and determine if and how any equipment has been changed.

6) Showing the interfaces on the router will reveal any interface errors that indicate a problem with the cable or hardware.

7) Examine the router interface usage patterns.

Working from the cable level and determining whether the problem affects a single user, department, building, or city-wide is a good place to start. A citywide problem sometimes indicates a data center outage. Building sometimes refers to a circuit, router, or primary switch. The section can indicate a problem with network switches or fiber cabling. A single user issue can be a myriad of issues from a damaged cable to network permissions. Since companies in some cases have hundreds of applications, network switches, and routers, the problem becomes more complex when it is a cross-departmental one. Not all employees have the same network permissions and use a variety of applications across departments, cities, and countries 188Bet.

Identifying who is affected by the problem can be a major factor in resolving the problem. ping is a popular tool because it checks that the network layer is all working. In this case, you will focus on app issues albeit not always. Traceroute checks how packets travel between the source and destination.

This post was created with our nice and easy submission form. Create your post!


What do you think?

32 Points

Written by Jessica Jack

Story MakerStory MakerYears Of Membership


Leave a Reply

Your email address will not be published. Required fields are marked *

What is The Best Way to Get Backlinks

Top React Native Boilerplates for 2021!