Full Diagnostic Tree & Step-by-Step Overview
An IP address conflict occurs when two devices on the same local network claim the exact same local IP (e.g., 192.168.1.50). Which operating system is throwing the error prompt?
- Windows OS ('Windows has detected an IP address conflict' or Code 4101)
- macOS ('Another device on the network is using your computer's IP address')
- Multiple devices (phones, printers, smart TVs) are randomly dropping offline simultaneously
Is your Windows computer configured to use a Static IP address, or does it obtain its IP automatically from your router (DHCP)?
- Obtain an IP address automatically (DHCP is enabled)
- Use the following IP address (Manually assigned static IP)
- I don't know / I want to completely reset all Windows network adapters
Stale DHCP Allocation or Outdated Network Interface Lease
Solution:
Diagnostic Cause
Windows is holding onto an expired dynamic IP lease in memory that the router has already re-assigned to a different device (like a smartphone or printer) that reconnected while your PC was asleep.
Step-by-Step Fix
1. Open Command Prompt as Administrator (Win + X > select Terminal (Admin) or Command Prompt (Admin)).
2. Force Windows to drop the current conflicting IP by typing:
ipconfig /release press Enter3. Clear stale hardware-to-IP mappings from memory:
arp -d * press Enter4. Flush local DNS caches:
ipconfig /flushdns press Enter5. Request a completely fresh, unique IP from your router:
ipconfig /renew press Enter6. Verify that the newly assigned IPv4 address resolves the error popup.
Manual Static IP Set Inside Router's Dynamic Assignment Pool
Solution:
Diagnostic Cause
You or a network utility assigned a static IP to this computer (e.g., 192.168.1.100), but that exact IP falls inside your router's active DHCP assignment range. The router subsequently gave that address to another device.
Step-by-Step Fix
1. Press Win + R, type ncpa.cpl and hit Enter to open Network Connections.
2. Right-click your active adapter (Ethernet or Wi-Fi) > select Properties.
3. Highlight Internet Protocol Version 4 (TCP/IPv4) > click Properties.
4. Option A (Recommended): Select Obtain an IP address automatically and Obtain DNS server address automatically.
5. Option B (If you require a static IP): Change the last number of your IP (e.g., to 192.168.1.225) to move it far outside the router's dynamic pool (which typically covers .2 through .100).
6. Click OK > Close to re-bind the interface.
Corrupted Winsock Stack or Phantom Virtual Adapter Collision
Solution:
Diagnostic Cause
Virtual adapters (from Hyper-V, VMware, or VPN clients) can create persistent ghost bindings that clash with your physical Ethernet or Wi-Fi interface.
Step-by-Step Fix
1. Click Start > open Settings (Win + I).
2. Navigate to Network & internet > Advanced network settings.
3. Scroll down and select Network reset.
4. Click Reset now > confirm Yes.
5. Windows will automatically clean all network adapters, remove virtual bridges, and restart your PC in 5 minutes.
6. Upon reboot, reconnect to your Wi-Fi or Ethernet network.
How is your Mac's network service configured in System Settings?
- Using DHCP (Automatic configuration)
- Using DHCP with Manual Address, or Manually configured static IP
- Connected via Wi-Fi and Thunderbolt Dock simultaneously
Expired macOS BSD Socket Lease & Cache Desynchronization
Solution:
Diagnostic Cause
macOS caches network parameters inside its system configuration daemon (configd). When coming out of Sleep mode, the OS may attempt to reuse an IP address that another local device claimed while the Mac was suspended.
Step-by-Step Fix
1. Open the Apple Menu () > click System Settings.
2. Select Network in the sidebar > click your active connection (Wi-Fi or Ethernet).
3. Click Details... next to the connected network.
4. Select TCP/IP from the left-hand tab menu.
5. Click Renew DHCP Lease > click Apply.
6. *If the conflict persists*: Open Terminal (Cmd + Space > type Terminal), run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and enter your Mac password to flush the local multicast DNS and IP resolution tables.
Manual IP Assignment Collision or Stale Location Profile
Solution:
Diagnostic Cause
A static IP assigned on macOS matches the address of a static server, smart hub, or secondary computer on the same subnet.
Step-by-Step Fix
1. Go to System Settings > Network > select your active connection (Wi-Fi/Ethernet).
2. Click Details... > select TCP/IP.
3. Locate Configure IPv4:
Change setting from *Manually* or *Using DHCP with manual address* back to Using DHCP.4. If a manual address is required for local hosting, click Configure IPv4 > select Using DHCP with manual address and enter an IP address high in your subnet range (e.g., 192.168.1.240).
5. Click OK > Apply.
Dual Physical Interfaces (Wi-Fi + Dock Ethernet) Claiming Same Subnet
Solution:
Diagnostic Cause
When a Mac is docked, both its Wi-Fi card and Thunderbolt/USB-C Ethernet adapter may request separate IP addresses simultaneously while attempting to bridge services, leading to internal ARP packet confusion.
Step-by-Step Fix
1. Open System Settings > Network.
2. Click the three-dot dropdown icon (...) at the bottom of the service list > select Set Service Order...
3. Drag Ethernet (or your Dock adapter) to the top of the list.
4. Drag Wi-Fi below Ethernet.
5. Click Save.
6. Turn off Wi-Fi when plugged into Ethernet to prevent single-device MAC address cloning collisions.
Rogue DHCP Server, Corrupted Router ARP Table, or Pool Exhaustion
Solution:
Diagnostic Cause
When multiple devices toss IP conflict errors simultaneously, the router's internal DHCP lease table has become corrupted or exhausted (too many smart devices filling up a small pool like 192.168.1.100 to 192.168.1.120).
Step-by-Step Fix
1. Reboot Network Gateway: Unplug the power cable from your router/switch, wait 30 seconds, and plug it back in. This completely wipes the temporary dynamic ARP table and forces all connected clients to re-negotiate fresh leases.
2. Log into Router Management: Open a browser and go to 192.168.1.1 or 192.168.0.1.
3. Navigate to LAN Settings / DHCP Server.
4. Expand Pool Size: Set Start IP Address to 192.168.1.2 and End IP Address to 192.168.1.254 (allowing up to 253 devices).
5. Check for Rogue DHCP: Ensure you do not have a secondary router or Wi-Fi extender plugged into a LAN port with its own DHCP server turned ON (set extenders to *Access Point (AP) Mode*).