An IP address conflict occurs when two devices on your network claim the same local IP address, causing erratic connectivity failures for both devices. This guide explains how to identify conflicting devices using ARP inspection, release and renew DHCP leases, move static IP assignments outside the DHCP pool, configure permanent DHCP reservations, and prevent conflicts from recurring on any router brand.
IP conflicts do not produce consistent errors — affected devices may connect for seconds, then drop, making them appear as Wi-Fi issues. If a device shows inconsistent connectivity with no clear cause, an IP conflict is a primary suspect.
IP conflicts occur when a manually assigned static IP overlaps with the router's DHCP pool, or when two devices are configured with the same static IP. Fix it by running ipconfig /release then ipconfig /renewon affected Windows devices, and checking your router's DHCP lease table for duplicates. For a permanent fix, use DHCP Reservations in your router settings.
Dynamic Host Configuration Protocol — the router's service that automatically assigns IP addresses to connecting devices from a defined pool range.
A router-side binding that tells the DHCP server to always assign a specific IP to a specific device (identified by MAC address).
An IP address manually configured on a device itself, bypassing DHCP assignment. Must be outside the DHCP pool to avoid conflicts.
Address Resolution Protocol cache — a temporary table mapping IP addresses to MAC addresses, used for local network communication. Can become stale and cause ghost conflicts.
The range of IP addresses the DHCP server draws from when assigning leases to clients (e.g., 192.168.1.100–192.168.1.199).
A network event where two devices broadcast conflicting ARP announcements for the same IP address, causing routing confusion for other devices.
| Aspect | DHCP (Dynamic) | Static IP (Device) | DHCP Reservation |
|---|---|---|---|
| Conflict risk | Low (managed by router) | High (if inside pool) | None |
| IP stability | May change on reconnect | Always the same | Always the same |
| Configuration location | Automatic | On each device | In router admin panel |
| Best for | Regular client devices | Legacy systems | Printers, NAS, servers |
| Management effort | None | High | One-time setup |
A device is manually assigned an IP (e.g., 192.168.1.105) that falls within the router DHCP range — the router may assign the same IP to another device.
Two devices are manually configured with the same static IP address, causing immediate and persistent conflict.
After a router reboot, the DHCP server may re-assign a previously used IP to a different device before the original lease expires.
Outdated ARP entries cause devices to route traffic to the wrong MAC address even after the conflict is resolved.
On Windows, open Command Prompt and run: arp -a. This displays all IP-to-MAC address mappings cached on your device. Look for the same IP address mapped to two different MAC addresses — this confirms a conflict. On Linux/Mac, run: arp -n. Note both MAC addresses and use an online MAC address lookup to identify which devices have the conflict.
On the device showing the 'IP Address Conflict' Windows notification: open Command Prompt as Administrator and run 'ipconfig /release' followed by 'ipconfig /renew'. This forces the device to release its current IP and request a new one from the router's DHCP server. On macOS: System Settings → Network → your connection → Advanced → TCP/IP → Renew DHCP Lease. On Android/iOS: forget the Wi-Fi network and reconnect.
Log into your router admin panel. Navigate to LAN → DHCP Server settings. Note the DHCP pool range (e.g., 192.168.1.100 to 192.168.1.199). Any device you want to assign a static IP must use an address outside this pool — for example, 192.168.1.2 through 192.168.1.99 or 192.168.1.200 through 192.168.1.254. Go to each conflicting device and update its static IP configuration accordingly.
Stale ARP cache entries can cause ghost IP conflicts long after the actual conflict is resolved. On Windows: open Command Prompt as Administrator and run 'netsh interface ip delete arpcache'. On Linux: sudo ip -s neigh flush all. On macOS: sudo arp -d -a. After clearing, the devices will re-discover correct IP-to-MAC mappings during the next network activity.
Log into your router admin panel and navigate to DHCP Reservations (or Address Reservation / Static DHCP — the name varies by brand). For each device that needs a fixed IP (printers, NAS, smart TVs, game consoles), add a reservation binding the device's MAC address to a specific IP. The router will always assign that IP via DHCP rather than from the dynamic pool, eliminating conflicts while maintaining proper pool management.
Contact your ISP only if you suspect the conflict involves the WAN-side IP address (your public IP). ISP DHCP conflicts in the WAN segment are managed by the ISP and cannot be resolved from your side. For LAN-side conflicts, the fixes above apply universally.
An IP address conflict occurs when two devices on the same local network are assigned or use the same IP address simultaneously. Since IP communication requires unique addressing, both devices experience network failures — packets sent to that IP are delivered to whichever device responds first, causing erratic connectivity for both. Conflicts happen when: a device is manually configured with a static IP that the DHCP server later also assigns dynamically, two devices are configured with the same static IP, or a DHCP lease persists after a router reboot while a device also holds a manual assignment for the same IP.
A static IP is manually configured directly on the device (in its network settings) — the device always uses that IP regardless of what the DHCP server does. A DHCP Reservation is configured in the router — it tells the DHCP server to always assign a specific IP to a specific MAC address whenever that device requests a lease. DHCP Reservation is almost always better: it centralizes IP management, prevents conflicts with the DHCP pool, and automatically handles device reconnections without any device-side configuration.
On Windows, you will see a notification 'There is an IP address conflict with another system on the network' and the conflicting device may lose internet access intermittently. On macOS, a similar alert appears saying another device is using your IP address. On Linux, you may see ARP conflict messages in system logs (dmesg | grep -i arp). Affected devices typically experience erratic connectivity — working for a few seconds then dropping — rather than complete failure.
Primarily, an IP conflict only directly affects the two devices sharing the same IP. However, secondary effects can occur: ARP confusion can cause intermittent routing failures for devices in the same subnet, broadcast traffic from conflicting ARP announcements increases slightly, and in rare cases with poorly implemented network stacks, the ARP storm from conflict resolution can cause brief network-wide slowdowns. Resolving the conflict quickly prevents these secondary effects.
The DHCP lease pool is the range of IP addresses the router's DHCP server can assign to clients. For example, a pool of 192.168.1.100 to 192.168.1.199 provides 100 addresses. Size the pool larger than your expected connected device count — typically 2–5x larger for home networks. Addresses outside the pool (e.g., 192.168.1.2 to 192.168.1.99) are safe to use for static IPs without conflict risk. Avoid overlapping any static IP assignments with the DHCP pool range.