How to Resolve IP Address Conflict on a Local Network

How to Resolve IP Address Conflict on a Local Network

How to Resolve IP Address Conflict on a Local Network

Your laptop keeps dropping off Wi-Fi while another device works normally. A duplicate address may be the reason. To resolve a conflicting IP address, identify both network interfaces using it, remove the overlap, and then check that each device stays connected.

An IP address conflict happens when two interfaces try to use the same local address on the same network segment. The steps below focus on IPv4, the familiar dotted-number addresses used on most home networks.

What is an IP address conflict and why does it happen?

What is an IP address conflict? It is a duplicate assignment that makes it difficult for nearby devices to determine which interface should receive traffic for that address. An interface is a device’s network connection, such as its Wi-Fi adapter or Ethernet port.

Most routers use DHCP (Dynamic Host Configuration Protocol) to lend addresses to clients for a period called a lease. A conflict can arise if someone manually assigns an address already in the DHCP pool, if two devices have the same manual address, or if competing DHCP servers hand out overlapping addresses. A device that reconnects only occasionally can make the problem appear intermittent. A DHCP reservation asks the server to give a particular client a chosen address; a manual or static setting is configured on the device itself.

Knowing how to resolve an IP address conflict starts with finding the competing assignments. A router’s lease list is helpful evidence, but a manually configured or sleeping device may not appear there. Microsoft’s DHCP troubleshooting guidance specifically suggests checking for static addresses that have not been excluded from the DHCP scope.

Check whether the trouble is local

A duplicate IP problem often affects particular devices or appears when a certain device wakes up. A warning naming a duplicate address is a strong clue. Compare the affected device with another client on the same network: can each reach the router, and can each reach an internet site? Note the time, the address in the warning and which devices are active.

If all devices lose internet access together but can still reach the router, investigate the router’s upstream connection or provider as well. If site names fail while IP-based services work, investigate DNS.

Find both sides of the overlap

Before changing anything, record the affected interface’s IPv4 address, subnet mask, default gateway and MAC address from its network settings. On Windows, ipconfig /all displays these details. Check the Wi-Fi and Ethernet adapters separately; VPN and virtual adapters can also have their own settings.

Sign in to the router or DHCP server and inspect the client or lease list, reservations and DHCP address range. Match addresses and MAC addresses against the affected devices. Compare MAC addresses shown for the particular network; names may be misleading.

Look for a second interface with the same address in its manual settings, including printers, cameras and devices that wake on a schedule. A lease list records DHCP assignments; it is not a complete inventory of static devices. If necessary, disconnect one suspected device briefly and observe whether the other recovers, then reconnect it and check again. A stale listing alone is not proof of two active users.

Remove the overlap safely

To fix an IP address conflict, first decide which device needs a stable address. Record existing settings before changing them. Then use one of these arrangements:

  • Automatic addressing: Set ordinary clients to obtain an address automatically from the intended DHCP server. Remove conflicting manual assignments and renew the affected leases.
  • DHCP reservation: If a device supports DHCP but needs a predictable address, reserve an address for its current client identifier or MAC in the router. Follow that router’s reservation rules, remove any conflicting manual assignment, and renew the client’s lease.
  • Manual address: Choose an unused usable address in the correct subnet, outside the DHCP pool or explicitly excluded from it. Check reservations and other static devices too. Enter the correct subnet mask, gateway and DNS settings for that network.

An IP address conflict fix also requires checking that only the intended DHCP service assigns addresses on that segment. A second router in the wrong mode can run another server; consult its instructions before changing modes. On a managed workplace network, ask the network administrator to make these changes.

For example, on a 192.168.1.0/24 network with a router at 192.168.1.1 and a DHCP pool of 192.168.1.100 through 192.168.1.199, an unused 192.168.1.20 may be suitable for a manual device. First check that it is not reserved or used elsewhere. The subnet and pool on your network may be different.

Renew and verify

Reconnect or renew each affected DHCP client after correcting the configuration. On Windows, ipconfig /release followed by ipconfig /renew renews DHCP configuration and briefly interrupts connectivity. Check the resulting address and gateway; a reserved address can remain the same if unique. Do not use release and renew as a substitute for correcting a duplicate manual setting.

Bring the suspected intermittent device back online. Confirm that both interfaces have distinct addresses, can reach the router and can use the services they need. Recheck after sleep or a restart. If the conflict returns, inspect the DHCP server and manual settings again, including devices absent during the first check.

Keep this checklist for resolving an address conflict: record the warning and interface details; identify both users of the address; correct the DHCP, reservation or manual overlap; renew affected clients; and verify both devices again while they are online.