Network Troubleshooting Guide: Fix Common Connection Issues

The Troubleshooting Methodology

Effective network troubleshooting follows a systematic approach: work from the physical layer upward, and eliminate the simplest causes before investigating complex ones. The OSI model provides a useful mental framework — check physical connectivity first, then data link, then IP, then application layer.

Before diving into diagnostics, answer these triage questions:

• Is the problem affecting all devices or just one? (Rules out ISP or router issues if device-specific)
• Is the problem affecting all sites/services or specific ones? (DNS, routing, or destination-specific if selective)
• When did it start? Were any changes made (updates, new hardware, ISP work in the area)?
• Is it constant or intermittent?

Always start by checking your public IP address. If you don't have an IP or it shows your ISP's gateway, you're not connected to the internet at all. If you have an IP but can't browse, the problem is likely DNS or routing.

No Internet Connection: Step-by-Step Fix

Work through this checklist in order:

1. Check physical connections — are all cables seated firmly? Is the router's WAN port receiving signal (usually a solid or blinking light)? Is the modem powered on and synchronized (usually shown by a solid "Online" or "Internet" light)?
2. Reboot in correct order — power off modem, router, and computer. Wait 30 seconds. Power on modem first and wait for it to fully synchronize (1–3 minutes). Then power on router and wait. Then computer.
3. Release and renew IP address — on Windows: ipconfig /release then ipconfig /renew. On Mac/Linux: reconnect the network interface or use sudo dhclient -r && sudo dhclient.
4. Ping your default gateway — find it with ipconfig (Windows) or ip route (Linux). If you can ping the gateway but not 8.8.8.8, the problem is between your router and the internet.
5. Ping by IP vs hostname — try ping 8.8.8.8. If that works but ping google.com fails, your DNS is broken, not your internet connection. Change DNS to 1.1.1.1 or 8.8.8.8 in your network settings.
6. Call your ISP — check their status page or app for outages in your area first to avoid a hold queue.

Slow Internet: Diagnosing Speed Problems

When internet feels slow, measurement comes before guessing. Run a speed test and compare against your plan's advertised speeds. Then determine where the slowness originates:

If speed test shows full speed but browsing feels slow:

• The problem may be latency rather than bandwidth — run a ping test
• Browser cache corruption — clear cache and cookies
• Specific websites may be slow at their end — test multiple sites
• DNS may be slow — switch to 1.1.1.1 or 8.8.8.8

If speed test shows below plan speed:

• Test on multiple devices. If only one device is slow, the issue is that device's hardware/software
• Test over Ethernet. If WiFi is slow but wired is fast, the problem is your WiFi environment
• Check for background processes consuming bandwidth (Windows Update, cloud sync, game downloads)
• Check for ISP throttling — some ISPs throttle streaming. A VPN can test whether throttling is protocol-specific
• Test at different times. Consistent slow evening speeds indicate ISP congestion

Dropping Connections and Intermittent Outages

Intermittent drops are among the hardest problems to diagnose because they're often absent when you're actively testing. Strategy: set up continuous monitoring so you capture the event when it occurs.

# Windows: log ping results continuously
ping -t 8.8.8.8 >> ping_log.txt

# Linux/Mac: log with timestamps
while true; do echo "$(date): $(ping -c 1 -W 2 8.8.8.8 | tail -1)"; sleep 10; done >> ping_log.txt

Run this continuously and check the log when a drop occurs. Look for patterns:

• Loss during evenings only — ISP congestion
• Loss during heavy rain or cold weather — water intrusion in outdoor cable splice or corroded connectors
• Drops every few hours at regular intervals — DHCP lease renewal issues, or router instability
• Drops correlated with microwave or cordless phone use — 2.4 GHz WiFi interference
• Random drops only on WiFi — check router logs for deauthentication events; driver issues or power management settings may disconnect WiFi periodically

Check your modem's event log for T3 (ranging request timeout) and T4 errors — these indicate upstream signal problems that always precede drops on cable internet.

DNS Problems and How to Fix Them

DNS failures cause a specific symptom: you can ping IP addresses but hostnames don't resolve. Websites show "Server not found" even though the internet connection itself is working. Fix process:

# Test DNS resolution manually
nslookup google.com
nslookup google.com 1.1.1.1   # test against a specific DNS server
nslookup google.com 8.8.8.8   # test against Google DNS

If nslookup works with 1.1.1.1 but not with your default DNS, your ISP's DNS server is failing. Fix: manually set your DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) in your network adapter settings.

Flush your local DNS cache to clear stale or corrupt entries:

# Windows
ipconfig /flushdns

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux (systemd)
sudo systemctl restart systemd-resolved

Run our DNS leak test to verify which DNS servers your system is actually using — especially important if you use a VPN and want to ensure DNS queries aren't leaking outside the VPN tunnel.

Advanced Tools and Diagnostics Reference

For complex issues, build a toolkit of diagnostic commands:

• ipconfig /all (Windows) or ip addr && ip route (Linux) — show full IP configuration including gateway and DNS
• netstat -rn — display routing table; useful for diagnosing split-tunnel VPN issues
• arp -a — list ARP table; useful for diagnosing IP conflicts on local network
• traceroute — map path and identify latency hop-by-hop
• nmap -sV --open localhost — check which services and ports are open on your own machine
• Port Checker — test whether specific ports are open from the internet
• HTTP Headers tool — inspect what headers a server returns, useful for diagnosing caching and redirect issues
• WHOIS lookup — identify IP ownership and ASN for diagnostic hop attribution

For documenting issues to share with your ISP, always include: your public IP (from our IP checker), traceroute output, MTR report, and timestamps of when the problem occurred.

Frequently Asked Questions