Finding and fixing an IP address conflict

Monday morning, the receptionist’s PC shows “Windows has detected an IP address conflict” and the network icon grows a yellow triangle. By lunchtime the label printer has stopped answering too. Conflicts like this look random, but they almost always have one of three boring causes, and once you know which, the fix takes minutes and stays fixed.

This guide is written for someone looking after their own home or small-office network. We’ll confirm the conflict, find the other device, fix the immediate problem, then remove the cause.

What an IP conflict actually is

Every device on a LAN needs a unique IP address. Your router’s DHCP server normally hands them out from a pool, say 192.168.1.100 to 192.168.1.199, and remembers who has which. A conflict happens when two devices both believe they own the same address. The usual culprits:

1. A static address inside the DHCP pool. Someone set a printer to 192.168.1.120 by hand, then DHCP gave .120 to a laptop that was off at the time.
2. Two DHCP servers. A second router or a mesh node plugged in “as a router” instead of in access-point mode starts handing out its own addresses on the same wire.
3. A stale lease after a restore. A router reset or firmware update forgets its lease table while devices keep their old addresses.

Rarer causes include a cloned virtual machine carrying the same static config as its parent.

Step 1: Confirm the conflict and note the address

On the affected Windows PC:

ipconfig /all

Look for the IPv4 Address. If it says (Duplicate) or the address is in the 169.254.x.x range, Windows detected the clash and gave up. Note the address it was trying to use and its own Physical Address (MAC).

On macOS, the warning reads “Another device on the network is using your computer’s IP address”; check System Settings → Network → Details → TCP/IP.

Step 2: Find who else holds that address

From a different computer on the same network, ping the address and read the ARP cache:

ping 192.168.1.120
arp -a | findstr 192.168.1.120

If the MAC shown is not the MAC of the PC with the warning, you’ve found the other party. Look up the first half of that MAC with any vendor lookup to get a manufacturer; “Brother” or “Zebra” points straight at a printer.

On Linux, arping can detect duplicates directly:

sudo arping -D -I eth0 -c 3 192.168.1.120

Any reply means someone is already using it.

Step 3: Map the whole range with Angry IP Scanner

When conflicts keep coming back, you want a picture of every address in use, not just one. Angry IP Scanner is a free, open-source scanner that runs on Windows, macOS and Linux, which makes it handy on whatever laptop you have with you.

Before you scan: Scan your own network or one you manage.

1. Get it from angryip.org (see /where-to-get for how to verify the file) and open it.
2. Set the range to your whole subnet, for example 192.168.1.0 to 192.168.1.255.
3. Under Tools → Fetchers, add MAC Address and MAC Vendor so each row shows the hardware behind it.
4. Click Start. On a /24 it finishes in seconds to a minute.
5. Sort by IP and look for addresses outside your DHCP pool that are alive. Each one should be a device you deliberately gave a static address. Any you don’t recognize is a candidate for the conflict.
6. Save the results with Scan → Export to CSV; you’ll use it in Step 5.

If you prefer the Windows-only Advanced IP Scanner, it shows the same IP-MAC-vendor columns. Our comparison of the two covers which suits you, and the IP scanners category lists more options.

Step 4: Check for a second DHCP server

On the PC with the warning, ipconfig /all also shows DHCP Server. It should be your main router’s address. If it’s something else, such as 192.168.0.1 when your router is 192.168.1.1, a second device is handing out leases.

Find it by its IP in the scan results, then log into it and switch it to Access Point or Bridge mode, or disable its DHCP server. Mesh kits and ISP-supplied routers added “just for Wi-Fi” are the usual offenders.

Step 5: Fix it now, then fix the cause

Immediate fix on the Windows PC:

ipconfig /release
ipconfig /renew

The PC gets a fresh address and the warning clears. In PowerShell, Get-NetIPAddress -AddressFamily IPv4 confirms the new address.

Permanent fix, in the router admin page:

1. Open the DHCP settings and note the pool range.
2. Move every static device outside the pool. If the pool is .100–.199, give printers and NAS boxes addresses in .10–.49, set on the device itself.
3. Better still, set those devices back to DHCP and create a DHCP reservation (sometimes called Address Reservation or Static Lease) for each MAC. The router then always hands that device the same address and never gives it to anyone else.
4. Record each reservation in your inventory; our guide to building a device inventory spreadsheet has a column for exactly this.
5. Reboot the router once so leases are rebuilt cleanly.

Common mistakes

• Fixing the PC that complained. The machine that shows the warning is often the innocent party. Find and correct the device with the hand-set address.
• Shrinking the pool without checking reservations. Some routers silently drop reservations that fall outside a new pool.
• Ignoring the second router. Release/renew will “fix” things for a day and then the rogue DHCP server hands out a duplicate again.
• Using .1 or .254 for a static device. Those are commonly the gateway; keep them clear.
• Forgetting printers’ own menus. Many printers have a static IP set on the front panel that survives resets of everything else.

If a device you can’t place turns out to be holding the address, our walkthrough on identifying an unknown device picks up from there, and Discovery & Inventory tools can keep an eye on address usage over time.