2.4 GHz Not Working but 5 GHz Working on TP-Link (Or Vice Versa): Full Troubleshooting Guide
Fix TP-Link 2.4 GHz or 5 GHz band not working. Step-by-step guide covering DNS errors, internet disconnected, Chromecast issues, and login problems.
- Root cause 1: Band steering or smart connect misconfiguration causes one radio (2.4 GHz or 5 GHz) to appear disabled or unreachable even though the hardware is functioning.
- Root cause 2: Incorrect DNS settings, DHCP conflicts, or a corrupt wireless channel assignment can make one band show 'Connected without Internet' or 'Internet Status: Disconnected' even when the other band works fine.
- Root cause 3: Firmware bugs in certain TP-Link models (e.g., Archer AX series) disable the 2.4 GHz radio after a failed OTA update, requiring a manual firmware flash or factory reset.
- Quick fix summary: Log in to 192.168.0.1 or 192.168.1.1, verify both radios are enabled under Wireless > Wireless Settings, set DNS to 8.8.8.8 / 8.8.4.4, change 2.4 GHz channel to 1, 6, or 11, and reboot. If login fails, use the TP-Link Tether app or perform a 10-second factory reset.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Enable disabled radio in admin panel | One band missing from SSID list entirely | 2 min | Low |
| Change wireless channel (1, 6, or 11 for 2.4 GHz) | Band visible but slow or dropping | 3 min | Low |
| Fix DNS (set to 8.8.8.8) | Connected without Internet on one band | 2 min | Low |
| Factory reset (hold Reset 10 sec) | Cannot log in or settings are corrupt | 5 min + reconfigure | Medium |
| Manual firmware flash via TFTP | Firmware corruption after failed OTA update | 20 min | High |
| Disable Smart Connect / Band Steering | Devices stuck on wrong band or band invisible | 3 min | Low |
| Reassign DHCP IP range | IP conflict between 2.4 and 5 GHz clients | 5 min | Low |
Understanding the Error
TP-Link routers broadcast two separate wireless radios — a 2.4 GHz band for range and a 5 GHz band for speed. When one band stops working while the other continues normally, users see symptoms such as:
- The 2.4 GHz SSID disappears from device Wi-Fi scan lists
- Devices on 2.4 GHz show "Connected, no internet" or "Internet Status: Disconnected"
- 5 GHz devices browse normally while 2.4 GHz devices get DNS errors
- Chromecast (which requires 2.4 GHz or a matching SSID) fails to cast
- The TP-Link admin panel at 192.168.0.1 becomes unreachable
This guide walks through every layer — hardware, firmware, wireless settings, DNS, and DHCP — to restore full dual-band operation.
Step 1: Confirm Which Band Is Affected
Before touching any settings, identify the exact failure mode.
On Windows:
netsh wlan show networks mode=bssid
Look for both your 2.4 GHz and 5 GHz SSIDs. If only one appears, the radio may be disabled or the channel is being blocked.
On macOS: Hold Option and click the Wi-Fi icon → "Open Wireless Diagnostics" → Window → Scan. Both bands will appear with their frequency listed.
On Android/iOS: Install a Wi-Fi analyzer app (e.g., WiFi Analyzer by farproc) and scan. Each SSID entry will show channel number — channels 1–14 are 2.4 GHz, channels 36+ are 5 GHz.
Step 2: Log In to the TP-Link Admin Panel
Navigate to http://192.168.0.1 or http://192.168.1.1 in a browser. Default credentials are:
- Username:
admin - Password:
admin(or the password printed on the router label)
If you see "This site can't be reached" or the page times out:
- Connect via Ethernet cable directly to a LAN port.
- Run
ipconfig(Windows) orip route(Linux/macOS) and check the Default Gateway — use that IP instead. - If still unreachable, the router may need a factory reset (hold the Reset button for 10 seconds with the router powered on).
Cannot login to TP-Link router error: If the password is rejected, the Tether mobile app can sometimes access the router over Wi-Fi using the admin PIN printed on the label. Alternatively, a factory reset is required.
Step 3: Verify Both Radios Are Enabled
Once logged in:
- Go to Wireless (for older models) or Advanced > Wireless (for newer Archer models).
- Check Wireless Settings for both 2.4 GHz and 5 GHz tabs.
- Ensure "Enable Wireless Radio" is checked for both.
- Verify the SSID is not blank or hidden unintentionally.
- Click Save and reboot the router.
On TP-Link Deco mesh systems, open the Deco app → tap your Deco unit → "Wi-Fi" → confirm 2.4 GHz is not toggled off.
Step 4: Fix Smart Connect / Band Steering Issues
TP-Link's "Smart Connect" feature merges both bands under a single SSID and automatically assigns devices. This causes problems when:
- Devices that need 2.4 GHz (Chromecast, smart home devices, IoT sensors) get assigned to 5 GHz
- The band steering algorithm keeps flipping a device between bands, causing drops
To disable Smart Connect:
- Log in → Advanced > Wireless
- Find the Smart Connect toggle and turn it OFF
- Assign unique names: e.g.,
HomeNetwork_2.4GandHomeNetwork_5G - Click Save and reboot
After disabling, manually connect your Chromecast and other 2.4 GHz-only devices to the _2.4G SSID.
Step 5: Change the Wireless Channel
Channel interference is the most common reason 2.4 GHz appears connected but delivers no internet while 5 GHz works fine.
- Go to Wireless > Wireless Settings > 2.4 GHz
- Change Channel from "Auto" to 1, 6, or 11 (the only non-overlapping 2.4 GHz channels)
- For 5 GHz, if you're in a congested area, try channels 36, 40, or 149
- Set Channel Width to 20 MHz on 2.4 GHz for maximum compatibility (use Auto/40 MHz only for throughput)
- Save and reboot
Step 6: Fix DNS TP-Link Problems
Symptom: Connected to 2.4 GHz, router shows "Internet Status: Connected," but websites don't load and ping to domain names fails while ping to 8.8.8.8 succeeds.
This is a DNS resolution failure. TP-Link routers sometimes apply incorrect DNS from ISP DHCP leases.
Fix via admin panel:
- Go to Advanced > Network > DHCP Server
- Set Primary DNS to
8.8.8.8 - Set Secondary DNS to
8.8.4.4 - Click Save
Fix on the client device (temporary):
- Windows:
netsh interface ip set dns "Wi-Fi" static 8.8.8.8 - Linux: Edit
/etc/resolv.confand addnameserver 8.8.8.8 - macOS: System Preferences → Network → Wi-Fi → Advanced → DNS → add 8.8.8.8
Verify DNS is working:
nslookup google.com 8.8.8.8
If this resolves but your default DNS does not, the issue is confirmed DNS misconfiguration on the router.
Step 7: Fix "Connected Without Internet" on TP-Link
The "Connected without internet" warning means the device got an IP address via DHCP but cannot reach the internet. Causes:
- WAN/ISP connection dropped — check the TP-Link status page (Basic > Internet). If it shows "Internet Status: Disconnected," the issue is upstream of the router. Power cycle the modem first.
- IP conflict — two devices have the same IP. Go to Advanced > Network > DHCP Server and confirm the lease pool doesn't overlap with any static IPs you've assigned.
- Captive portal loop — some ISPs require MAC address registration. If you replaced a router, clone the old router's MAC under Advanced > Network > Internet > MAC Clone.
- MTU mismatch — try setting MTU to 1492 under WAN settings if you're on PPPoE, or 1500 for cable/fiber.
Step 8: Chromecast TP-Link Problem
Chromecast requires the casting device (phone/laptop) and the Chromecast to be on the same network and same subnet. With TP-Link's Smart Connect enabled or with 2.4 GHz/5 GHz on different subnets, this breaks.
Fix:
- Disable Smart Connect (Step 4) and give both bands the same SSID or connect both devices to the same band.
- Ensure AP Isolation is disabled: Advanced > Wireless > Additional Settings → uncheck "AP Isolation."
- Disable any Guest Network that Chromecast might accidentally join.
- Factory reset the Chromecast and re-add it while your phone is connected to the 2.4 GHz SSID.
- If using TP-Link Deco with IoT Network enabled, move the Chromecast back to the main network.
Step 9: Manual Firmware Flash (Last Resort)
If the 2.4 GHz radio is completely dead after a firmware update and a factory reset didn't help:
- Download the correct firmware for your exact model and hardware version from https://www.tp-link.com/us/support/download/
- Connect via Ethernet to LAN port 1
- In TP-Link admin: Advanced > System Tools > Firmware Upgrade → upload the .bin file
- For TFTP recovery (router unresponsive): Set your PC to static IP 192.168.0.66, open TFTP server, name the firmware file
ArcherXXXv1_tp_recovery.bin, hold the WPS button while powering on the router until the power LED flashes
Step 10: Factory Reset as Final Step
If nothing else works:
- Hold the Reset pinhole button for 10 seconds while the router is on
- Wait 2 minutes for the router to reboot
- Reconnect using default credentials from the label
- Reconfigure WAN, SSID, and DNS settings from scratch
- Do NOT restore from a saved backup config — it may reintroduce the corrupt setting
Frequently Asked Questions
#!/usr/bin/env bash
# TP-Link Dual-Band Diagnostic Script
# Run on Linux/macOS. For Windows, use the netsh equivalents commented below.
echo "=== Step 1: Show current Wi-Fi connection info ==="
if command -v nmcli &>/dev/null; then
nmcli device wifi list
else
echo "nmcli not found, trying iwconfig..."
iwconfig 2>/dev/null || echo "iwconfig not found. Install wireless-tools."
fi
# Windows equivalent: netsh wlan show networks mode=bssid
echo ""
echo "=== Step 2: Check default gateway (TP-Link admin IP) ==="
ip route show | grep default
# Windows: ipconfig | findstr /i "Default Gateway"
# macOS: netstat -nr | grep default
echo ""
echo "=== Step 3: Ping default gateway (should be 192.168.0.1 or 192.168.1.1) ==="
GATEWAY=$(ip route show | grep default | awk '{print $3}' | head -1)
echo "Gateway detected: $GATEWAY"
ping -c 4 "$GATEWAY"
# Windows: ping 192.168.0.1
echo ""
echo "=== Step 4: Test DNS resolution ==="
echo "Testing system DNS..."
nslookup google.com
echo ""
echo "Testing Google DNS directly (8.8.8.8)..."
nslookup google.com 8.8.8.8
# If system DNS fails but 8.8.8.8 works, set DNS to 8.8.8.8 in TP-Link admin
# Windows: nslookup google.com && nslookup google.com 8.8.8.8
echo ""
echo "=== Step 5: Test internet connectivity (bypass DNS) ==="
ping -c 4 8.8.8.8
ping -c 4 1.1.1.1
# If these fail, the problem is at the WAN/modem layer, not DNS
echo ""
echo "=== Step 6: Check for IP conflicts or duplicate assignments ==="
arp -a | sort
# Look for duplicate IPs with different MACs — that indicates DHCP conflict
# Windows: arp -a
echo ""
echo "=== Step 7: Check wireless channel (Linux only) ==="
if command -v iwlist &>/dev/null; then
sudo iwlist scan 2>/dev/null | grep -E '(ESSID|Frequency|Channel)'
fi
# Look for your SSID — frequency 2.4xx GHz = 2.4 band, 5.xxx GHz = 5 GHz band
echo ""
echo "=== Step 8: Flush DNS cache ==="
if command -v systemd-resolve &>/dev/null; then
sudo systemd-resolve --flush-caches && echo "systemd DNS cache flushed"
elif command -v dscacheutil &>/dev/null; then
sudo dscacheutil -flushcache && echo "macOS DNS cache flushed"
fi
# Windows: ipconfig /flushdns
echo ""
echo "=== Step 9: Attempt to reach TP-Link admin panel ==="
curl -s --max-time 5 http://192.168.0.1 | grep -i "tp-link\|tplink\|login" | head -5
curl -s --max-time 5 http://192.168.1.1 | grep -i "tp-link\|tplink\|login" | head -5
# If no output, the router admin page is unreachable — connect via Ethernet
echo ""
echo "=== Diagnostic complete ==="
echo "Summary:"
echo " - If Step 3 (gateway ping) fails: connect via Ethernet and check router power"
echo " - If Step 4 system DNS fails but 8.8.8.8 works: set DNS to 8.8.8.8 in TP-Link admin"
echo " - If Step 5 fails: modem/ISP issue — power cycle modem"
echo " - If Step 6 shows duplicate IPs: check DHCP pool in TP-Link admin"
echo " - If Step 9 shows no output: factory reset router (hold Reset 10 sec)"Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, network administrators, and SRE professionals with 10+ years of experience diagnosing home and enterprise networking issues. We specialize in translating complex router, DNS, and wireless troubleshooting into clear, actionable guides for both technical and non-technical audiences.