What a Conflict Actually Is
Every device on your network needs a unique IP address, the same way every house on a street needs a unique number. When two devices end up with the same address, the network cannot tell them apart — replies meant for one arrive at the other, so both suffer dropped connections, stalls, and "connected but no internet" moments. Crucially, this usually affects only the conflicting devices; the rest of the house is unaffected, which is the clue that distinguishes a conflict from a router or ISP problem.
The Symptoms
| What you notice | Why a conflict causes it |
|---|---|
| Windows pop-up: "There is an IP address conflict" | Windows detected another device announcing the same address |
| One device drops out intermittently while others are fine | The two devices take turns "winning" the address |
| Device shows a 169.254.x.x address (APIPA) | It gave up getting a valid address and self-assigned one |
| A printer or NAS "disappears" then comes back | A static-IP device colliding with a DHCP-assigned one |
| Conflict appears after adding a second router | Two DHCP servers handing out overlapping addresses |
Step 1: Confirm the Address Is Duplicated
First, read the affected device's current address, then test whether the address still responds after you take that device offline.
# See the device's own IP
ipconfig # Windows (look at IPv4 Address)
ipconfig getifaddr en0 # macOS Wi-Fi
ip addr # Linux
# Note the address, e.g. 192.168.1.50. Now power that device OFF,
# then from another device on the network, ping that address:
ping 192.168.1.50
# If it STILL replies with the device off -> another device owns it too = conflict.
# If it goes unreachable -> no conflict on that address.A self-assigned 169.254.x.x (or "self-assigned IP" on macOS) is itself strong evidence: the device tried to claim an address, found it contested or got no DHCP answer, and fell back to a useless link-local address.
Step 2: Map the Address to Devices
To see which two devices are fighting, check the neighbour/ARP table and the router's client list.
# See which MAC address currently answers for an IP
arp -a # Windows / macOS / Linux — find the IP, note its MAC
# Then in the router admin panel (192.168.1.1):
# open the DHCP client list / connected devices and look for
# the same IP listed twice, or one IP with an unexpected device name.Match the MAC address from arp -a against the router's device list to identify the second claimant. A MAC address is unique per network adapter, so it tells you exactly which physical device is involved.
Step 3: Fix It Now
- Release and renew the affected device's address so the router hands it a fresh, unused one:
# Windows ipconfig /release && ipconfig /renew # macOS: System Settings > Network > Details > TCP/IP > Renew DHCP Lease # Linux sudo dhclient -r && sudo dhclient - If a device has a manual static IP, change it to an address outside the router's DHCP range, or better, remove the static setting and use a reservation instead (Step 4).
- Reboot the router if two devices remain stuck on the same address — this clears the lease table and re-assigns cleanly.
Step 4: Prevent It Permanently
Conflicts almost always come from mixing manual static IPs with automatic DHCP assignment. The clean fix is to never set static IPs on the devices themselves. Instead, use a DHCP reservation in the router: you tell the router "always give this MAC address this IP." The address is then permanent and the router knows about it, so it will never hand the same address to anyone else. This gives you the predictability of a static IP without the collision risk.
Two further safeguards: make sure only one DHCP server is running on the network — if you added a second router, put it in access-point/bridge mode so it stops handing out addresses. And size the DHCP pool to your device count so it never runs dry.
The Second-Router Trap
The most common cause of sudden conflicts across a whole network is a second router added as a "range extender" while still in router mode. It runs its own DHCP server on the same subnet, so two servers hand out overlapping addresses and chaos follows. This is closely related to double NAT; the fix is the same — switch the secondary unit to access-point mode so a single device governs addressing.
Frequently Asked Questions
What causes an IP address conflict?
It happens when two devices end up with the same IP address on one network. The usual triggers are a static IP set on a device that falls inside the router's DHCP pool, two DHCP servers running at once (often a second router not in bridge mode), or a device waking from sleep and reclaiming an address the router has since handed to another device.
How do I know if I have an IP conflict or a different problem?
The tell-tale sign is intermittent connectivity that affects specific devices, often with an on-screen warning about a duplicate address on Windows, or a self-assigned 169.254.x.x address. If every device is affected equally and there is no duplicate-address warning, the problem is more likely the router, modem, or ISP rather than a conflict.
How do I permanently stop IP conflicts?
Let the router's DHCP assign every address, and use DHCP reservations to pin specific devices to fixed addresses instead of setting static IPs manually on the devices. A reservation lives in the router, so it can never collide with the DHCP pool. Also make sure only one device on the network is running a DHCP server.
Can an IP conflict slow down the whole network?
Not usually. A conflict typically degrades only the two devices sharing the address; the rest of the network keeps working normally. The exception is when a rogue second DHCP server is handing out bad configuration to many devices at once — then multiple devices can lose connectivity, which looks like a network-wide slowdown but is really many small conflicts.