My Synology sat in the corner blinking happily, fully powered, fully online, and completely absent from the Network panel on a freshly reinstalled Windows 11 machine. No error, no warning, just an empty list where a friendly little server icon used to be.
That silence is the frustrating part. Windows does not tell you what is wrong, it just quietly pretends the box is not there.
The good news is that in almost every case I have troubleshooted, the cause is one of three things, and none of them require you to touch the NAS itself. Work through the steps below in order and you will land on the fix without guessing.
First, confirm the NAS is actually reachable
Before you change a single Windows setting, prove the NAS is alive on the network. This one test saves people hours of chasing discovery settings when the real problem is a dead cable or a wrong IP.
Open the Start menu, type cmd, and hit Enter. In the black window, type ping followed by your NAS IP address, for example ping 192.168.1.50.
If you do not know the IP, most NAS brands have a finder tool. Synology has its own web-based device finder, and QNAP ships Qfinder. Either will show you the current address in under a minute.
Got four replies back? Good. The NAS is on the network and Windows can talk to it. The reason it is missing from the panel is now almost certainly a discovery or protocol setting on the PC side.
Step 1: Set your network profile to Private
This is the single most common culprit, and it is the first thing I check every time. Windows 11 hides network devices when it thinks you are on a public network, like a coffee shop, to protect you.
The trouble is that Windows frequently defaults a home Ethernet or Wi-Fi connection to Public after a reinstall or a router swap. On Public, network discovery is switched off by design, so your NAS vanishes.
Open Settings, go to Network and internet, then click your active connection (Ethernet or Wi-Fi). Under Network profile type, choose Private network.
That change alone brings the NAS back for a large share of people. Give it thirty seconds and reopen File Explorer to check.
Why Private matters so much
A Private profile tells Windows you trust this network, which flips on discovery and lets your PC both broadcast and listen for other devices. Public keeps you invisible and deaf. There is no middle ground that shows a NAS while staying on Public.
Step 2: Turn on network discovery and file sharing
Setting the profile to Private usually enables discovery automatically, but not always. It is worth confirming manually, because a leftover setting from a previous config can keep it off.
Go to Settings, then Network and internet, then Advanced network settings, then Advanced sharing settings. Expand the Private networks section.
Turn on both Network discovery and File and printer sharing. Make sure the box for "Set up network connected devices automatically" is ticked as well.
Restart File Explorer after this, or reboot if you want to be thorough. Give the network a minute to repopulate, because discovery broadcasts on a timer rather than instantly.
Step 3: Re-enable SMB, the protocol Windows dropped
Here is the one that catches almost everyone eventually. Windows 11 no longer installs the older SMB 1.0 client by default, and it disabled it entirely for security reasons after some ugly ransomware years.
Modern NAS units use SMB 2 or SMB 3 and are fine. But an older NAS, or one left on factory defaults, may still be advertising itself over SMB 1, which is exactly the part Windows removed.
The correct fix is not to reinstall SMB 1 on the PC. It is to raise the SMB version on the NAS. Log into your NAS control panel, find the file services or SMB settings, and set the maximum protocol to SMB 3 and the minimum to SMB 2.
| Symptom | Likely SMB issue | Fix |
|---|---|---|
| NAS missing from panel, ping works | NAS only advertising SMB 1 | Raise NAS max to SMB 3, min to SMB 2 |
| Can reach NAS by IP but not name | Browser service / SMB 1 discovery gone | Access via IP, enable WS-Discovery on NAS |
| "You can't connect because SMB1" error | PC forcing legacy protocol | Update NAS firmware, keep SMB1 off |
The reliable workaround: map by IP address
The Network panel is a convenience, not the actual connection. If discovery keeps being flaky, you can skip it entirely and connect straight to the NAS by its address. This works even when the panel is stubbornly empty.
In File Explorer, click the address bar and type two backslashes followed by the NAS IP, like 192.168.1.50, then press Enter. Your shared folders should appear and prompt for a username and password.
To make it permanent, right-click This PC, choose Map network drive, pick a letter, enter 192.168.1.50sharename, and tick Reconnect at sign-in. Now you get a drive letter every boot regardless of what the Network panel decides to show.
I run every one of my machines this way. It has never once dropped off after a Windows update, which is more than I can say for the discovery panel.
Pin the NAS IP so it never moves
Mapping by IP only stays reliable if the IP stays put. Log into your router, find the DHCP reservation or static lease list, and tie the NAS MAC address to a fixed address. It takes two minutes and removes a whole category of future headaches.
Still empty? A quick catch-all pass
If you have done all three steps and the panel is still blank, run through this short list. One of these usually flushes out the holdout.
- Restart both devices. A full power cycle of the PC and the NAS clears stale discovery caches on both ends.
- Check the firewall. Third-party security suites love to block network discovery. Temporarily disable one to test, then add an exception if that was the cause.
- Confirm both are on the same subnet. A PC on 192.168.1.x and a NAS on 192.168.0.x will never see each other by discovery. Match the first three octets.
- Enable WS-Discovery on the NAS. Synology and QNAP both offer this newer discovery method that replaces the old SMB 1 browsing. Turn it on in the file services settings.
Nine times out of ten, the profile-plus-SMB combination is the answer, and the map-by-IP trick covers the rest permanently.
Where this leaves you
An empty Network panel feels like a hardware failure, but it is nearly always three toggles and a protocol version standing between you and your files. Set the profile to Private, confirm discovery is on, raise the SMB level on the NAS, and you are done.
And if you would rather never think about it again, map the drive by IP with a reserved address. That is the setup I trust on my own gear, and it survives updates that break the pretty panel every single time.
Frequently asked questions
Why can Windows 11 ping my NAS but still not show it in Network?
Ping confirms the network path works, but the Network panel relies on separate discovery services. Usually the profile is set to Public, network discovery is off, or the NAS is only advertising over the removed SMB 1 protocol. Fix those and the icon returns.
Should I reinstall SMB 1.0 to see my NAS?
No. SMB 1 has serious security flaws and Microsoft removed it on purpose. The correct fix is to raise the SMB version on the NAS to 2 or 3, which every NAS made in the last decade supports through its control panel.
How do I connect to my NAS without it showing in Network?
Type two backslashes and the NAS IP address into the File Explorer address bar, for example \192.168.1.50, then press Enter. You can also right-click This PC and choose Map network drive to get a permanent drive letter that ignores the discovery panel entirely.
Where do I change the network profile from Public to Private in Windows 11?
Open Settings, go to Network and internet, click your active Ethernet or Wi-Fi connection, then under Network profile type select Private network. Wait about thirty seconds and reopen File Explorer to check.
My NAS keeps disappearing after Windows updates. How do I stop that?
Discovery is fragile and updates often reset it. Map the NAS by its IP address and reserve that IP in your router's DHCP settings. A mapped drive with a reserved address reconnects at every sign-in regardless of the discovery panel.
