How to Fix WiFi IP Address Conflicts on Your Network

An IP address conflict happens when two devices on the same network are assigned the same private IP address. The result: one or both devices lose internet access, even though WiFi signal strength looks fine. Windows flags it with “Windows has detected an IP address conflict.” Macs show a yellow warning icon in Network settings. Android simply fails to connect.

The good news is that most conflicts are caused by simple DHCP lease problems and resolve in under two minutes. This guide walks through every fix — for each major operating system — and then covers the router-level changes that prevent conflicts from recurring.

Why IP Address Conflicts Happen

Every device on your network needs a unique IP address. Your router’s DHCP server normally handles this automatically, handing out addresses from a pool (typically something like 192.168.1.100–192.168.1.200) and tracking which device holds each lease. Conflicts arise when that system breaks down.

Stale DHCP Leases

When a device disconnects without formally releasing its IP, the router may eventually hand that same address to a new device — and then the original device comes back still holding it. Mobile devices that frequently join and leave the network are the most common culprit in 2026.

Static IP Overlapping the DHCP Pool

If you manually assigned a static IP to a printer, NAS, or smart home hub, and that address falls inside the router’s DHCP range, the router can hand it to another device as a dynamic lease. The two devices then fight over the same address.

Rogue DHCP Server

If someone accidentally connects a second router to your network in non-bridge mode, it starts its own DHCP server. Two DHCP servers handing out addresses from different (or overlapping) pools creates widespread conflicts across multiple devices.

VPN and Virtual Network Adapters

Some VPN clients and virtualization software (VMware, VirtualBox) create virtual network adapters that don’t always release their IP correctly, causing conflicts with physical devices on the same subnet.

Fix 1: Release and Renew on Windows

This is the fastest fix for Windows PCs and usually resolves the conflict immediately.

1. Press Windows + R, type cmd, and press Ctrl + Shift + Enter to open Command Prompt as administrator.
2. Type the following and press Enter: ipconfig /release
3. Wait a moment, then type: ipconfig /renew
4. Windows will request a fresh IP address from the DHCP server. The conflict should clear immediately.

If the conflict returns after a short time, the root cause is on the router side — skip to the router fixes below.

Fix 2: Renew DHCP Lease on Mac

macOS makes this straightforward through System Settings.

1. Open System Settings › Network.
2. Select your WiFi connection and click Details…
3. Go to the TCP/IP tab.
4. Click Renew DHCP Lease and then OK.

Alternatively, turning WiFi off and back on (via the menu bar icon) forces a new DHCP request and achieves the same result. If the yellow warning icon in Network settings persists, restart the router and try again.

Fix 3: Forget and Reconnect on Android

Android doesn’t expose an explicit “renew DHCP” button, so the quickest path is to forget the network and reconnect.

1. Go to Settings › Network & Internet › Internet (path varies by manufacturer).
2. Tap the gear icon next to your WiFi network.
3. Tap Forget.
4. Reconnect to the network by tapping it and entering your password.

When Android reconnects, it requests a brand-new DHCP lease, and the router assigns a fresh address from its pool.

Fix 4: iPhone and iPad (iOS)

iOS handles this similarly to Android.

1. Go to Settings › Wi-Fi.
2. Tap the (i) icon next to your network name.
3. Tap Forget This Network and confirm.
4. Reconnect to obtain a fresh DHCP lease.

Alternatively, toggle Airplane Mode on for 10 seconds and then off. This forces all radios to drop their connections and re-establish fresh leases when they reconnect.

Fix 5: Restart Your Router

When multiple devices on the same network are conflicting, or when individual device fixes don’t stick, restart the router. A reboot clears the DHCP lease table and forces every connected device to request a fresh address. Unplug the router for 30 seconds, plug it back in, wait 60 seconds for it to fully boot, and then reconnect your devices. This resolves the large majority of conflicts on home networks.

Fix 6: Separate Static IPs From the DHCP Pool

If you have devices with manually-assigned static IPs (printers, NAS drives, smart home hubs), make sure those addresses fall outside the router’s DHCP range. Here’s how to check and fix this:

1. Log in to your router admin panel — usually 192.168.1.1 or 192.168.0.1 in a browser.
2. Find the DHCP settings (often under LAN › DHCP Server or Advanced › Network).
3. Note the DHCP start and end addresses. For example: 192.168.1.100–192.168.1.200.
4. Change any static IP assignments to addresses outside this range — for example, 192.168.1.2–192.168.1.99 for static devices, leaving 192.168.1.100–192.168.1.200 for dynamic leases.

Fix 7: Use DHCP Reservations Instead of Static IPs

The cleanest long-term solution is to replace manual static IP assignments with DHCP reservations (also called “address reservation” or “static DHCP” depending on your router brand). A DHCP reservation tells the router to always assign the same IP to a specific device based on its MAC address — you get the predictability of a static IP without any risk of conflicts, because the router tracks everything.

To set one up: in your router’s admin panel, go to DHCP settings and look for “Address Reservation” or “Static Leases.” Add the device’s MAC address (found in the device’s network settings or the router’s connected-devices list) and the IP you want it to always receive.

How to Identify the Conflicting Device

If your router’s admin panel shows a list of connected devices, look for two entries with the same IP address. The MAC addresses will be different, which tells you exactly which two devices are fighting. On Windows, running arp -a in Command Prompt shows a table of IP-to-MAC mappings for your local network — a duplicated IP in that table confirms the conflict and identifies both devices.

When to Check for a Rogue DHCP Server

If conflicts are widespread — affecting multiple devices at random — and restarting your router doesn’t help, there may be a second DHCP server on your network. Check all the physical devices plugged into your network: consumer routers should be set to bridge or access point mode if they’re not the primary router. Any device handing out DHCP leases will show up as a gateway address in ipconfig /all (Windows) or netstat -rn (Mac/Linux).

Quick Summary

Most IP address conflicts on home WiFi are resolved in order:

1. Restart your router — clears stale leases for everyone.
2. Release/renew on Windows or forget and reconnect on mobile — gets the affected device a new lease.
3. Move static IPs outside the DHCP pool — prevents the structural conflict that keeps recurring.
4. Switch to DHCP reservations for devices that need a fixed address.

For more on keeping your home network healthy, see our guides on fixing WiFi DHCP errors and how home network speeds actually work.