2.4 GHz Not Working But 5 GHz Working on TP-Link Router (Full Fix Guide)
Fix TP-Link 2.4 GHz not working while 5 GHz works. Step-by-step guide covering band steering, DNS issues, Chromecast problems, and login failures.
- Root cause 1: The 2.4 GHz radio may be disabled, broadcasting on a conflicting channel, or misconfigured in the TP-Link admin panel — while 5 GHz remains unaffected because it operates on a separate radio chip and channel range.
- Root cause 2: Band steering, Smart Connect, or firmware bugs can silently suppress the 2.4 GHz SSID, causing devices like Chromecast and IoT gadgets that only support 2.4 GHz to fail connection while 5 GHz devices stay online.
- Quick fix summary: Log into your TP-Link admin panel at 192.168.0.1 or tplinkwifi.net, navigate to Wireless > 2.4 GHz settings, confirm the band is enabled, set a non-overlapping channel (1, 6, or 11), disable Smart Connect if active, reboot the router, and update firmware if the issue persists.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Re-enable 2.4 GHz radio in admin panel | 2.4 GHz SSID missing from Wi-Fi list entirely | 2 min | None |
| Change 2.4 GHz channel to 1, 6, or 11 | 2.4 GHz visible but slow or dropping connections | 3 min | None |
| Disable Smart Connect / Band Steering | Devices stuck on wrong band or failing handshake | 3 min | Low — may require device reconnection |
| Flush DNS and reset TCP/IP stack | Connected to 2.4 GHz but no internet (DNS errors) | 5 min | None |
| Factory reset via router pin | Admin login fails or settings are corrupted | 10 min | High — all settings lost |
| Firmware update via TP-Link admin panel | Persistent bug after all other fixes fail | 10-20 min | Medium — router restarts |
| Separate 2.4 GHz and 5 GHz SSIDs | Chromecast or smart home devices can't connect | 5 min | Low — device re-pairing needed |
Understanding Why 2.4 GHz Stops Working While 5 GHz Remains Active
TP-Link routers use two physically separate radio chips — one for 2.4 GHz and one for 5 GHz. This is why one band can completely fail while the other continues operating normally. The 2.4 GHz band is especially prone to interference because it shares spectrum with Bluetooth, microwaves, baby monitors, and neighboring Wi-Fi networks. The 5 GHz band, operating on less crowded frequencies, typically remains stable.
Common symptoms include:
- Your 2.4 GHz SSID disappears from available Wi-Fi networks
- Devices connect to 2.4 GHz but show "Connected, no internet" or "Internet status: Disconnected" in the TP-Link dashboard
- Chromecast, smart plugs, and IoT sensors fail to connect while laptops and phones on 5 GHz work fine
- You see error messages like
DNS_PROBE_FINISHED_NO_INTERNETorERR_NAME_NOT_RESOLVEDon 2.4 GHz clients - The TP-Link admin panel at
192.168.0.1shows WAN status as "Disconnected" for specific clients
Step 1: Log Into the TP-Link Admin Panel
Open a browser and navigate to http://192.168.0.1 or http://tplinkwifi.net. If you cannot login to your TP-Link router:
- Try the default credentials: Username
admin, Passwordadmin - If those fail, check the sticker on the bottom of your router for a custom default password
- If the page doesn't load at all, ensure you are connected via Ethernet or the 5 GHz band (which is still working)
- Try
http://192.168.1.1if192.168.0.1doesn't respond — some TP-Link models use the alternate subnet
If you see ERR_CONNECTION_REFUSED or the page times out, your router may need a factory reset (see Step 6).
Step 2: Verify 2.4 GHz Radio Is Enabled
Once logged in:
- Navigate to Wireless > Wireless Settings (for older firmware) or Advanced > Wireless > Wireless Settings (for newer firmware)
- Select the 2.4 GHz tab
- Confirm Enable Wireless Radio checkbox is ticked
- Verify your SSID is entered and Broadcast SSID (or "Broadcast Network Name") is enabled
- Click Save and reboot the router
If the checkbox was already ticked, proceed to channel configuration.
Step 3: Fix Channel Congestion on 2.4 GHz
Automatic channel selection often picks congested channels. Manually set a non-overlapping channel:
- In the Wireless Settings for 2.4 GHz, change Channel from
Autoto1,6, or11 - Set Channel Width to
Autoor20MHz(avoid 40MHz if interference is heavy) - Save and reboot
To find the least congested channel on Windows before making changes, open Command Prompt as Administrator and run:
netsh wlan show networks mode=bssid
On macOS, hold Option and click the Wi-Fi menu icon, then select Open Wireless Diagnostics > Window > Scan.
Step 4: Disable Smart Connect / Band Steering
TP-Link's Smart Connect feature merges 2.4 GHz and 5 GHz into a single SSID and automatically assigns devices to a band. This feature frequently causes problems for devices that explicitly need 2.4 GHz (Chromecast, Ring doorbells, Philips Hue bridges).
To disable it:
- Navigate to Advanced > Wireless > Wireless Settings
- Toggle off Smart Connect or Band Steering
- You will be prompted to configure separate SSIDs for each band — name them distinctly, e.g.,
HomeNetwork_2.4GandHomeNetwork_5G - Save and reconnect your IoT/Chromecast devices to the 2.4 GHz SSID explicitly
Step 5: Fix DNS Problems on 2.4 GHz Clients
If devices connect to 2.4 GHz but show "Connected without internet" or DNS failures, the issue may be DNS misconfiguration on the router or client.
On the TP-Link router:
- Go to Advanced > Network > Internet (or DHCP Settings)
- Under Primary DNS, enter
8.8.8.8(Google) or1.1.1.1(Cloudflare) - Under Secondary DNS, enter
8.8.4.4or1.0.0.1 - Save and reboot
On a Windows client connected to 2.4 GHz: Open Command Prompt as Administrator and run the full flush sequence:
ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh int ip reset
netsh winsock reset
Restart the PC after running these commands.
On macOS:
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
Step 6: Fix Chromecast TP-Link Problems
Chromecast (all generations) only supports 2.4 GHz or requires specific 5 GHz configurations. Common fixes:
- Ensure Smart Connect is disabled so 2.4 GHz has its own SSID
- Disable AP Isolation on TP-Link: Navigate to Advanced > Wireless > Advanced Settings and uncheck AP Isolation for 2.4 GHz
- Ensure Multicast is not being filtered — go to Advanced > Network > IGMP Proxy and enable it
- Factory reset the Chromecast and re-pair it to the 2.4 GHz network
Step 7: Update TP-Link Firmware
Firmware bugs are a documented cause of 2.4 GHz radio failure on TP-Link Archer and Deco models:
- Go to Advanced > System Tools > Firmware Upgrade
- Click Check for Updates (requires internet via 5 GHz or Ethernet)
- Alternatively, download the firmware manually from
https://www.tp-link.com/us/support/download/matching your exact model and hardware version (found on the router's bottom label) - Upload and apply — the router will reboot automatically
Step 8: Factory Reset as Last Resort
If you still cannot login to the TP-Link router or no settings change resolves the issue:
- Locate the Reset pinhole on the router's back or bottom
- With the router powered on, hold the pin for 10-15 seconds until the LED flashes
- Release and wait 2 minutes for the router to fully reboot
- Reconnect using default credentials and reconfigure from scratch
Note: After factory reset, you must reconfigure your ISP connection settings (PPPoE username/password if applicable).
Frequently Asked Questions
#!/bin/bash
# TP-Link Wi-Fi Diagnostic Script
# Run on a client connected via Ethernet or 5 GHz while 2.4 GHz is down
# Works on Linux/macOS; Windows equivalents are shown in comments
echo "=== TP-Link 2.4 GHz Troubleshooting Diagnostics ==="
echo ""
# --- 1. Check default gateway (router IP) ---
echo "[1] Detecting default gateway..."
if [[ "$OSTYPE" == "darwin"* ]]; then
GATEWAY=$(netstat -nr | grep default | awk '{print $2}' | head -1)
else
GATEWAY=$(ip route | grep default | awk '{print $3}' | head -1)
fi
echo " Gateway: $GATEWAY"
# Windows: ipconfig | findstr "Default Gateway"
# --- 2. Ping gateway to test LAN connectivity ---
echo "[2] Pinging router gateway ($GATEWAY)..."
ping -c 4 $GATEWAY
# Windows: ping 192.168.0.1
# --- 3. Ping external IP to test WAN connectivity ---
echo "[3] Pinging 8.8.8.8 to test WAN (bypass DNS)..."
ping -c 4 8.8.8.8
# Windows: ping 8.8.8.8
# --- 4. DNS resolution test ---
echo "[4] Testing DNS resolution..."
nslookup google.com
# Windows: nslookup google.com
# --- 5. Traceroute to detect where traffic drops ---
echo "[5] Running traceroute to 8.8.8.8..."
if [[ "$OSTYPE" == "darwin"* ]]; then
traceroute -m 15 8.8.8.8
else
traceroute -m 15 8.8.8.8 2>/dev/null || tracepath 8.8.8.8
fi
# Windows: tracert 8.8.8.8
# --- 6. Check current DNS servers assigned ---
echo "[6] Checking assigned DNS servers..."
if [[ "$OSTYPE" == "darwin"* ]]; then
scutil --dns | grep nameserver | head -5
else
cat /etc/resolv.conf
fi
# Windows: ipconfig /all | findstr DNS
# --- 7. Scan 2.4 GHz channels for congestion (Linux only, requires iwlist) ---
echo "[7] Scanning for nearby 2.4 GHz networks and channel usage..."
if command -v iwlist &> /dev/null; then
sudo iwlist scan 2>/dev/null | grep -E 'ESSID|Channel|Frequency' | grep -A1 '2.4\|Frequency:2'
else
echo " iwlist not available. On macOS use: airport -s"
echo " Install on Linux: sudo apt install wireless-tools"
fi
# macOS: /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -s
# Windows: netsh wlan show networks mode=bssid
# --- 8. Flush DNS cache ---
echo "[8] Flushing DNS cache..."
if [[ "$OSTYPE" == "darwin"* ]]; then
sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
echo " macOS DNS cache flushed."
else
sudo systemd-resolve --flush-caches 2>/dev/null || sudo /etc/init.d/dns-clean restart 2>/dev/null
echo " Linux DNS cache flushed."
fi
# Windows (run as Administrator):
# ipconfig /flushdns
# ipconfig /release
# ipconfig /renew
# netsh int ip reset
# netsh winsock reset
# --- 9. Check current IP address and subnet ---
echo "[9] Current IP configuration:"
if [[ "$OSTYPE" == "darwin"* ]]; then
ifconfig | grep -E 'inet |ether' | grep -v '127.0.0.1'
else
ip addr show | grep -E 'inet |link/ether' | grep -v '127.0.0.1'
fi
# Windows: ipconfig /all
echo ""
echo "=== Diagnostics Complete ==="
echo "If 2.4 GHz SSID is missing: Log into http://192.168.0.1 and re-enable the 2.4 GHz radio."
echo "If DNS fails: Set router DNS to 8.8.8.8 / 8.8.4.4 in Advanced > Network > DHCP Settings."
echo "If WAN ping fails: Check ISP connection and WAN settings under Advanced > Network > Internet."Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, SREs, and network specialists with combined experience spanning enterprise infrastructure, home networking, and ISP-level troubleshooting. We write actionable, command-driven guides grounded in real-world diagnosis rather than generic advice. Our TP-Link coverage includes Archer, Deco, and TL-series routers across firmware generations.