What's going on

Few things are more frustrating than having four devices streaming smoothly in your living room while a newly unboxed phone or laptop repeatedly refuses to join your ASUS network. Because existing connections continue to function normally, it is easy to assume the new device is broken.

In most cases, the router's operating system (Asuswrt) is actively blocking or dropping the handshake. This typically happens when the router runs out of local network IP addresses to hand out, enforces strict WPA3 security protocols that the new device cannot parse, or holds onto stale configuration tables in its non-volatile memory (NVRAM).

Symptoms people notice

• Existing family devices remain connected to Wi-Fi without issue, but any new client fails during authentication.
• Mobile devices report "Failed to obtain IP address" or switch immediately to cellular data.
• The connection panel claims the Wi-Fi password is wrong even after re-entering it multiple times.
• Smart home IoT accessories (smart plugs, doorbells) refuse to complete setup on 2.4GHz networks.
• The ASUS router System Log repeatedly shows DHCPD: DHCPREQUEST without a corresponding DHCPACK response.

Likely causes

1. DHCP Pool Exhaustion: The router has reached its configured limit for assigned IP addresses or has set an excessively long lease time for historical connections.
2. Security Protocol Conflicts: Modern ASUS routers default to WPA2/WPA3 mixed mode with Protected Management Frames (PMF) enabled, which causes handshake timeouts on non-WPA3 hardware.
3. Active Wireless MAC Filtering: An enabled MAC filter setting rejects any Wi-Fi chipset address not explicitly placed on the whitelist.
4. Smart Connect Band Steering: The router attempts to force a 2.4GHz-only client onto a 5GHz band, dropping the connection attempt.
5. Corrupted Asuswrt NVRAM: Firmware updates can leave residual configuration variables that prevent new client handshakes until cleared.

Quick checks first

Before digging into advanced router settings or replacing hardware, perform these basic sanity checks:

• Restart the Router: Pull the power cable from your ASUS router, wait 30 seconds, and plug it back in. This temporarily flushes transient IP assignment locks.
• Disable Randomized MAC Addresses: Modern iOS and Android phones use dynamic private Wi-Fi addresses. Disable "Private Address" in the phone's Wi-Fi settings for your home SSID to see if authentication succeeds.
• Test Guest Network: Turn on Guest Network 1 in Asuswrt. If the new device connects to the guest network without issue, the main network's security or filtering rules are definitely cause for blame. Check our general router troubleshooting hub for additional network layer triage.

When it's a real hardware fault

While most connection failures stem from software misconfigurations, internal hardware degradation can manifest as selective connection drops. ASUS dual-band and tri-band routers rely on independent Power Amplifier (PA) and Low Noise Amplifier (LNA) modules for each radio frequency.

If the 2.4GHz PA module experiences thermal degradation, the router may continue broadcasting the SSID with high beacon strength, but fail to receive the lower-power return transmission from a new device trying to authenticate. If soft resets, factory resets, and firmware downgrades fail across all bands while legacy devices gradually begin dropping off, the Wi-Fi radio SoC or system board capacitors are likely failing.

Soft resets vs board/panel work

Fixing client connection issues is strictly a software and configuration job. You should never attempt to open the router casing or solder internal components to fix connection handshakes.

• Soft Resets & Firmware Flashes: Safe, highly effective, and entirely DIY. Clearing the NVRAM via physical button combinations or re-flashing official Asuswrt/Merlin firmware solves over 90% of non-hardware connection bugs.
• Internal Hardware Repairs: Replacing Wi-Fi power amplifiers, flash memory chips, or system board processors requires micro-soldering equipment and specialized diagnostic tools. If hardware testing confirms a damaged radio board, replacing the router entirely or reviewing alternative models on our router reviews hub is much more cost-effective.

Next steps

1. Log into router.asus.com, navigate to LAN > DHCP Server, and verify your IP range is sufficiently wide.
2. Temporarily set Wireless > General > Authentication Method to WPA2-Personal and disable Protected Management Frames.
3. If issues persist, backup your settings and execute a full WPS-button NVRAM hard reset.
4. If new devices fail to connect across multiple distinct networks even after a full router reset, test those devices on an alternative Wi-Fi hotspot to isolate whether the issue belongs to the client device or the ASUS router hardware.