Step 1: Understand the Problem

First determine exactly what "slow" means.

• Are all users affected?
• Is only one computer affected?
• Is the problem limited to one application?
• Does the problem occur all the time?
• Does it happen only during certain hours?
• Is Wi-Fi affected but Ethernet working normally?

These questions help narrow down the possible causes.

Step 2: Check the Physical Connection

Start with the simplest possibilities.

• Check Ethernet cables.
• Check switch port status.
• Check wireless signal quality.
• Check link speed and duplex.
• Check for damaged connectors.
• Check whether network devices are powered correctly.

Step 3: Use Ping

The ping command is one of the most basic connectivity troubleshooting tools.

```

Windows:

C:> ping 192.168.1.1

Linux:

$ ping 192.168.1.1 

Test progressively farther destinations.

```

PC
|
+--> Default Gateway
|
+--> ISP
|
+--> Internet Destination 

This can help determine whether the issue is local, at the gateway, or farther along the network path.

Step 4: Check Latency and Packet Loss

Look at the ping responses for unusually high round-trip times and packet loss.

```

Reply from 192.168.1.1:
time=2ms

Reply from 192.168.1.1:
time=3ms

Reply from 192.168.1.1:
time=2ms 

Consistently high or highly variable latency, or packet loss, indicates that further investigation is needed.

Step 5: Use Traceroute

traceroute on Linux/macOS and tracert on Windows can show the network path toward a destination.

```

Windows:

C:> tracert example.com

Linux:

$ traceroute example.com 

It can help identify where delay or connectivity problems may begin, although individual hops may deprioritize or filter diagnostic probes, so a slow-looking hop does not automatically mean that hop is the actual problem.

Step 6: Check DNS

Sometimes the network itself is working correctly but DNS resolution is slow or failing.

Use nslookup on Windows or Linux.

```

C:> nslookup example.com 

If IP connectivity works but domain-name resolution is failing, DNS should be investigated.

Step 7: Check Bandwidth Usage

A network can feel slow because available bandwidth is being heavily consumed.

```

Internet Link
100 Mbps
|
+---- Video Streaming
+---- Cloud Backup
+---- File Downloads
+---- Video Meetings
+---- Web Traffic
|
Congestion 

Check whether the WAN or LAN interface is operating close to its available capacity.

Step 8: Check Interface Errors

Network interfaces can provide valuable information about the health of a link.

On Cisco devices, useful commands include:

```

Switch# show interfaces
Switch# show interfaces counters errors 

Look for indicators such as input errors, CRC errors, drops, overruns, or other abnormal counters.

Step 9: Check Network Device CPU and Memory

An overloaded router, switch, firewall, wireless controller, or other network device can contribute to performance problems.

```

Router# show processes cpu
Router# show memory 

Available commands vary by Cisco platform and software version.

Step 10: Check Logs

Logs can reveal events that are not obvious from a simple ping test.

```

Router# show logging 

Look for interface changes, authentication problems, link failures, configuration events, and other relevant messages.

Structured Troubleshooting Flow

          Slow Network
               |
               v
      Is the problem isolated?
         /             \
       YES              NO
        |                |
   Check device       Check network
        |                |
        v                v
   IP / DNS          Ping gateway
        |                |
        v                v
   Test connection   Ping external host
                         |
                         v
                   Check traceroute
                         |
                         v
                   Check bandwidth
                         |
                         v
                   Check interfaces
                         |
                         v
                      Check logs
    

Example: Office Network Is Slow

Imagine employees report that websites are very slow every day between 9:00 AM and 11:00 AM.

A network engineer might discover:

1. Local gateway latency is normal.
2. Internet connectivity works.
3. DNS responds normally.
4. WAN utilization reaches near capacity during peak hours.
5. Large cloud backups consume much of the available bandwidth.

The root cause is therefore more likely to be congestion than a faulty cable or DNS failure.

Common Troubleshooting Mistakes

• Changing configurations without collecting evidence.
• Assuming the ISP is always responsible.
• Testing only one destination.
• Ignoring DNS problems.
• Ignoring interface errors.
• Looking only at bandwidth and ignoring latency or packet loss.
• Failing to compare the problem with a known-good device.

Quick Quiz

1. What command can test basic IP connectivity?
2. What does tracert/traceroute help identify?
3. Which command can be used to test DNS resolution?
4. Why should interface errors be checked?
5. Why should network logs be reviewed?

Key Takeaways

• Start troubleshooting by clearly defining the problem.
• Check physical connectivity first.
• Use ping to test reachability and delay.
• Use traceroute/tracert to examine the network path.
• Use nslookup to investigate DNS.
• Check bandwidth utilization during congestion.
• Check interface errors on network devices.
• Review CPU, memory, and device logs when appropriate.
• Always collect evidence before changing configurations.