Resolving DHCP Starvation on TPLink Archer AX73 Router

Introduction

A home network that runs smoothly is essential for video calls, streaming, gaming, and the everyday tasks that keep a household connected. When the TPLink Archer AX73 router stops assigning IP addresses to devices, the network stops functioning – a problem commonly referred to as DHCP starvation. This guide walks you through the causes, symptoms, and step‑by‑step solutions so you can restore reliable connectivity to every device in your home.

Understanding DHCP Starvation

The Dynamic Host Configuration Protocol (DHCP) is a network service that hands out IP addresses automatically. Each device that connects to the router requests an address, and the DHCP server replies with an available IP from its pool. DHCP starvation occurs when the server cannot satisfy these requests. The result is a cascade of network errors: devices cannot reach the internet, local services fail, and the router becomes the bottleneck.

Key Reasons for Starvation

1. Exhausted IP Pool – The pool is too small for the number of devices on the network.
2. Overly Short Lease Time – Devices release addresses too quickly, creating a rapid churn that the server cannot keep up with.
3. MAC‑Based Filtering – An overly strict MAC filter or a blocked address can prevent legitimate devices from receiving an address.
4. Firmware Bugs – Out‑of‑date firmware can contain defects that limit DHCP performance.
5. Network Misconfiguration – Conflicting static IPs or subnet settings can block the DHCP server from allocating addresses.

Knowing which of these factors applies to your situation is the first step toward a permanent fix.

Symptoms of DHCP Starvation on the Archer AX73

• Devices repeatedly show “No Internet” or “IP address not obtained.”
• The router’s status page displays a high number of “DHCP client request failures.”
• New devices cannot connect even though older devices work fine.
• The DHCP server’s lease table fills up quickly, leaving little free IPs.
• Intermittent connectivity where a device works for a short time and then loses access.

If you notice one or more of these symptoms, it is time to investigate the DHCP settings.

Preparation Checklist

Before you start adjusting settings, gather the following information:

Make sure you have physical or remote access to the router’s web interface. The default login credentials are usually:

• Username: admin
• Password: admin

If you have changed them, use your current credentials.

Step‑by‑Step Guide to Resolve DHCP Starvation

1. Log into the Archer AX73 Web Interface

1. Open a web browser on a computer connected to the router (wireless or wired).
2. Type the router’s IP address in the address bar. By default it is 192.168.0.1 or 192.168.1.1.
3. Enter your username and password.

You should now see the main dashboard.

2. Inspect Current DHCP Settings

Navigate to Network > LAN > DHCP Server.
Here you will find:

• IP Address Range – the start and end addresses.
• Lease Time – the duration for each lease.
• DHCP Client List – devices currently holding addresses.

Take note of these values and compare them with your preparation checklist.

3. Expand the DHCP IP Pool

If the router’s IP pool is small relative to the number of devices, increase its size:

1. Click Edit next to the DHCP Server.
2. Adjust the start address to a lower number (e.g., 192.168.0.2 → 192.168.0.10).
3. Adjust the end address to a higher number (e.g., 192.168.0.254 → 192.168.0.200).

Ensure that the new range still falls within the router’s subnet.
After making changes, click Apply. The router will restart the DHCP service, releasing any stale leases.

4. Extend the Lease Time

Short lease times cause devices to renew IP addresses frequently, which can overload the DHCP server. To reduce churn:

1. In the same DHCP Server edit screen, locate the Lease Time field.
2. Change it from a short value (e.g., 1 hour) to a longer one (e.g., 12 hours or 24 hours).
3. Click Apply.

This change is harmless for most home networks and will reduce the number of DHCP requests over time.

5. Verify and Adjust MAC Filtering

If the router is set to block unknown MAC addresses:

1. Go to Advanced > MAC Filtering.
2. If MAC Filtering is enabled, either turn it off or add the MAC addresses of all devices that must receive IPs.
3. Save changes and reboot the router.

Unnecessary filtering is a common source of DHCP starvation, especially when new devices are added.

6. Update the Router Firmware

Out‑of‑date firmware can contain bugs that affect DHCP performance:

1. Go to System > Firmware Update.
2. If an update is available, download it.
3. Click Update Now and wait until the router finishes.
4. The router will reboot automatically.

After the update, repeat steps 2–5 to confirm that the new firmware is functioning correctly.

7. Re‑associate All Devices

Once the DHCP server is reconfigured:

1. Disconnect each device from the network.
2. Reconnect them one at a time.
3. Verify that each device obtains a new IP within the adjusted range.

If any device still shows “No IP address,” check its network adapter settings to ensure it is set to obtain an address automatically.

8. Add Static IPs for Critical Devices

For devices that must always be reachable (e.g., a NAS, a printer, or a server):

1. Find the device’s MAC address.
2. In the DHCP Server edit screen, click Add under Static Lease.
3. Enter the MAC address, desired IP (within the pool), and a friendly name.
4. Save and reboot the router.

Static leases guarantee that these devices receive the same IP each time, reducing potential conflicts.

9. Monitor DHCP Logs

To confirm that starvation has been resolved:

1. Go to System > Log.
2. Filter for DHCP events.
3. Look for “assigned” entries.
4. Ensure that there are no repeated “failed” or “timeout” events.

If the log shows a clean distribution of assignments, your DHCP server is operating correctly.

Advanced Troubleshooting

If the above steps do not resolve the problem, consider the following advanced checks.

Network Segmentation

If you have multiple VLANs or sub‑nets, each may have its own DHCP scope. Verify that the scope for the VLAN containing your devices is large enough.

Rogue DHCP Servers

Sometimes a secondary device (e.g., a PC set up as a DHCP server) can interfere:

1. Check all devices for DHCP services.
2. Disable any non‑router DHCP servers.
3. Reboot the network.

Hardware Reset

As a last resort, perform a factory reset:

1. Locate the reset button on the back of the router.
2. Press and hold for 10 seconds until the LED blinks.
3. Reconfigure the router from scratch, ensuring the DHCP settings are appropriate.

Factory reset should only be used when all other troubleshooting fails, as you will lose all custom settings.

Maintaining a Healthy DHCP Environment

Once the starvation issue is fixed, keep your network stable with these practices:

• Regular Firmware Checks: Update at least once every few months.
• Monitor Device Count: Add new devices gradually to avoid sudden pool exhaustion.
• Use a Separate Guest Network: Keep guest devices off the main DHCP pool to reduce churn.
• Backup Settings: Save a copy of your router configuration so you can restore it quickly.

By staying proactive, you prevent the next wave of DHCP starvation.

Final Thoughts

DHCP starvation on the TPLink Archer AX73 can be frustrating, but it is largely a configuration issue. By expanding the IP pool, extending lease times, disabling unnecessary MAC filtering, keeping firmware up to date, and monitoring logs, you can restore reliable connectivity to every device in your home network. Follow the steps above, and you’ll enjoy seamless internet access for video conferences, gaming sessions, and smart‑home devices alike.

Happy networking!