An IP address conflict happens when two devices hold the same IPv4 address on one subnet, so one or both lose network access. Fix it by releasing and renewing the DHCP lease on the affected client, rebooting the router, and reserving addresses that were manually assigned inside the DHCP pool.
Symptoms
- Windows or macOS shows a duplicate IP warning shortly after connecting to the network.
- One device loses internet access while other devices on the same LAN keep working normally.
- Intermittent drops on a printer, NAS, or VoIP phone that previously had a stable connection.
- ARP tables on the router or switch show the same IP mapped to two different MAC addresses.
- Ping to the local gateway succeeds, then fails within seconds as ARP entries flip.
Common Causes
Static IP inside the DHCP scope
An admin hard-coded an address on a printer or server that falls within the router's DHCP range, so the router later hands the same address to a laptop.
Stale or overlapping DHCP leases
Two DHCP servers on the same broadcast domain, or a router that lost its lease database after a reboot, can hand identical addresses to different clients.
Device waking from sleep
A laptop returning from hibernation may keep its old lease while the DHCP server has already reassigned that address to another client during the idle window.
VPN or bridged interfaces
A tunnel that pushes routes into your local subnet, or a virtual adapter bridged to the LAN, can inject an address that clashes with a physical device.
Cloned virtual machine or image
VMs deployed from the same template sometimes ship with a fixed IP in the guest OS, so every clone fights for the same address the moment it boots.
Step-by-Step Fix
- Identify the two devices holding the same IP
On the router or a managed switch, open the ARP table and look for one IPv4 address mapped to two MAC addresses. Match each MAC to a device via DHCP client list or vendor OUI. Knowing which two endpoints collide tells you whether the fix belongs on a client, a printer, or a server. - Release and renew the lease on the affected client
On Windows, open an elevated Command Prompt and run ipconfig /release followed by ipconfig /renew. On macOS, go to System Settings, Network, Details, TCP/IP, and click Renew DHCP Lease. On Linux, use sudo dhclient -r then sudo dhclient. The client should pull a fresh, unused address. - Reboot the router to rebuild the lease table
If both devices insist on the same address after a renew, power-cycle the router for 30 seconds so it flushes its lease cache. When it comes back, reconnect clients one at a time and confirm each receives a distinct address before adding the next. - Move static IPs outside the DHCP pool
Log in to the router and note the DHCP range, for example 192.168.1.100 to 192.168.1.200. Any device with a hard-coded address must sit outside that range, such as 192.168.1.10 for a printer. This single change prevents the majority of recurring conflicts. - Create DHCP reservations for critical devices
For printers, NAS units, cameras, and servers, bind the MAC address to a fixed IP inside the router's DHCP reservations. The device still boots with DHCP enabled, but always receives the same address, and the server will never hand that address to anyone else. - Check for a second DHCP server on the LAN
Run a DHCP discovery from a test client, for example nmap --script broadcast-dhcp-discover, and confirm only one server answers. Rogue servers often come from a spare router plugged in as a switch, or a hypervisor with an unwanted virtual DHCP service enabled. - Inspect VPN, virtual adapters, and VM clones
Disable any VPN that pushes local routes and check virtual switches for bridged mode conflicts. For cloned VMs, set the guest network to DHCP or assign each clone a unique static IP. Re-test connectivity after each change so you know which layer resolved the collision.
Common IP conflict scenarios and the correct fix
| Scenario | Likely cause | Correct fix |
|---|---|---|
| Duplicate IP warning on one PC only | Stale lease after sleep or reboot | Release and renew the lease on that client |
| Printer drops offline daily | Static IP inside DHCP pool | Move the static address outside the pool or add a reservation |
| Two clients flip in and out of network | Rogue second DHCP server | Locate and disable the extra DHCP service |
| VMs fight for one address | Cloned template with fixed IP | Switch guests to DHCP or assign unique static IPs |
| Conflict appears only when VPN connects | Overlapping remote subnet | Change LAN subnet or adjust VPN split-tunnel routes |
Prevention
- Document a clear IP plan: DHCP pool, static range, and reservations, and keep it with the network diagram.
- Use DHCP reservations instead of client-side static IPs whenever the device supports it.
- Disable unused DHCP services on secondary routers, access points, and hypervisors.
- Shorten aggressive lease times only when needed; very short leases increase churn and conflict risk.
FAQ
Can an IP address conflict damage a device or the network?
No, a conflict does not harm hardware. It only blocks the affected device from communicating on the subnet because the router's ARP table cannot decide which MAC address owns the IP. Once the duplicate is removed and ARP entries refresh, normal traffic resumes without any lasting effect on the router, switch, or client.
Why does the same conflict return every few days?
Recurring conflicts almost always point to a static IP sitting inside the DHCP pool, or to a second DHCP server on the LAN. The router keeps handing out an address that another device already claims. Move the static IP outside the pool, or convert it to a DHCP reservation, and the pattern stops.
Should I use static IPs or DHCP reservations for servers and printers?
DHCP reservations are usually the better choice. The device keeps a predictable address, but all IP management stays centralized on the router or DHCP server. If that server later changes subnets or ranges, you update one place instead of touching every device, which sharply reduces the risk of future conflicts.
Need help auditing your DHCP setup and eliminating recurring IP conflicts? Contact our network support team for a review.