Down Speed & Wi-Fi Troubleshooting: Fix Slow Internet, 'Connected But No Internet', and Wi-Fi Not Connecting
Fix slow download speeds, 'connected but no internet', and Wi-Fi not connecting. Step-by-step commands and diagnostics for Windows, Mac, Android, and routers.
- Root cause 1: IP address conflicts, stale DHCP leases, or DNS misconfiguration cause 'connected but no internet' and unidentified network errors.
- Root cause 2: RF interference, channel congestion, outdated drivers, or ISP-side throttling cause slow download/upload speeds and poor Wi-Fi signal.
- Root cause 3: Router firmware bugs, double-NAT, half-duplex mismatch on Ethernet, or faulty hardware cause intermittent drops and speeds far below your plan.
- Quick fix summary: Release/renew IP, flush DNS, update Wi-Fi adapter drivers, change Wi-Fi channel, reboot modem then router in sequence, and run a wired speed test to isolate the problem layer.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Release & Renew IP + Flush DNS | Connected but no internet, unidentified network, DHCP errors | 2 min | None |
| Change Wi-Fi Channel (2.4 GHz / 5 GHz) | Slow Wi-Fi, interference, 2.4 GHz working but 5 GHz not (or vice versa) | 5 min | Low — brief disconnection |
| Update/Reinstall Wi-Fi Adapter Driver | Wi-Fi not showing up, adapter errors, Intel AC 9560/AX200 not working | 10 min | Low — may require reboot |
| Power-cycle Modem then Router (sequence matters) | No internet after outage, ISP light errors, modem not connecting | 3 min | None |
| Factory Reset Router | Persistent DNS issues, double NAT, corrupt config, mywifiext not working | 15 min | Medium — loses all settings |
| Run Wired Ethernet Speed Test | Isolate whether slowness is Wi-Fi or ISP/modem layer | 5 min | None |
| Change DNS to 8.8.8.8 / 1.1.1.1 | Slow browsing, dns_probe_finished_nxdomain, pages load slow but speed test is fast | 3 min | Low |
| QoS / Bandwidth Throttle Check | Upload speed slow, download fast, ISP throttling suspected | 10 min | None |
Understanding the Problem: Why Is My Internet Slow or Not Connecting?
When you see messages like 'Can't connect to this network', 'Wi-Fi connected, no internet access', 'Unidentified network', or you're simply getting download speeds far below what you pay for, the fault can sit at any of four layers:
- Device layer — Wi-Fi adapter driver, IP stack corruption, or misconfigured DNS.
- Router/access-point layer — Channel congestion, firmware bug, double-NAT, or overheating.
- Modem layer — DHCP lease failure, upstream signal loss, or hardware fault.
- ISP layer — Throttling, line degradation, regional outage, or provisioning mismatch.
The diagnostic strategy below moves from the device outward, so you spend your time fixing the most likely culprit first.
Step 1: Confirm Which Layer Is Broken
Run a wired speed test first. Plug an Ethernet cable directly from your modem (bypassing the router) into your computer and visit fast.com or speedtest.net. Compare the result to your plan speed.
- Wired speed ≈ plan speed → problem is in your Wi-Fi or router.
- Wired speed also slow → problem is your modem or ISP.
- No IP address at all → DHCP or modem issue.
On Windows, open PowerShell as Administrator and run:
ipconfig /all
ping 8.8.8.8 -t
tracert 8.8.8.8
Look for Default Gateway in ipconfig output. If it shows 169.254.x.x (APIPA), your device never received a DHCP lease — the modem or router is not responding.
Step 2: Fix IP and DNS Issues on Windows
If you see 'Unidentified network', 'No internet access', or IPv4 connectivity: No network access, run the full IP stack reset:
# Run PowerShell or CMD as Administrator
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /flushdns
ipconfig /renew
Reboot after running these commands. This resolves the majority of 'connected but no internet' cases on Windows 10 and Windows 11.
For DNS-only slowness (pages load slowly but speed test is fast, dns_probe_finished_nxdomain), change your DNS:
- Open Network & Internet Settings → Change adapter options → Right-click adapter → Properties → IPv4 → Use the following DNS
- Set Preferred DNS:
1.1.1.1, Alternate:8.8.8.8
Step 3: Fix Wi-Fi Adapter Driver Issues
Drivers are the most common cause of Intel AC 9560 not working, Intel AX200/AX201 not working, killer Wi-Fi 6 AX1650 not working, and similar errors. The symptom is often that Wi-Fi shows as available but cannot connect, or it connects but drops constantly.
On Windows:
- Press
Win + X→ Device Manager → Network Adapters. - Right-click your Wi-Fi adapter → Update driver → Search automatically.
- If that fails: right-click → Uninstall device → check 'Delete driver software' → reboot. Windows will reinstall a clean driver.
- For Intel adapters, download the latest directly from Intel's driver page.
On macOS:
# Reset Wi-Fi on macOS
sudo ifconfig en0 down
sudo ifconfig en0 up
# If that doesn't help, remove saved Wi-Fi preferences:
sudo rm /Library/Preferences/SystemConfiguration/com.apple.wifi.plist
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
Reboot after removing the preference files.
Step 4: Fix Slow Wi-Fi — Channel Congestion and Band Issues
If your speed test over Wi-Fi is much lower than over Ethernet, the Wi-Fi radio is the bottleneck. Common causes:
Channel congestion: In dense apartment buildings, the 2.4 GHz band (channels 1, 6, 11) saturates quickly. Log in to your router admin page (typically 192.168.1.1 or 192.168.0.1) and change the 2.4 GHz channel. Use a Wi-Fi analyzer app (e.g., NetSpot on Mac/Windows, WiFi Analyzer on Android) to find the least-used channel.
2.4 GHz working but 5 GHz not (or vice versa): If your device can't connect to the 5 GHz band, check:
- The device is within ~15 meters of the router (5 GHz has shorter range).
- 5 GHz is enabled in router settings — some ISP-provided routers ship with it disabled.
- Your device supports Wi-Fi 5/6 — very old devices only support 2.4 GHz.
- DFS channels: If your router auto-selected a DFS channel (52–144 on 5 GHz), some devices drop off during radar detection events. Manually set a non-DFS channel (36, 40, 44, 48, 149–165).
Router placement: Walls, microwaves, baby monitors, and Bluetooth devices all interfere with 2.4 GHz. Move the router to a central, elevated position.
Step 5: Fix Slow Upload Speed
Slow upload speed with normal download speed is often caused by:
- Upload throttling by ISP (common on cable plans like Cox, Spectrum, Xfinity) — check your plan's advertised upload cap.
- QoS misconfiguration — a router applying bandwidth limits to upstream traffic.
- Half-duplex mismatch on Ethernet — if a device negotiates half-duplex instead of full-duplex, upload collisions cause severe slowdowns.
To check for duplex mismatch on Windows:
# Check current duplex setting
Get-NetAdapter | Select-Object Name, Speed, FullDuplex
If FullDuplex is False, open Device Manager → Network adapter → Properties → Advanced → find Speed & Duplex → set to 1.0 Gbps Full Duplex.
Step 6: Reboot Modem and Router in the Correct Sequence
A surprising number of 'no internet' issues resolve with a proper power-cycle sequence:
- Unplug the modem (and router if separate) from power. Wait 60 seconds — not 10. This allows the modem's DHCP lease to fully expire upstream.
- Plug in the modem only. Wait for all lights to stabilize (typically 90 seconds).
- Plug in the router. Wait 60 seconds.
- Reconnect your device.
This sequence fixes most Cox, CenturyLink, Frontier, Optimum, and Google Fiber 'no internet after outage' scenarios.
Step 7: Fix Double NAT
Double NAT (two devices both acting as routers/NAT gateways) causes game server connection failures, VPN issues, slow speeds, and port forwarding not working. You'll see it when ipconfig shows a 10.x.x.x or 192.168.x.x default gateway, and pinging that gateway reveals it's another NAT device behind the ISP modem-router.
Fix: Log in to your ISP's modem-router and enable Bridge Mode or IP Passthrough to let your own router handle NAT. Alternatively, disable the router function on your own router and use it only as an access point.
Step 8: ISP-Specific Checks
- Cox slow internet / Cox panoramic Wi-Fi not working: Check Cox's outage map at
cox.com/myaccount. If no outage, reboot the Panoramic modem by holding the reset button for 5 seconds (soft reset) or log in at192.168.0.1. Cox upload speeds are often capped at 35 Mbps on older DOCSIS 3.0 plans — upgrade to DOCSIS 3.1 plan for higher upload. - CenturyLink / Quantum Fiber slow / can't connect to this network: Log in to
192.168.0.1, verify PPPoE credentials are correct. CenturyLink DSL is distance-sensitive — if you're far from the DSLAM, speeds will be lower than advertised. - Google Fiber slow: Gigabit speeds require a Gigabit-capable Ethernet adapter AND a Cat 5e/Cat 6 cable. USB 2.0 to Ethernet adapters cap at ~300 Mbps. Test with
iperf3to rule out the LAN. - AT&T Wi-Fi issues / BGW210 problems: Log in at
192.168.1.254. If using your own router, enable IP Passthrough to the router's MAC address to avoid double NAT. - Frontier restart router: Log in at
192.168.254.254(Actiontec) or192.168.1.1(Arris). Use the admin reboot function rather than pulling power to avoid NVRAM corruption.
Step 9: Fixes for Smart TVs, Printers, and IoT Devices
LG TV says 'Wi-Fi is turned off': Go to Settings → All Settings → Network → Wi-Fi Connection and toggle Wi-Fi on. If the option is greyed out, perform a soft reset: Settings → Support → Self Diagnosis → Reset to Initial Settings. If the Wi-Fi module physically failed (common on older LG OLEDs), use a USB Wi-Fi adapter or Ethernet via the TV's LAN port.
HP printer says 'not connected to internet' / Canon printer won't connect to Wi-Fi: Most printer Wi-Fi issues are caused by connecting to the 5 GHz band — printers almost universally require 2.4 GHz. Ensure the printer is connecting to the 2.4 GHz SSID. After changing routers, run the printer's Wireless Setup Wizard from the control panel.
Alexa can't connect to Wi-Fi / having trouble connecting to internet: In the Alexa app, go to Devices → Echo & Alexa → [device] → Change Wi-Fi. Echo devices support only 2.4 GHz and 5 GHz WPA2 — they do not support WPA3 or 802.1X enterprise networks. If recently changed router password, you must reconfigure via the app.
Step 10: When Nothing Works — Advanced Diagnostics
# On Linux/macOS — full network diagnostic
ping -c 4 192.168.1.1 # Test gateway
ping -c 4 8.8.8.8 # Test internet IP (no DNS)
ping -c 4 google.com # Test DNS resolution
traceroute google.com # Find where packets stop
nslookup google.com 1.1.1.1 # Test alternate DNS
curl -o /dev/null -s -w "%{speed_download}" https://speed.cloudflare.com/__down?bytes=100000000
If ping 8.8.8.8 works but ping google.com fails, the issue is DNS-only. If ping 192.168.1.1 fails, the issue is between your device and router. If gateway pings fine but 8.8.8.8 fails, the issue is between your router and the internet (modem or ISP).
Frequently Asked Questions
#!/usr/bin/env bash
# ============================================================
# Network Diagnostic Script
# Works on Linux and macOS. For Windows, see PowerShell block below.
# ============================================================
echo "=== Network Interface Info ==="
if command -v ip &>/dev/null; then
ip addr show
else
ifconfig
fi
echo ""
echo "=== Default Gateway ==="
if command -v ip &>/dev/null; then
ip route show default
else
netstat -rn | grep default
fi
GATEWAY=$(ip route show default 2>/dev/null | awk '/default/ {print $3}' | head -1)
if [ -z "$GATEWAY" ]; then
GATEWAY=$(netstat -rn 2>/dev/null | grep default | awk '{print $2}' | head -1)
fi
echo ""
echo "=== Pinging Gateway ($GATEWAY) ==="
ping -c 4 "$GATEWAY"
echo ""
echo "=== Pinging 8.8.8.8 (Internet IP, no DNS) ==="
ping -c 4 8.8.8.8
echo ""
echo "=== Pinging google.com (DNS + Internet) ==="
ping -c 4 google.com
echo ""
echo "=== DNS Resolution Test ==="
nslookup google.com 1.1.1.1
nslookup google.com 8.8.8.8
echo ""
echo "=== Traceroute to 8.8.8.8 ==="
if command -v traceroute &>/dev/null; then
traceroute -m 15 8.8.8.8
else
tracepath -m 15 8.8.8.8
fi
echo ""
echo "=== Download Speed Test (requires curl) ==="
curl -o /dev/null -s -w "Download speed: %{speed_download} bytes/sec\nTime total: %{time_total}s\n" \
https://speed.cloudflare.com/__down?bytes=25000000
echo ""
echo "=== Wi-Fi Signal Strength (Linux) ==="
if command -v iwconfig &>/dev/null; then
iwconfig 2>/dev/null | grep -E 'Signal|Bit Rate|SSID'
fi
# ============================================================
# Windows PowerShell equivalent (run as Administrator):
# ============================================================
: <<'WIN_POWERSHELL'
# Run these in PowerShell (Admin):
# Full IP stack reset:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /flushdns
ipconfig /renew
# Show all adapters:
Get-NetAdapter | Select-Object Name, Status, LinkSpeed, MacAddress
# Test connectivity layers:
Test-NetConnection -ComputerName 192.168.1.1 -InformationLevel Detailed
Test-NetConnection -ComputerName 8.8.8.8 -InformationLevel Detailed
Test-NetConnection -ComputerName google.com -Port 443 -InformationLevel Detailed
# Check for duplex mismatch:
Get-NetAdapter | Select-Object Name, Speed, FullDuplex
# Check current DNS:
Get-DnsClientServerAddress
# Set DNS to Cloudflare + Google (replace 'Wi-Fi' with your adapter name):
Set-DnsClientServerAddress -InterfaceAlias 'Wi-Fi' -ServerAddresses ('1.1.1.1','8.8.8.8')
# Measure download speed:
$url = 'https://speed.cloudflare.com/__down?bytes=25000000'
$start = Get-Date
Invoke-WebRequest -Uri $url -OutFile $null -UseBasicParsing
$elapsed = (Get-Date) - $start
Write-Host "Elapsed: $($elapsed.TotalSeconds)s | Approx speed: $([math]::Round(25/($elapsed.TotalSeconds),2)) MB/s"
WIN_POWERSHELL
echo "=== Diagnostic Complete ==="Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network administrators with over a decade of experience diagnosing connectivity failures across enterprise and home networks. We specialize in translating complex TCP/IP and RF troubleshooting into actionable steps for every skill level.
Sources
- https://support.microsoft.com/en-us/windows/fix-wi-fi-connection-issues-in-windows-9424a1f7-6a3b-65a6-4d78-7f07eee84d2c
- https://support.google.com/fiber/answer/6240460
- https://www.intel.com/content/www/us/en/support/articles/000005489/wireless/legacy-intel-wireless-products.html
- https://superuser.com/questions/1358367/connected-to-wifi-but-no-internet-access-on-windows-10
- https://serverfault.com/questions/192116/how-to-diagnose-a-slow-network-connection
- https://www.reddit.com/r/HomeNetworking/wiki/index