Possible symptoms
The connection may become intermittent, disappear after another device arrives, or display a conflict alert. A conflict does not explain all outages: a Wi-Fi, DHCP or DNS failure can produce similar symptoms.
Common causes
The classic case combines a manually configured address and a DHCP-assigned address in the same range. A duplicate reservation, a cloned system image, or two poorly coordinated DHCP servers can also assign the same address.
Resolution procedure
Temporarily disconnect one of the affected devices, and then put regular customers back into automatic provisioning. Renew their lease and check the router's reservations. For a fixed address, use a single DHCP reservation or a range that is explicitly excluded from the pool.
Preventing the return of conflict
Document static addresses, centralize bookings, and avoid random choices. On a managed network, DHCP logs and ARP tables can be used to reconcile an IP address to the interfaces that claim it.
Frequently asked questions
Is there a conflict with my public IP?
Most often not: it concerns a private address used inside the local network.
Is changing the address at random a solution?
No. This can shift the conflict. The DHCP assignment must be corrected or an explicitly reserved address must be chosen.
Reference sources
To be explored next
Published and verified by the VoirMonIP.com team on July 15, 2026.