My Synology DS220+ vanished from the network on a Tuesday night, right in the middle of a Plex movie. The library froze, the mobile app spun forever, and then Windows threw a little balloon: "There is an IP address conflict with another system on the network."
Two devices had grabbed the same address. One of them was my NAS.
This is one of the most common and most misdiagnosed home network problems I run into. People assume a drive died or the NAS bricked itself, when really two machines are just arguing over one number. Here is exactly how to find the culprit and shut it down for good.
What an IP conflict actually is
Every device on your home network needs a unique address, something like 192.168.1.50. Your router hands these out automatically through a system called DHCP, which is basically a receptionist assigning seat numbers as guests arrive.
A conflict happens when two devices end up holding the same seat number. The router thinks the address is free and hands it to a laptop, but your NAS is still sitting there using it. Traffic gets confused, packets go to the wrong place, and both devices start dropping off intermittently.
The classic trigger: someone set the NAS to a fixed manual address like 192.168.1.50, but never told the router to stop giving that same address to other devices. Weeks later the router leases .50 to a phone, and the fight begins.
Step 1: Confirm it is really the NAS
Before touching anything, write down the address in the warning. On Windows the balloon usually names the conflicting IP. On a Mac, System Settings, Network will flag it in red under the active connection.
Now check whether that address belongs to your NAS. Open your NAS admin panel (DSM for Synology, QTS for QNAP) if you can still reach it, and look under Control Panel, Network, Network Interface. Note the IP it thinks it has.
If the NAS shows 192.168.1.50 and the conflict warning also says 192.168.1.50, you have your confirmation. The NAS may still respond by name for a minute or two before it drops, so move quickly.
Step 2: Find the other device fighting for the address
This is the part everyone skips, and it is the most useful step. You need to know what else is claiming that IP, or the conflict comes straight back.
Log in to your router (commonly 192.168.1.1 or 192.168.0.1 in a browser) and find the client list, sometimes labeled DHCP Leases, Connected Devices, or Attached Devices. This table shows every device, its assigned IP, and its hardware MAC address.
Look for the disputed IP. You may see it listed against a device that is clearly not the NAS: an iPhone, a smart TV, a Windows laptop. That is your second combatant.
Step 3: Clear the collision fast
The quickest way to break the deadlock is to force one device to release the address. I usually do this to the non-NAS device because it is easier to move.
- Reboot the offending device (the laptop or phone). When it comes back, the router should lease it a fresh, different IP.
- If you cannot reach that device, reboot the NAS instead. Power it down cleanly from the admin panel, wait 30 seconds, and start it again.
- As a last resort, reboot the router itself. This clears the whole lease table and forces everyone to renegotiate.
After the reboot, check the router client list again. The two devices should now hold two different addresses. Your shares should reappear within a minute.
This gets you working again, but it is a bandage. If you stop here, it will happen again in a few weeks. The real fix is Step 4.
Step 4: Reserve the NAS address permanently
The correct long-term fix is a DHCP reservation. You tell the router: "This exact MAC address always gets this exact IP, and never give that IP to anyone else." It is the best of both worlds, a stable address that the router still respects.
Here is how the two common approaches compare.
| Method | Where you set it | Conflict risk |
|---|---|---|
| Static IP on the NAS | NAS network settings | High if the address sits inside the router's DHCP pool |
| DHCP reservation | Router client list | Very low, the router protects the address |
| Static IP outside the pool | Both NAS and router | Low, but needs manual planning |
To set a reservation, go back to the router's DHCP settings, find your NAS by its MAC address, and click Reserve or Add Static Lease. Pick an address, ideally one low and memorable like 192.168.1.10, and save.
Then, on the NAS itself, set the network interface back to Get IP automatically (DHCP). This sounds backwards, but it is right: the NAS asks for an address, and the router always answers with the reserved one. No manual settings on both ends to fall out of sync.
Step 5: Avoid the conflict coming back
The root cause is nearly always an overlap between manually assigned addresses and the router's automatic pool. Fix the overlap and the problem stays gone.
Most home routers hand out DHCP addresses in a range, say 192.168.1.100 through 192.168.1.200. Anything you assign by hand, or reserve, should either sit outside that range or be a proper reservation inside it. Never a random static address in the middle of the pool with no reservation.
If you run several fixed devices, a NAS, a printer, a Pi, a Home Assistant box, keep a short note of which IP belongs to what. Ten minutes of documentation saves you an hour of detective work later.
A quick sanity check
Once everything settles, ping the NAS from a computer to confirm it responds steadily. Open a terminal or command prompt and run ping followed by the NAS address. Watch for a run of replies with no timeouts. Steady replies mean the address is now uniquely yours.
If you still see intermittent "Request timed out" lines mixed with replies, two devices are probably still sharing the address, and you missed one in the lease table. Go back to Step 2 and look harder.
When it is not really a conflict
One more thing worth flagging, because it fooled me once. If you have two routers or a mesh system plus an old router still running DHCP, you can get phantom conflicts from two separate address servers handing out overlapping numbers.
Log in to each router and make sure only one has DHCP enabled. The second unit should be in access point or bridge mode with its DHCP server switched off. Two DHCP servers on one network is a guaranteed source of recurring conflicts, and no amount of reservations will fix it until you disable the extra one.
Getting your evening back
Nine times out of ten, an IP conflict with a NAS is a two-minute reboot to get moving and a five-minute reservation to make it permanent. The trick is resisting the urge to reboot blindly and instead reading the router's lease table so you actually know which two devices were fighting.
Set the reservation, tidy your address ranges, and this particular pop-up should never interrupt a movie night again.
Frequently asked questions
Will an IP address conflict corrupt the data on my NAS?
No. An IP conflict is a network addressing issue, not a disk issue. Your volumes, shares, and files are untouched. Once the two devices hold different addresses again, everything comes back exactly as it was.
Should I set a static IP directly on the NAS or use a router reservation?
Use a router DHCP reservation in most homes. It gives the NAS a permanent address while letting the router protect that address from being handed to anything else. A raw static IP set only on the NAS is the single most common cause of the conflict in the first place.
Why did the conflict appear weeks after everything worked fine?
The NAS was likely on a manual IP that sat inside the router's DHCP pool. It worked until the day the router leased that same address to a new phone or laptop. Nothing changed on the NAS, the collision was just waiting to happen.
How do I know which device is stealing the NAS address?
Open the router's connected devices or DHCP lease list and find the disputed IP. Match by MAC address rather than name, since NAS units use manufacturer prefixes like 00:11:32 for Synology. A different prefix on that IP is your intruder.
I have a mesh system and conflicts keep coming back. What is wrong?
You probably have two devices running DHCP at once, such as an old router still active alongside the mesh. Disable DHCP on all but one unit and put the extras in access point or bridge mode. Recurring conflicts almost always trace back to a second address server.
