What causes an IP address conflict on your network, and how to fix it

Short answer: an IP address conflict happens when two devices on your network end up assigned the same local IP address at the same time. Your router or one of the devices will usually throw up a warning, and one or both devices drop off the network until it’s resolved. The usual cause is a device with a manually set static IP that happens to sit inside the range your router hands out automatically.

Why two devices end up with the same address

Every device on your home network needs its own local IP address so your router knows where to send traffic. Most devices get that address automatically from your router’s DHCP server, which keeps track of what it’s already handed out and avoids repeats.

A conflict happens when something sidesteps that bookkeeping. The most common case: someone sets a static IP by hand on a computer, printer, or camera, picking an address like 192.168.1.50 without checking whether the router might also hand that same address to a different device later. DHCP doesn’t know the address is taken, so eventually it assigns .50 to something else, and now two devices claim it at once.

A router reboot or factory reset can cause the same thing in a smaller way. Leases get cleared, and DHCP occasionally hands an address to a different device than before, right as an older device with a leftover static setting is still holding onto it.

What it looks like when it happens

The symptoms vary slightly by device, but the pattern is consistent:

• Windows shows a direct “IP address conflict” notification, naming the address involved.
• One of the two devices suddenly loses its connection while the other keeps working.
• Both devices connect intermittently, dropping and reconnecting as the router keeps reassigning the contested address.
• A device that worked fine yesterday can’t reach the internet today, with no settings changed on that device itself.

If you’re not sure which two devices are actually colliding, your router’s connected-devices list (usually under “DHCP clients” or “Connected Devices” in the admin page) shows every current IP-to-MAC pairing. Cross-referencing an unfamiliar MAC there against a MAC address lookup tells you the manufacturer, which is often enough to identify the device.

How to fix it

1. Open your router’s admin page and find the DHCP client list.
2. Identify the two devices sharing the address. One is usually the device set up with a manual static IP.
3. On that device, either switch it back to automatic (DHCP), or move its static IP outside the range your router hands out automatically. Most routers show that range on the DHCP settings page.
4. If the device needs to stay at a fixed address for something like port forwarding or remote access, set up a DHCP reservation instead of a manual static IP. A reservation tells the router to always hand that device the same address, so DHCP never assigns it to anything else by accident.
5. Restart the devices involved, or disconnect and reconnect them, so they pick up a clean address right away.

Preventing it from happening again

The fix that actually prevents repeat conflicts is moving every fixed-address device from a manual static IP to a router-side DHCP reservation. With a reservation, the router is the one keeping track of which address belongs to which device, so it won’t hand that address to anything else. A manual static IP, by contrast, is invisible to the router until it’s already caused a problem.

If you’re assigning a handful of devices, reserve each one by its device name or MAC address in the router’s DHCP settings rather than typing addresses into each device by hand. It takes a few extra minutes up front and removes the conflict entirely going forward.