Network Troubleshooting Guide: Fix Common Internet Connection Problems

Nothing disrupts your day quite like internet connectivity problems. Whether you're staring at a "No Internet" message, struggling with painfully slow speeds, or dealing with a connection that keeps dropping, this guide will walk you through a systematic troubleshooting process to identify and fix the problem.

We'll start with the simplest solutions and work our way to more advanced diagnostics. Most internet problems fall into a handful of common categories, and by following this methodical approach, you'll resolve the vast majority of issues without needing to call your ISP.

The 30-Second Quick Fixes

Before diving into detailed diagnostics, try these rapid solutions that fix the majority of internet problems:

1. Toggle WiFi off and on on your device (or unplug/replug your Ethernet cable)
2. Restart your router and modem: Unplug both from power, wait 30 seconds, plug in the modem first, wait 60 seconds, then plug in the router
3. Try a different device: If your phone works on WiFi but your laptop doesn't, the problem is device-specific, not network-wide
4. Try a different browser: If one browser can't load pages, try another to rule out browser-specific issues

If these don't help, proceed with the systematic process below.

Step 1: Determine the Scope of the Problem

The first question to answer is: what exactly isn't working? The answer shapes your entire troubleshooting path.

Is it a Total Outage or Partial?

Total outage (nothing works on any device):

• Check your router's indicator lights. If the internet/WAN light is off or red, the problem is between your router and your ISP.
• Check your ISP's status page (use your phone's cellular data) for reported outages in your area.
• Check if other homes in your area are affected (ask neighbors or check social media).

Partial (some things work, others don't):

• If you can reach some websites but not others, it's likely a DNS issue or the specific sites are down.
• If WiFi works but is very slow, it could be congestion, interference, or a bandwidth-related issue.
• If some devices work but others don't, it's a device-level configuration issue.

Can You Reach Your Router?

Open a browser and navigate to your router's admin page (commonly 192.168.0.1 or 192.168.1.1). If you can reach it:

• Your local network is functioning
• The problem is between your router and the internet, or with DNS

If you can't reach the router:

• Your device may not be connected to WiFi, or the Ethernet connection may be faulty
• Your router may need to be restarted or may have failed
• There could be an IP address conflict on your local network

Step 2: Check Physical Connections

It sounds basic, but physical connection issues cause a surprising percentage of network problems.

For Wired Connections:

• Ensure the Ethernet cable is firmly seated at both ends (listen for the click)
• Try a different Ethernet cable (cables can develop internal breaks, especially at the connector)
• Try a different port on your router
• Check for LED activity lights on the router's Ethernet port

For WiFi:

• Ensure WiFi is enabled on your device (check the hardware switch if your laptop has one)
• Check if you're connected to the correct network (not a neighbor's)
• Move closer to the router to rule out signal strength issues
• Look at the WiFi icon for signal strength bars

For the Router and Modem:

• Check all cable connections: power, Ethernet WAN (from modem), and coax/fiber (to modem)
• Verify indicator lights are showing normal status (consult your router's manual for what each light means)
• If you have a separate modem and router, check the cable between them

Step 3: Diagnose DNS Issues

DNS problems are one of the most common causes of "internet isn't working" when the connection itself is actually fine. If you can ping IP addresses (like 8.8.8.8) but can't load websites by name, DNS is the culprit.

Test DNS Resolution

On Windows:

ping 8.8.8.8
nslookup google.com

On macOS / Linux:

ping -c 4 8.8.8.8
nslookup google.com

If ping 8.8.8.8 succeeds but nslookup google.com fails, you have a DNS problem.

Fix DNS Issues

Solution 1: Flush your DNS cache

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder

Linux:

sudo systemd-resolve --flush-caches

Solution 2: Switch to a public DNS server

If your ISP's DNS servers are having problems, switching to a public DNS provider often fixes the issue immediately.

Recommended DNS servers:

• Cloudflare: 1.1.1.1 and 1.0.0.1
• Google: 8.8.8.8 and 8.8.4.4
• Quad9: 9.9.9.9 and 149.112.112.112

You can change DNS settings on your device or on your router (which affects all devices on your network).

On Windows:

1. Open Settings > Network & Internet > Advanced network settings > your adapter > Edit
2. Set DNS to manual and enter the preferred and alternate DNS addresses

On macOS:

1. Open System Settings > Network > your connection > Details > DNS
2. Add the DNS server addresses

Step 4: Check for IP Address Issues

IP address conflicts or DHCP failures can prevent your device from connecting properly.

Verify Your IP Configuration

Windows:

ipconfig /all

macOS:

ifconfig

Linux:

ip addr show

What to look for:

• Your device should have an IP in your router's range (typically 192.168.0.x or 192.168.1.x)
• If you see an address starting with 169.254.x.x (APIPA address), your device failed to get an IP from DHCP. The router's DHCP server may be malfunctioning, or you may have a connection issue to the router.
• Check that the default gateway matches your router's IP address
• Check that DNS servers are configured (not blank)

Release and Renew Your IP

Windows:

ipconfig /release
ipconfig /renew

macOS/Linux:

sudo dhclient -r
sudo dhclient

This forces your device to request a fresh IP address from the router.

Step 5: Diagnose Slow Internet

If you're connected but speeds are poor, the problem could be anywhere from your device to the destination server.

Run a Speed Test

Use our Speed Test tool to measure your actual download and upload speeds. Compare the results with what you're paying for from your ISP.

Interpreting results:

• Getting expected speeds? The problem might be with a specific website or service, not your connection.
• Speeds are 50%+ lower than expected? There's likely a problem with your connection.
• Upload fine but download slow (or vice versa)? This can indicate a specific channel problem with your ISP.

WiFi-Specific Speed Issues

WiFi is often the bottleneck, not your internet connection itself. Test by connecting directly to the router with an Ethernet cable and running the speed test again.

If wired speed is fine but WiFi is slow:

• Channel congestion: In apartments, dozens of WiFi networks compete on the same channels. Use a WiFi analyzer app to find the least congested channel and switch your router to it.
• Distance and obstacles: WiFi signals weaken significantly through walls, floors, and large appliances. Move closer to the router or consider a mesh WiFi system.
• Band selection: Use the 5GHz band for speed (shorter range) and 2.4GHz for distance (slower speeds). WiFi 6E and WiFi 7 also offer the 6GHz band.
• Interference: Microwave ovens, Bluetooth devices, baby monitors, and cordless phones can interfere with 2.4GHz WiFi.
• Too many devices: Each connected device shares the available bandwidth. Smart home devices, background updates, and cloud sync can consume bandwidth silently.

Check for Background Bandwidth Usage

Before assuming your internet is slow, check what's consuming bandwidth:

• Cloud backup services (iCloud, Google Drive, Dropbox) syncing large files
• Automatic OS or game updates downloading
• Other family members streaming or downloading
• Smart home cameras uploading video continuously
• Malware using your connection for malicious purposes (if nothing else explains the usage)

Step 6: Trace the Network Path

If your connection is working but specific websites or services are slow or unreachable, trace the route to pinpoint where the problem occurs.

Run a Traceroute

Use our Traceroute tool or the built-in command:

Windows:

tracert problematic-website.com

macOS / Linux:

traceroute problematic-website.com

What to look for:

• A sudden increase in latency at a specific hop indicates where the bottleneck is
• Timeouts (***) at every hop from a certain point onward suggest a routing failure
• Routing loops (same routers appearing repeatedly) indicate a misconfiguration

For a detailed guide on interpreting results, see our article on How to Read Traceroute Results.

Step 7: Check Your Router's Health

If problems are recurring, your router itself may be the issue.

Signs Your Router Is Struggling:

• Frequent disconnections or the need to reboot regularly
• Slow speeds that recover after a restart
• Not all devices can connect even when below the device limit
• The router feels physically hot

Router Health Checks:

1. Check connected device count: Log into your router's admin panel and check how many devices are connected. Consumer routers can struggle with 20+ simultaneous devices.
2. Check for firmware updates: Outdated firmware can cause stability and security issues.
3. Check CPU and memory usage: Some router admin panels show system resource usage. If CPU is consistently above 80%, the router is overloaded.
4. Check channel congestion: Switch to a less congested WiFi channel.
5. Factory reset as a last resort: If the router has been running for years without a reset, accumulated configuration issues can cause problems. Back up your settings first, then reset and reconfigure.

When to Replace Your Router

• It doesn't support WPA3 or WiFi 6 (802.11ax)
• It's more than 5 years old
• It can't handle the number of devices in your home
• Frequent crashes or freezes that firmware updates don't fix
• Your internet plan is faster than what the router can handle

Step 8: ISP-Level Troubleshooting

If you've ruled out everything on your end and the problem persists, it's time to investigate your ISP's side.

Gather Evidence Before Calling

Your ISP's support team will be much more helpful if you provide specific data:

1. Your public IP address from My IP Address
2. Speed test results from Speed Test showing speeds below your plan
3. Traceroute output showing where packets are being lost or delayed
4. The time and duration of the problem (ISPs can cross-reference with their network monitoring)
5. What you've already tried (so they don't waste time walking you through basic steps)

Common ISP Issues

• Node congestion: Cable internet shares bandwidth among neighbors. Peak hours (7-11 PM) may show significant slowdowns.
• Line issues: Physical damage to cables between your home and the ISP can cause intermittent problems. This may require a technician visit.
• DNS server problems: ISP-provided DNS servers sometimes fail. Switch to public DNS as described above.
• Routing problems: ISP routing table issues can affect connectivity to specific destinations. A traceroute showing the problem in the ISP's network is the best evidence.
• Outages: Planned or unplanned outages affecting your area. Check your ISP's status page.

Step 9: Advanced Diagnostics

For persistent or complex problems, these advanced tools can help:

Check Your Network Externally

• Use Port Scanner to verify ports are accessible from outside
• Use IP Lookup to verify your IP's metadata
• Use HTTP Headers to check if a specific website is responding correctly

Continuous Monitoring

If problems are intermittent, set up continuous monitoring:

# Continuous ping with timestamps (macOS/Linux)
ping google.com | while read line; do echo "$(date): $line"; done

# Windows equivalent
ping -t google.com

Run this for several hours or overnight and look for patterns in latency spikes or packet loss.

Check for Packet Loss

# macOS/Linux
ping -c 100 8.8.8.8

# Windows
ping -n 100 8.8.8.8

Any packet loss above 1-2% indicates a real problem. 0% packet loss is normal for a healthy connection.

Troubleshooting Decision Tree

Here's a quick decision tree to guide your troubleshooting:

1. Can you reach your router's admin page?

- No: Check WiFi connection, cables, restart router

- Yes: Continue to step 2

1. Can you ping 8.8.8.8?

- No: Problem is between your router and the internet (ISP issue or modem failure)

- Yes: Continue to step 3

1. Can you resolve DNS (nslookup google.com)?

- No: DNS issue. Change DNS servers to 1.1.1.1/8.8.8.8

- Yes: Continue to step 4

1. Is the problem with all sites or specific ones?

- Specific sites: Those sites may be down, or there's a routing issue (run traceroute)

- All sites: Check for proxy settings, firewall software, or VPN interference

1. Is the problem speed-related?

- Yes: Run speed test, check WiFi vs wired, check for bandwidth-consuming devices

- No: Review error messages for specific clues

Key Takeaways

• Always start with the simplest fixes: toggle WiFi, restart the router, try another device
• Determine the scope first: total outage, specific sites, specific devices, or slow speeds
• DNS problems are extremely common and easily fixed by switching to public DNS servers (1.1.1.1)
• Use Speed Test to verify your connection speed and Traceroute to locate bottlenecks
• WiFi issues are often the real culprit, not your internet connection. Test with Ethernet.
• Gather specific evidence (speed tests, traceroutes, timestamps) before contacting your ISP
• If your router is old, overloaded, or missing modern security features, it may be time for an upgrade

Related Articles:

• How to Read Traceroute Results: Finding and Fixing Network Problems
• How to Check If a Port Is Open: Complete Troubleshooting Guide
• WiFi Security in 2026: WPA3 and How to Secure Your Wireless Network