IPdidi
English

How to fix an IP address conflict

An address-conflict warning usually concerns devices on your local network. Start with the affected connection and its DHCP settings before changing your router or public IP.

What the warning means

An IPv4 address conflict occurs when two devices try to use the same IPv4 address on the same network link. Traffic may reach the wrong device or connectivity may become unreliable. An explicit duplicate-address warning is a stronger clue than slow internet alone.

For example, a printer manually configured as 192.168.1.50 can collide with a laptop if the router also assigns that address through DHCP. DHCP is the service that leases local network settings to devices.

Two devices showing the same public IP on a website is a different situation. Home routers commonly let many devices share a public IPv4 address. See public vs private IP addresses.

Before changing anything

Do not factory-reset the router or choose a random address as a first step. An address that looks unused might belong to an offline device.

Restore the affected connection

Reconnect and check automatic addressing

Disconnect and reconnect the affected Wi-Fi or Ethernet connection. If the device has an unnecessary manual IPv4 address, return it to automatic addressing only when you know the network uses DHCP. Keep a record of any settings you change.

A device with a deliberately assigned static configuration, such as a managed server or printer, needs its address checked against the network plan instead.

Renew a DHCP lease

On Windows, open Command Prompt and run ipconfig /all to identify the affected adapter and check its DHCP status. If it uses DHCP, ipconfig /renew "Wi-Fi" requests renewed configuration for an adapter named Wi-Fi; substitute the actual adapter name. Renewal may return the same address.

On a Mac, open System Settings > Network, select the connection, open Details > TCP/IP, and choose Renew DHCP Lease. Labels can vary by macOS version.

Renewal can restore connectivity, but a recurring conflict needs the underlying assignment problem fixed. These instructions describe vendor-documented controls; they are not a claim that IPdidi has reproduced the fault on your device.

Find why the conflict returns

On a home router you administer, inspect its DHCP leases, reservations, and connected-device list. Compare them with known manual addresses, especially printers, cameras, NAS devices, and a recently added second router.

FindingWhat to check next
A manual address overlaps the DHCP poolReserve that address correctly, or move the manual device to a documented address excluded from dynamic allocation.
Two devices have the same manual addressAssign unique addresses using the correct subnet and gateway.
A second DHCP server serves the same network without coordinationCheck the second router's intended role and its setup instructions.
The router list shows only one deviceCheck leases and device configuration; a current list can miss an offline device.

Two routers are not automatically a fault. A router serving a separate downstream subnet is different from two uncoordinated DHCP servers serving the same link. Do not disable the only DHCP server while investigating.

For devices that need stable local addresses, a DHCP reservation often simplifies management: the router consistently assigns a chosen address to a particular device. Keep manual assignments and dynamic pools coordinated.

Verify the result

Reconnect the affected device and check that it has the intended local configuration, can reach the router, and can access the services it needs. Then check that the conflicting device also works. A warning disappearing once does not prove a recurring assignment problem is resolved.

The IP lookup and My IP page can help check public internet connectivity after recovery. They cannot inspect your router's DHCP leases or prove that local devices have unique addresses.

Common questions

Will a VPN fix an IP conflict?

A VPN does not repair duplicate addresses on your home network. Troubleshoot the local connection and address assignments first. Virtual adapters can add complexity, so identify which adapter reported the warning.

Does changing DNS fix it?

Changing a DNS resolver does not give two local devices unique IPv4 addresses. DNS troubleshooting belongs to a different problem: resolving names after basic connectivity works.

Does a conflict mean someone hacked my network?

The warning alone does not establish an attack. Accidental manual configuration or an assignment problem can cause it. Investigate unfamiliar devices through your router's supported controls rather than assuming their identity from an address.

Sources and scope

This guide covers local IPv4 conflicts. IPv6 address configuration and duplicate-address detection require separate troubleshooting.

Sources checked on November 4, 2026.