What Happens When Two Devices Share the Same IP Address?

Two devices with one IP confuse ARP caches and cause intermittent drops. Learn the causes, how to find both devices, fixes and prevention.

Jul 30, 2025 - 15:30
Nov 9, 2026 - 00:40
 0  188
What Happens When Two Devices Share the Same IP Address?

When two devices share the same IP address on one network, other hosts and the router keep changing which MAC address they map to that IP in their ARP caches. Traffic reaches one device, then the other, so both see dropped connections, timeouts and intermittent access. Most operating systems detect the clash and warn you, and some stop using the address.

This article explains what happens on the wire, how to find both devices, and how to stop conflicts coming back. It belongs to our networking fundamentals series, which starts with the OSI model and why it still matters. IP conflicts sit right at the boundary between Layer 2 and Layer 3, so that context helps.

Key takeaways

  • An IP conflict breaks the one-to-one link between an IP address and a MAC address that ARP depends on.
  • Symptoms are intermittent: one device works for a while, then the other, and both may drop sessions.
  • The usual causes are a static address inside the DHCP pool, two DHCP servers, cloned virtual machines and devices returning from sleep with an old lease.
  • IPv4 hosts detect conflicts with ARP probes (RFC 5227). IPv6 hosts use Duplicate Address Detection (RFC 4862) before using an address.
  • Prevention is mostly process: DHCP reservations, static ranges outside the pool, one authoritative DHCP server and an IPAM record.

What happens on the network

ARP gets two answers

On an IPv4 LAN, a host that wants to reach 192.168.1.50 broadcasts an ARP request asking who has that address. Normally one host answers with its MAC address, and the sender caches the mapping. The full process is described in how ARP maps IP addresses to MAC addresses.

With a conflict, two hosts answer. The sender keeps whichever reply it processed last, and that can change on every refresh. The router does the same. Return traffic for an existing TCP session may suddenly go to the wrong machine, which does not recognize the session and sends a reset or ignores it. The user sees a frozen page, a dropped SSH session or a failed file copy.

Why it looks random

ARP cache entries expire after a timeout that differs between operating systems, and a host also updates its cache when it sees a gratuitous ARP. So the "winner" changes when caches expire, when one device reboots, or when one sends a gratuitous ARP after waking up. That is why conflicts are often reported as "the Wi-Fi drops every few minutes" instead of as an addressing problem.

What the operating system does

SystemTypical behavior on conflict
WindowsShows a notification that another device on the network is using the computer's IP address and logs a TCP/IP event in the System log. A host that detects the conflict at startup may not bring the address up.
macOSShows an alert that another device is using the IP address.
Linux with NetworkManagerCan run ARP-based duplicate detection before configuring an IPv4 address, controlled by the ipv4.dad-timeout connection property.
IPv6 hostsRun Duplicate Address Detection. If a duplicate is found, the address is marked duplicated and is not used.
Printers, cameras, IoT devicesOften no warning at all. They simply become unreachable part of the time.

Common causes

Static address inside the DHCP pool

This is the most frequent cause. Someone gives a printer 192.168.1.100 by hand, and the DHCP server, which does not know about it, later leases the same address to a laptop. Many DHCP servers ping or ARP-check an address before offering it, which reduces but does not remove this risk, because a device that is switched off at the time will not answer.

Two DHCP servers

A consumer router plugged into an office network, or a test DHCP service left running on a VM, can hand out addresses from an overlapping range. Clients get leases from whichever server answers first. Switch features such as DHCP snooping exist to block DHCP offers from untrusted ports.

Cloned virtual machines and images

Cloning a VM that has a static IP, or a template with a fixed address in its network configuration, produces two machines with the same address. Cloning can also duplicate MAC addresses or machine IDs that some DHCP clients use to identify themselves, which leads to two hosts receiving the same lease.

Stale leases after sleep or roaming

A laptop that sleeps for days may wake up and briefly use an old address that the DHCP server has since given to someone else. Well-behaved clients send a DHCPREQUEST to confirm the lease and stop using it if the server refuses, but buggy or misconfigured clients may not.

Manual errors in server and network configs

Typing the same address into two servers, two Kubernetes node configs or two load balancer virtual IPs causes the same symptoms. High-availability setups that use a floating virtual IP, such as VRRP, can also misbehave if both nodes believe they are active.

How to find the two devices

The goal is to get both MAC addresses, then trace each MAC to a switch port or Wi-Fi association. Commands below are read-only and safe to run on your own network.

Check the ARP or neighbor table

# Linux: show neighbor (ARP) entries
ip neigh show

# Windows and macOS
arp -a

Run it a few times. If the MAC address for the suspect IP changes between runs, you have found a conflict.

Ask the address directly with arping

# Linux (iputils arping): -D runs duplicate address detection mode
sudo arping -D -I eth0 -c 3 192.168.1.50
# A reply means some host already uses this address

Without -D, arping prints every reply with the responder's MAC, so two different MACs in the output confirm two devices.

Check the DHCP server and switch

  • Look up the IP in the DHCP lease table to find which MAC it was leased to.
  • Check the switch MAC address table to find the port for each MAC. On many managed switches this is a show mac address-table style command; the exact syntax depends on the vendor.
  • Look up the first half of each MAC (the OUI) in the IEEE registry to identify the manufacturer, which often tells you whether it is a printer, a phone or a VM.

Check system logs

On Windows, the System event log records the conflict along with the other device's MAC. On Linux, NetworkManager logs duplicate detection results in the journal (journalctl -u NetworkManager).

How to fix the conflict

  1. Decide which device keeps the address. Usually the server, printer or network device that other systems are configured to reach.
  2. Move the other device. Set it back to DHCP, or give it a different static address outside the DHCP pool.
  3. Renew the lease on DHCP clients. On Windows: ipconfig /release then ipconfig /renew. On Linux with NetworkManager: nmcli connection down "name" then nmcli connection up "name".
  4. Clear stale ARP entries on the router or affected hosts if traffic still goes to the wrong MAC. On Linux: sudo ip neigh flush to 192.168.1.50.
  5. Find the root cause so it does not come back: a static address in the pool, a rogue DHCP server or a cloned image.

How to prevent IP conflicts

ControlWhat it preventsNotes
DHCP reservationsStatic addresses colliding with leasesBind important devices to a MAC in the DHCP server instead of configuring them by hand
Static range outside the poolManual addresses being leased againFor example .1 to .49 static, .50 to .250 dynamic
One authoritative DHCP service per subnetOverlapping leases from two serversUse failover between two servers rather than two independent ones
DHCP snooping on switchesRogue DHCP serversMark only uplinks to the real server as trusted
IPAM tool or version-controlled address planDuplicate manual allocationsOpen-source options include NetBox and phpIPAM
Generalizing VM templatesClones with duplicate static IPs or IDsUse cloud-init or Sysprep so each clone gets its own identity
Cloud-managed addressingMost conflicts inside a VPCCloud providers assign private IPs to interfaces and do not let two interfaces in a VPC hold the same one

Good subnet planning also helps, because each range has a clear owner. See how subnetting improves network efficiency and security and the consequences of poor IP address management. If you run DHCP yourself on Linux, configuring DNS and DHCP on RHEL 10 shows how to set up reservations with Kea.

IPv6 and duplicate addresses

IPv6 builds conflict detection into address setup. Before a host uses a new unicast address, it sends Neighbor Solicitation messages for it as a tentative address. If another node answers, the address fails Duplicate Address Detection and is not assigned. Conflicts are rarer in IPv6 because the address space per subnet is huge and addresses are often generated from random interface identifiers, but manual static configuration can still collide. The protocol background is in what IPv6 is and why it is replacing IPv4 in the cloud.

Is an IP conflict a security issue?

Usually it is a configuration mistake. The same mechanism, a second device answering ARP for an address it does not own, is also how ARP spoofing works, so unexplained conflicts on a network you manage are worth investigating. Defensive controls include Dynamic ARP Inspection with DHCP snooping on managed switches, monitoring tools that alert when an IP's MAC changes (for example arpwatch), and network segmentation that limits who shares a broadcast domain. If a MAC you cannot account for keeps claiming a server's address, treat it as an incident and isolate the port.

Troubleshooting addressing, ARP and DHCP on Linux is part of our Linux administration course, run in our Kharadi, Pune classroom and live online.

Frequently asked questions

Can two devices have the same IP address on different networks?

Yes. Private addresses such as 192.168.1.10 are reused in millions of separate networks. A conflict only happens when both devices are in the same Layer 2 network or subnet.

Will an IP conflict damage my device?

No. It causes connectivity problems only. Once one device gets a different address, both work normally.

Why do both devices lose connection, not just one?

Other hosts and the router keep switching the MAC address they associate with the IP, so traffic goes to each device part of the time and established sessions break on both.

How do I find which device is causing the conflict?

Get both MAC addresses from ARP tables, arping replies, the DHCP lease table or the Windows event log. Then use the switch MAC table or wireless controller to find the port or access point for each MAC.

Does restarting the router fix an IP conflict?

Sometimes, briefly, because leases and ARP caches are reset. If a device has a static address inside the DHCP pool, the conflict will return. Fix the configuration instead.

How does IPv6 handle duplicate addresses?

IPv6 hosts run Duplicate Address Detection, defined in RFC 4862, before using an address. If another node already uses it, the address is marked duplicate and is not assigned.

What is the best way to prevent IP conflicts in an office?

Use one DHCP service per subnet, give fixed devices DHCP reservations, keep any manual addresses outside the dynamic pool, enable DHCP snooping on managed switches and record allocations in an IPAM tool.

References

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.