How to Find the Device Causing an IP Conflict

Renewing your IP makes the conflict warning go away — until it comes back. To fix it for good you need to know which device is the other half of the conflict. Every network already keeps the evidence; here's how to read it.

The principle: follow the MAC address

An IP address can be shared by accident; a MAC address (the hardware ID of a network card) almost never is. When two devices fight over one IP, the network briefly learns two different MAC addresses for it. Find the second MAC, look up who made it, and you've found the culprit. Everything below is just a different way to see that IP → MAC mapping.

Method 1: Read the ARP table (fastest)

Your computer keeps a cache of the MAC address behind every local IP it has talked to recently. That cache is the ARP table.

1. Note the conflicting IP. It's in the warning message, or it's the address your device had before it dropped off (ipconfig / ifconfig).
2. Ping it from another device so it's fresh in the cache: ping 192.168.1.50.
3. Show the table:
   • Windows: arp -a
   • macOS: arp -an
   • Linux: ip neigh
4. Compare. If the MAC listed against the IP isn't your device's own MAC (shown in ipconfig /all as “Physical Address”), that's the other device. Run the commands again a minute later; if the MAC flips between two values, you're watching the conflict happen.

Rather than eyeball it, paste the whole output into our IP conflict checker. It flags any IP with two MACs, and looks up each device's manufacturer in one click.

Method 2: Identify the device from its MAC

The first six hex digits of a MAC address (the OUI) identify the manufacturer. Paste the MAC into the MAC address lookup:

• Hewlett Packard, Brother, Canon, Epson — a printer, very often with a manual static IP.
• Espressif, Tuya, Shenzhen … — a smart plug, bulb or other IoT gadget.
• Hikvision, Dahua, Reolink — an IP camera or NVR (often shipped with a fixed address like 192.168.1.64 or 192.168.1.108).
• Synology, QNAP, Raspberry Pi — a NAS or a hobby server someone gave a static IP.
• TP-Link, Netgear, ASUS, Ubiquiti — a second router or access point: suspect a rogue DHCP server.
• No vendor, “locally administered” — a phone or laptop with a private Wi-Fi address.

Method 3: Check the router's client list

Log in to your router (usually 192.168.0.1 or 192.168.1.1) and open the page called Attached devices, DHCP clients, Client list or LAN status. It lists every lease with name, IP and MAC. Two things to look for:

• The conflicting IP appears with a MAC that isn't the device you expect.
• A device you know is on the network with that IP doesn't appear at all — meaning it has a manual static IP the router never handed out. That's your conflict.

Some routers also keep a system log with lines like “IP conflict detected” or “DHCP: duplicate address”, including the offending MAC. Business-grade gear (UniFi, Omada, MikroTik, Cisco) usually reports this directly.

Method 4: Test the address directly (Linux and macOS)

Linux's arping performs Duplicate Address Detection: it asks “who has 192.168.1.50?” from the unspecified address, so the reply can only come from another device.

sudo arping -D -I eth0 -c 3 192.168.1.50

Any reply prints the MAC of the device holding the address. On macOS, brew install arping provides the same tool. For a whole-network view, sudo arp-scan --localnet lists every device with its MAC and vendor — duplicate IPs appear as (DUP: 2).

Method 5: Watch the conflict happen (Wireshark)

If the conflict is intermittent, capture traffic with Wireshark and apply the filter arp.duplicate-address-detected. Wireshark highlights every time two MACs answer for one IP, with timestamps that tell you exactly when the other device came online.

Found it — now fix it

1. Set the other device to obtain its IP automatically (DHCP), or move its static IP outside the router's DHCP pool.
2. If it's a router or access point, disable its DHCP server or switch it to access-point/bridge mode.
3. Create a DHCP reservation on the main router for anything that needs a fixed address.

The full prevention checklist is in how to fix IP address conflicts.

A quick shortcut: if a conflict appears right after you plug something in, that new device is the culprit 90% of the time — especially printers, cameras and second routers, which often ship with a fixed IP.