An IP address conflict message in Windows 11 means two devices on the same network were assigned the same IP address. They’re fighting over the same network identity, and the result is both devices losing or experiencing degraded internet access. The notification usually says “Windows has detected an IP address conflict” and the machine’s network icon may show a warning. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The fastest fix in most cases: release and renew your IP address, forcing a fresh assignment from the router.
ipconfig /release
ipconfig /renewAdministrator Command Prompt. After running both commands, wait 30 seconds and test internet access. The /release command tells the router you’re giving up the conflicted address; /renew requests a fresh one. If the router assigns a different address this time, the conflict is gone.
Why it happens
There are two distinct scenarios. Understanding which one applies tells you what to fix permanently:
DHCP gave the same address to two devices — usually happens when a device was offline for longer than the router’s DHCP lease time, the lease expired and was reassigned to a different device, and then the original device came back online still claiming the old address. The release/renew above resolves this. A router restart also clears stale leases.
Someone manually assigned a static IP that conflicts with the DHCP range — more persistent. The device with the static IP ignores /release and /renew because it’s not using DHCP. Find the static IP device and either change its static IP to something outside the DHCP range, or convert it to DHCP.
Restarting the router
Router restart clears the DHCP lease table and reassigns all addresses fresh on reconnection. Unplug the router for 60 seconds → reconnect. Devices reconnect one by one and receive fresh addresses. This resolves conflicts caused by stale DHCP leases where the router “forgot” who had which address. Quick and effective for home networks.
Finding the conflicting device
If the conflict keeps recurring after release/renew and router restart, another device on the network is consistently claiming the same address. To find it: Command Prompt → arp -a → look for the conflicting IP address in the list. The MAC address next to it identifies the conflicting device. Search the MAC address prefix in a MAC lookup tool (macvendors.com) to identify the manufacturer — this tells you what type of device it is (printer, phone, smart home device, etc.).
Router admin panel → DHCP client list also shows all connected devices with their IP and MAC addresses. This is often the fastest way to see every device and spot duplicates.
Static IP on your machine — fix it
If your machine is configured with a static IP: Settings → Network and internet → Wi-Fi or Ethernet → your connection → IP settings → Edit → change from Manual to Automatic (DHCP). After switching to DHCP, the machine requests an address from the router rather than claiming one regardless of what else has it. This eliminates the conflict permanently from your machine’s side.
If you need a static IP (for remote access, printer setup, etc.): choose an address outside the DHCP range. Log into the router admin panel → DHCP settings → note the DHCP range (often 192.168.1.1–192.168.1.100). Set your static IP to something above that range (192.168.1.200, for example) to ensure the router never assigns it automatically to another device.
IoT devices and conflict sources
Smart home devices — plugs, lights, cameras, thermostats — are common conflict sources. They often have long DHCP lease requests (days or weeks) and don’t handle lease renewal gracefully when offline. A camera that was powered off for maintenance, reconnected after the lease expired, and then contested the reassigned address causes exactly this pattern.
Solution: assign reserved (static) DHCP leases to smart home devices in the router admin panel. Most routers allow “DHCP reservation” — you specify a device’s MAC address and the router always assigns the same IP to it. This gives the stability of a static IP without manual configuration on each device, and prevents DHCP reassignment conflicts entirely.
Network stack reset for persistent issues
When /release and /renew don’t work and the conflict notification keeps appearing: the Windows networking stack may have corrupted state that’s causing the machine to claim the same address despite the router trying to assign a different one.
netsh winsock reset
netsh int ip reset
ipconfig /flushdnsAdministrator Command Prompt → all three → restart. After the network stack reset, the machine requests its IP fresh with a clean state.
Corporate networks and DHCP scope exhaustion
In office environments: IP address conflicts sometimes indicate DHCP scope exhaustion — the router or DHCP server has assigned all available addresses and has nothing left to give. When all addresses in the scope are claimed (or appear to be claimed by stale leases), new devices get denied and may see conflict notifications as they try to self-assign an address in the apipa range (169.254.x.x).
IT needs to expand the DHCP scope or reduce lease times to clear stale entries. Users can’t fix scope exhaustion themselves — reporting the conflict alongside the result of ipconfig /all (which shows the current IP address, lease time, and DHCP server) gives IT the information they need to diagnose which problem they’re dealing with.
Our guide on Ethernet no valid IP configuration covers the DHCP failure scenarios that accompany IP conflicts — both errors share the same network stack and DHCP infrastructure. For home networks where smart device management is part of the solution, our router management guide covers accessing the router admin panel and DHCP configuration. Microsoft’s IP address conflict documentation covers the Windows DHCP client event log (Windows Logs → System → source “DHCP-Client”) that records each address assignment attempt and conflict detection event.
VPN and virtual adapter conflicts
VPN software creates virtual network adapters with their own IP address ranges. When the VPN subnet overlaps with the local network range, devices can be assigned addresses that conflict with VPN virtual addresses — or the VPN client may claim an address from the local DHCP range for its tunnel interface.
If conflict notifications started after installing VPN software: check the VPN adapter’s IP address. Settings → Network and internet → Advanced network settings → view all adapters → look for a VPN or TAP adapter → check its IP. If it’s in the same range as the local network (both in 192.168.1.x, for example), the ranges overlap. Most VPN software allows changing the VPN subnet in its settings — change it to a range that doesn’t overlap with the local network (172.16.0.x or 10.0.0.x are common non-conflicting alternatives).
Duplicate MAC address — the rare but real case
MAC addresses are supposed to be globally unique hardware identifiers. In practice, they’re occasionally duplicated — either by manufacturing errors, by MAC spoofing software that cloned another device’s address, or by virtualisation software that assigned a non-unique virtual MAC to a VM.
When two devices on the same network share a MAC address, the DHCP server gives them the same IP (because it uses MAC as the identifier for lease assignment). This creates an IP conflict that release/renew never resolves, because both devices always get the same IP from DHCP by design.
Check the MAC address: ipconfig /all → Physical Address of the conflicted adapter. Compare with the conflicting device’s MAC (from the arp -a output). If they match: one device has an incorrect or cloned MAC. For virtual machines: ensure unique MAC addresses in hypervisor settings. For physical machines: MAC spoofing software sometimes causes this. Device Manager → Network adapter → Properties → Advanced → Network Address — if a custom MAC is configured here, that may be the source of the duplicate.
When the conflict is on a VM host
Machines running VirtualBox, VMware, or Hyper-V create virtual network adapters that appear as separate devices on the network. When a VM is configured in bridged mode (it receives its own IP from the router rather than a private NAT address), it’s subject to the same DHCP assignment as physical devices and can conflict with them.
Conflicts caused by VMs: configure the VM to use NAT networking rather than bridged. In NAT mode, the VM shares the host machine’s IP address rather than having its own, eliminating it as a conflict source. Bridged networking is useful when you need the VM to be accessible from other network devices, but for general use NAT is simpler and conflict-free.
DHCP reservation setup in the router
The permanent prevention for recurring IP conflicts in a home or small office network: configure DHCP reservations for all devices you control. Log into the router admin panel → DHCP settings → look for “DHCP Reservation,” “Static DHCP,” or “IP/MAC Binding” → for each device, enter its MAC address and assign a specific IP address that the router will always give to that device.
After setting up reservations: the router always gives Device A the same IP, Device B a different fixed IP, and so on. No two devices are ever assigned the same address. The reservation approach is more maintenance than pure DHCP (you need to add each new device) but completely eliminates the lease-expiry-conflict scenario. For networks with IoT devices, printers, and servers that need predictable addresses, this is the appropriate configuration regardless of conflict history.
IPv6 address conflicts — different but related
IPv6 uses link-local addresses (starting with fe80::) that are self-generated rather than DHCP-assigned. These can occasionally conflict on very small subnets or when MAC-based address generation produces a collision (rare). IPv6 uses Duplicate Address Detection (DAD) to check for conflicts before using an address — if DAD fails, Windows disables the conflicted IPv6 address and may show an error.
IPv6 conflicts are less common than IPv4 conflicts because the address space is vastly larger and DAD prevents most conflicts before they cause connectivity problems. If IPv6 addresses specifically are conflicting, regenerating the IPv6 address by disabling and re-enabling the network adapter (Device Manager → disable → enable) triggers a fresh DAD process and usually resolves it.
Persistent conflict that survives all fixes
If the conflict notification keeps appearing despite release/renew, router restart, and network stack reset: Windows is seeing a conflict that either isn’t actually there (a false positive from a buggy driver or security software) or is being caused by a device that’s re-asserting the conflicted address faster than Windows can resolve it.
Check the DHCP Client event log to see the exact sequence: Event Viewer → Windows Logs → System → filter by Source “DHCP-Client” → look at Event IDs around 1000 (conflict detected events). These events show the MAC address of the conflicting device, the IP being contested, and the timestamps — which immediately identifies whether this is a rapidly repeating conflict with a specific device or a one-time conflict that keeps getting logged from a stale entry.
One more practical note: IP address conflicts are almost always benign in terms of data security. They’re a routing problem — two devices confusing the network about who to send packets to — rather than a security breach. The conflict doesn’t mean someone is attempting to intercept your traffic (though a malicious actor could theoretically use IP conflict to disrupt a specific device). In a home network with known devices, a conflict is almost certainly DHCP management rather than a security event. In a corporate environment with unknown devices appearing in the arp table: worth reporting to IT as it could indicate an unauthorised device on the network, even if the conflict itself isn’t a threat.
The three-step resolution that works for the vast majority of home network IP conflicts: (1) ipconfig /release and /renew on the affected machine, (2) restart the router to clear stale leases, (3) if conflicts recur, identify the conflicting device via arp -a and either remove its static IP or set up DHCP reservations in the router. Steps 1 and 2 are immediate fixes; step 3 is the permanent prevention. The more involved diagnostics — duplicate MAC addresses, VPN subnet overlap, DHCP scope exhaustion — apply to the minority of cases where the first three steps didn’t resolve it completely.
If you’re on a network where you don’t control the router (hotel, student accommodation, shared office): IP conflicts are more common because the DHCP pool is shared among many unknown devices with varying lease behaviours. Your only local fix in these environments is release/renew and potentially setting a static IP in a range that’s unlikely to conflict (ask IT or network management for an appropriate static IP if DHCP keeps producing conflicts). You can’t set up reservations or restart a shared router. Our guide on Router DHCP Not Assigning IP Address covers an adjacent issue.
