Error Medic

Down Speed & Wi-Fi Not Working: Complete Troubleshooting Guide for Slow Internet, No Connection & 'Can't Connect to This Network' Errors

Fix slow download speeds, 'can't connect to this network', WiFi connected but no internet, and upload speed issues. Step-by-step commands included.

Last updated:
Last verified:
2,506 words
Key Takeaways
  • Most 'connected but no internet' errors stem from IP address conflicts, DNS failures, or outdated/corrupted network adapter drivers.
  • Slow download/upload speeds are usually caused by router channel congestion, ISP throttling, incorrect DNS servers, or half-duplex ethernet negotiation.
  • The fastest fixes are: flush DNS cache, release/renew IP address, reset TCP/IP stack, update network adapter drivers, and power-cycle modem+router in sequence.
  • Band-specific failures (2.4 GHz working but 5 GHz not, or vice versa) point to radio hardware issues or mismatched channel widths.
  • Persistent low down speed despite good speed-test results often indicates browser-level issues, VPN overhead, or QoS misconfiguration on the router.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Flush DNS + renew IP (ipconfig /flushdns)WiFi connected, no internet; pages not loading2 minNone
Reset TCP/IP stack (netsh int ip reset)Persistent 'unidentified network', limited connectivity5 min + rebootLow
Power-cycle modem and routerAll devices affected, ISP signal issue, modem not online3 minNone
Update/reinstall network adapter driverCan't connect to network, adapter not working, slow WiFi10 minLow
Change DNS to 8.8.8.8 / 1.1.1.1Slow browsing despite fast speed test, DNS probe errors2 minNone
Change WiFi channel (router admin)Slow WiFi, 2.4 GHz or 5 GHz congestion in the area5 minLow
Disable/re-enable network adapterAdapter shows as working but no connectivity1 minNone
Factory reset routerRouter firmware corrupted, double NAT, persistent DNS issues15 minMedium — loses config
Replace ethernet cableEthernet slower than WiFi, unidentified network on cable only5 minNone
Contact ISPDown speed slower than plan, slow broadband in area, ISP outage20+ minNone

Understanding 'Down Speed' Problems and WiFi Connection Failures

When your download speed (down speed) drops below what you pay for, or when you see errors like 'Can't connect to this network', 'WiFi connected but no internet', 'Unidentified network', or 'No internet access', the root cause usually falls into one of five categories:

  1. IP layer failures — DHCP couldn't assign an IP, or a stale lease caused a conflict.
  2. DNS resolution failure — Your device can't translate domain names to IP addresses.
  3. Physical/RF layer issues — Bad cable, weak WiFi signal, channel congestion, or a 2.4/5 GHz radio problem.
  4. Driver or adapter malfunction — The network adapter driver is outdated, corrupted, or has a power-management conflict.
  5. ISP or router-side problem — Modem not syncing, ISP outage, throttling, or router firmware bug.

Phase 1: Isolate the Scope of the Problem

Before running commands, answer these questions:

  • Is every device affected? If yes → modem/router or ISP issue. If only one device → driver or OS issue.
  • Is speed slow or completely down? Full outage vs. degraded performance have different causes.
  • Does ethernet work when WiFi doesn't? If yes → WiFi radio or band-specific problem.
  • Does a speed test show full speed but browsing is slow? If yes → DNS or browser issue, not bandwidth.

Phase 2: Quick Wins (Run First)

Step 1 — Power-cycle in the correct order:

  1. Unplug the modem (the box from your ISP) from power.
  2. Unplug the router.
  3. Wait 60 seconds.
  4. Plug in the modem first. Wait for all lights to stabilize (30–90 seconds).
  5. Plug in the router. Wait 60 seconds.
  6. Reconnect your device.

This resolves the majority of 'modem not connecting to internet', 'Cox WiFi not working', 'Frontier internet not working', and 'Google Fiber slow' complaints.

Step 2 — Flush DNS and renew your IP address (Windows): Open Command Prompt as Administrator and run the commands in the code block below.

Step 3 — Forget and reconnect the WiFi network: On Windows: Settings → Network & Internet → WiFi → Manage known networks → Forget your network → Reconnect and re-enter the password. This fixes 'Can't connect to this network' in over 40% of cases.

Step 4 — Disable IPv6 temporarily: Navigate to Control Panel → Network and Sharing Center → Change adapter settings → right-click your adapter → Properties → uncheck Internet Protocol Version 6 (TCP/IPv6) → OK. This resolves 'IPv6 no network access' and 'IPv4 and IPv6 no network access' errors common on Windows 10/11.


Phase 3: Diagnosing Slow Down Speed

Check what speed you're actually getting: Run a speed test at fast.com and speedtest.net. Compare results. If fast.com (Netflix CDN) is dramatically slower than speedtest.net, your ISP may be throttling specific traffic types.

Check for channel congestion (2.4 GHz): Use a WiFi analyzer app (e.g., NetSpot on Mac, WiFi Analyzer on Android). If channels 1, 6, or 11 are congested by neighbors, log into your router admin (typically http://192.168.1.1 or http://192.168.0.1) and manually set your 2.4 GHz band to the least-congested channel.

Check ethernet duplex settings: If your ethernet connection is slower than WiFi ('ethernet slower than WiFi'), open Device Manager → Network Adapters → right-click your ethernet adapter → Properties → Advanced tab → set Speed & Duplex to match your router's setting (usually 1.0 Gbps Full Duplex).

Check for ISP throttling: Run a speed test with a VPN enabled. If speed increases significantly with VPN, your ISP is throttling specific protocols or services.


Phase 4: Driver-Level Fixes

Common affected adapters: Intel Wi-Fi 6 AX200, AX201, AX210; Realtek RTL8822CE; MediaTek MT7921; Intel Wireless-AC 9560, 9462; Killer Wi-Fi 6 AX1650.

Update the driver:

  1. Open Device Manager (Win+X → Device Manager).
  2. Expand Network adapters.
  3. Right-click your WiFi adapter → Update driver → Search automatically.
  4. If that fails, download the driver directly from the manufacturer's website (Intel, Realtek, MediaTek) and install manually.

Disable power management on the adapter:

  1. In Device Manager, right-click your WiFi adapter → Properties.
  2. Click the Power Management tab.
  3. Uncheck Allow the computer to turn off this device to save power.
  4. Click OK.

This fixes WiFi dropping intermittently, 'laptop can't find WiFi network', and slow upload speed issues common on Dell, Lenovo, HP, and Acer laptops.


Phase 5: Router-Specific Fixes

Nighthawk router troubleshooting: If you can't access the router admin at routerlogin.net or 192.168.1.1, try connecting via ethernet cable directly to the router. If still unreachable, do a factory reset (press the reset button for 10 seconds). Common Nighthawk issues include double NAT (check WAN IP — if it's 192.168.x.x or 10.x.x.x, you have double NAT) and DNS server misconfiguration.

Fixing double NAT: Log into your router and check the WAN/Internet status page. If the WAN IP is a private IP range (192.168.x.x, 10.x.x.x, 172.16-31.x.x), you have double NAT. Either put your ISP's modem/gateway into bridge mode, or enable DMZ on the ISP device pointing to your router's WAN IP.

mywifiext.net not working / www.mywifiext.net refused to connect: The Netgear extender setup page only works when you're connected to the extender's own network (NETGEAR_EXT). Connect to that SSID first, then navigate to http://mywifiext.net or http://192.168.1.250. If still refused, factory reset the extender.

Cox Panoramic WiFi not working (blinking orange): Blinking orange light means the modem is not synced with Cox's network. Check for a Cox outage at cox.com/residential/support/internet-status. If no outage, reboot the gateway. If it persists more than 15 minutes, Cox likely needs to re-provision the modem remotely.


Phase 6: Device-Specific Fixes

LG Smart TV WiFi turned off / won't connect: Go to Settings → All Settings → Network → Wi-Fi Connection. If WiFi shows as 'turned off', go to Settings → All Settings → General → Reset to Initial Settings (a full factory reset is sometimes the only fix for the LG TV 'WiFi is turned off' bug). Alternatively, update the TV firmware via USB if WiFi can't connect.

Chromebook not connecting to WiFi: Go to Settings → Network → WiFi → click your network → Forget → reconnect. If Chrome OS shows 'Network not available', open the terminal (Ctrl+Alt+T), type shell, then run: sudo restart shill to restart the network service.

iPhone can't connect to WiFi: Go to Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings. This clears all saved networks, VPN configurations, and APN settings. Reconnect to your WiFi afterwards.

Alexa can't connect to WiFi / Alexa having trouble connecting to the internet: In the Alexa app: Devices → Echo & Alexa → your device → Change → follow the WiFi setup wizard. Ensure you're on 2.4 GHz (most Echo devices don't support 5 GHz). If still failing, deregister and re-register the device in the Alexa app.

HP Printer not connecting to WiFi: On the printer, go to Network Setup → Restore Network Settings. Then re-run the Wireless Setup Wizard. If the printer connects but shows 'not connected to internet', verify your router firewall is not blocking UDP port 5353 (mDNS/Bonjour).


Phase 7: When to Call Your ISP

Call your ISP if:

  • Down speed is consistently below 60% of your plan speed after all device-level fixes.
  • The outage or slowdown affects all devices simultaneously.
  • Your modem never syncs (no solid internet light).
  • You see 'DSL no signal' or the modem shows no upstream/downstream channels.
  • Providers like Cox, CenturyLink, Frontier, Optimum, Breezeline, Windstream, Mediacom, or Google Fiber have confirmed outages in your area.

Always run three speed tests at different times of day before calling, and note the results. ISPs will ask for these.

Frequently Asked Questions

bash
# ============================================================
# WINDOWS: Full Network Reset & Diagnostic Script
# Run as Administrator in Command Prompt or PowerShell
# ============================================================

# Step 1: Check current IP configuration
ipconfig /all

# Step 2: Test DNS resolution
nslookup google.com
nslookup google.com 8.8.8.8

# Step 3: Test basic connectivity
ping 8.8.8.8 -n 10
ping google.com -n 10

# Step 4: Trace the route to find where packets drop
tracert google.com

# Step 5: Flush DNS cache
ipconfig /flushdns

# Step 6: Release and renew IP address
ipconfig /release
ipconfig /renew

# Step 7: Reset Winsock (fixes corrupted socket layer)
netsh winsock reset

# Step 8: Reset TCP/IP stack
netsh int ip reset C:\resetlog.txt

# Step 9: Reset IPv4 and IPv6
netsh int ipv4 reset
netsh int ipv6 reset

# Step 10: Reset Windows Firewall to defaults (use carefully)
netsh advfirewall reset

# Step 11: Set DNS manually to Cloudflare (replace 'Wi-Fi' with your adapter name if different)
netsh interface ip set dns name="Wi-Fi" static 1.1.1.1
netsh interface ip add dns name="Wi-Fi" 8.8.8.8 index=2

# Step 12: Check for adapter-level errors
netsh interface show interface
netsh wlan show interfaces
netsh wlan show drivers

# Step 13: Delete corrupted WiFi profile (replace YOUR_WIFI_NAME)
netsh wlan delete profile name="YOUR_WIFI_NAME"

# Step 14: Check current speed negotiation on ethernet
Get-NetAdapter | Select-Object Name, LinkSpeed, MediaConnectionState

# Step 15: Reboot required after steps 7-9
shutdown /r /t 10 /c "Rebooting after network stack reset"

# ============================================================
# LINUX / macOS: Diagnostic Commands
# ============================================================

# Check IP configuration (Linux)
ip addr show
ip route show
cat /etc/resolv.conf

# Flush DNS (macOS Ventura/Monterey/Sonoma)
sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder

# Flush DNS (Linux systemd-resolved)
sudo systemd-resolve --flush-caches

# Check WiFi signal and channel (Linux)
iwconfig
iw dev wlan0 link
nmcli device wifi list

# Release and renew DHCP (Linux)
sudo dhclient -r && sudo dhclient

# Test speed from CLI (requires speedtest-cli)
pip install speedtest-cli
speedtest-cli --simple

# Check for packet loss on your gateway
ping -c 20 192.168.1.1

# Run MTR (combined ping + traceroute) to find slow hops
mtr --report google.com

# Restart networking service (Linux)
sudo systemctl restart NetworkManager

# Check Chromebook shill network service
# (run in Chrome OS terminal: Ctrl+Alt+T, then type 'shell')
sudo restart shill
E

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and network administrators with 10+ years of experience diagnosing connectivity issues across home networks, enterprise infrastructure, and cloud environments. Our guides are tested on real hardware and validated against official vendor documentation before publication.

Sources

Related Articles in Other

Explore More wifi Guides