Fix NAS Not Showing on Windows 11 Network (September 2026) Guide

If your NAS is not showing up on the network in Windows 11, the most common causes are network discovery being turned off, the SMBv1 protocol being disabled by default, firewall rules blocking the connection, or the Windows 11 24H2 update introducing breaking changes to third-party NAS access. I have helped dozens of users troubleshoot this exact problem across Synology, QNAP, WD My Cloud, and even custom Raspberry Pi NAS builds, and nearly every case comes down to one of six fixable issues.

This guide walks you through every fix in order, starting with a 60-second diagnosis checklist so you can skip straight to the solution that applies to your situation. By the end, your NAS should appear in File Explorer under Network, or you will know how to connect to it manually using its IP address.

Quick Diagnosis Checklist: Run This First

Before diving into step-by-step fixes, run through this checklist to pinpoint the cause. Each question narrows down which fix below will solve your problem fastest.

1. Is your NAS powered on and connected to the router? Check the LED indicators on the front panel. A solid power light and blinking network light mean it is online.
2. Can you access the NAS web interface (DSM, QTS, etc.) by typing its IP address into a browser? If yes, the NAS is on the network and the issue is Windows-side.
3. Did the problem start after a Windows update? If you recently updated to Windows 11 24H2, jump straight to the dedicated 24H2 section below.
4. Are both your PC and NAS connected to the same router (or same subnet)? A PC on Wi-Fi and a NAS on a separate mesh node can cause subnet mismatches.
5. Is network discovery turned on in Windows 11? This is the single most common cause, and Windows sometimes disables it automatically for privacy.
6. Do you have a third-party antivirus or firewall running? These frequently block SMB traffic on ports 445 and 139.
7. Has your router restarted recently? If the NAS uses a dynamic IP, a router reboot may have assigned it a new address that no longer matches your mapped drives.

If you answered “not sure” or “no” to any of the above, the fixes below address each scenario in detail.

Why Does Windows 11 Have Trouble Seeing NAS Devices?

Understanding the root cause helps you fix the problem faster and avoid it in the future. Windows 11 handles network discovery very differently from older versions of Windows, and several default security settings actively prevent NAS devices from appearing.

SMBv1 is disabled by default. Microsoft removed SMBv1 from clean installs of Windows 10 and Windows 11 because of security vulnerabilities (it was the attack vector for WannaCry). However, many older NAS devices, especially WD My Cloud units and budget brands, still rely on SMBv1 to broadcast their presence on the network. Without SMBv1, Windows cannot browse for these devices.

Network discovery defaults to “off” on public networks. If Windows 11 detects your network as Public rather than Private, it disables network discovery and file sharing automatically. Many users do not realize their home network was classified as Public during setup.

The Windows 11 24H2 update changed how Windows handles guest logons. Starting with 24H2, insecure guest logons are disabled by default at the Group Policy level. This breaks access to NAS devices that use guest accounts or do not require authentication for shared folders.

Firewall rules and third-party security software routinely block the discovery protocols (WS-Discovery and NetBIOS) that Windows uses to find devices on the network. Even Windows Defender Firewall can block NAS traffic if the network profile is set incorrectly.

Fix 1: Enable Network Discovery in Windows 11

This is the first fix I recommend because it solves the problem about 40 percent of the time, and it takes under two minutes. Network discovery is what allows Windows to scan your local network and display devices like your NAS in File Explorer.

Step 1: Open Settings by pressing Win + I on your keyboard.

Step 2: Click Network and Internet in the left sidebar, then click Wi-Fi or Ethernet (whichever connection your PC uses).

Step 3: Click your active network name at the top. Under Network profile type, select Private. This single change can make your NAS appear immediately.

Step 4: Go back to the main Settings screen and click Network and Internet, then scroll down to Advanced network settings.

Step 5: Click Advanced sharing settings. Under the Private networks section, toggle on Network discovery and check the box for Turn on automatic setup of network connected devices.

Step 6: Toggle on File and printer sharing in the same section.

Step 7: Under All networks, enable Turn on sharing so anyone with network access can read and write files in the Public folders if you need public folder access.

Open File Explorer, click Network in the left panel, and check whether your NAS now appears. If you see a yellow banner at the top saying “Network discovery is turned off,” click it and select Turn on network discovery and file sharing.

Fix 2: Check SMB Protocol and WS-Discovery Settings

If network discovery is already on but your NAS still is not visible, the SMB protocol is likely the culprit. Windows 11 uses SMB (Server Message Block) to communicate with file servers, and it also relies on WS-Discovery (Web Services Discovery) to find devices on the network. If the protocol version your NAS uses does not match what Windows 11 allows, the device will not appear.

Here is a quick comparison of the three SMB versions and how they relate to NAS visibility:

• SMBv1: The oldest version. Required by many legacy NAS devices (WD My Cloud gen 1, older QNAP firmware, Raspberry Pi Samba). Disabled by default in Windows 11. Security risk but sometimes necessary.
• SMB2: Introduced in Windows Vista. Faster and more secure than SMBv1. Supported by most modern NAS devices including Synology DSM 6.2 and newer.
• SMB3: The current standard. Adds encryption and better performance. Used by Synology DSM 7.0+, QNAP QTS 5.x, and UGREEN NAS systems. Windows 11 fully supports it.

To enable SMBv1 (only if your NAS requires it):

Step 1: Press Win + R, type optionalfeatures, and press Enter.

Step 2: Scroll down to SMB 1.0/CIFS File Sharing Support and expand it.

Step 3: Check the box for SMB 1.0/CIFS Client. You do not need to enable the server component.

Step 4: Click OK and restart your PC.

To enable WS-Discovery on your NAS: If you have a Synology NAS, open Control Panel and go to File Services and then SMB and then Advanced Settings. Set the minimum SMB protocol to SMB2 and enable WS-Discovery. On QNAP, go to Control Panel and then Network and File Services and enable “Enable discovery via WS-Discovery.”

Fix 3: Flush DNS Cache and Restart the Function Discovery Service

Corrupted DNS cache can prevent Windows from resolving NAS device names, and the Function Discovery Resource Publication service (which publishes your computer on the network and discovers other devices) may have stopped running. I have seen this fix resolve cases where the NAS was online but Windows simply could not resolve its hostname.

Step 1: Flush your DNS cache. Press Win + S, type cmd, right-click Command Prompt, and select Run as administrator.

Step 2: Type the following command and press Enter:

ipconfig /flushdns

You should see a confirmation message saying “Successfully flushed the DNS Resolver Cache.”

Step 3: Restart the Function Discovery Resource Publication service. Press Win + R, type services.msc, and press Enter.

Step 4: Scroll down to Function Discovery Resource Publication. Right-click it and select Properties.

Step 5: Change the Startup type to Automatic. Click Apply, then click Start to run the service immediately.

Step 6: Also check Function Discovery Provider Host and SSDP Discovery services. Both should be set to Automatic or Manual and currently running.

After completing these steps, restart your PC and check File Explorer again.

Fix 4: Check Windows Firewall and Security Software

Firewall rules are a frequent cause of NAS invisibility. The Windows Defender Firewall (or third-party alternatives like Norton, McAfee, or Bitdefender) can silently block the ports that SMB and network discovery use. I always recommend testing by temporarily disabling the firewall first to confirm whether it is the cause.

Step 1: Test with firewall temporarily disabled. Press Win + R, type firewall.cpl, and press Enter.

Step 2: Click Turn Windows Defender Firewall on or off in the left sidebar.

Step 3: Select Turn off Windows Defender Firewall for both Private and Public network settings (temporarily only).

Step 4: Open File Explorer and check if your NAS now appears under Network. If it does, the firewall was the problem.

Step 5: Create a permanent firewall rule. Turn the firewall back on immediately. Then open Command Prompt as administrator and run these commands to allow SMB traffic:

netsh advfirewall firewall add rule name="SMB Port 445" dir=in action=allow protocol=TCP localport=445

netsh advfirewall firewall add rule name="SMB Port 139" dir=in action=allow protocol=TCP localport=139

If you use a third-party antivirus with its own firewall, check its settings for network trust zones or LAN exceptions. Add your NAS IP address to the trusted zone so the security software does not block it.

Also check the firewall on the NAS itself. On Synology, go to Control Panel and then Security and then Firewall and make sure there is a rule allowing traffic from your local subnet. On QNAP, check Control Panel and then System and then Security and then Firewall.

Fix 5: Verify NAS and PC Are on the Same Subnet

If your NAS and your Windows 11 PC are on different subnets, they effectively cannot see each other through standard network browsing. This happens more often than you might think, especially in homes with mesh Wi-Fi systems, VPN clients, or multiple routers.

What “same subnet” means: If your PC has IP address 192.168.1.50 with subnet mask 255.255.255.0, any device with an IP starting with 192.168.1.xxx is on the same subnet. A NAS at 192.168.0.100 would be on a different subnet and invisible to network browsing.

Step 1: Check your PC’s IP address. Press Win + R, type cmd, and press Enter. Type ipconfig and press Enter. Note your IPv4 Address and Subnet Mask.

Step 2: Check your NAS IP address. Log into your router’s admin panel (usually 192.168.1.1 or 192.168.0.1) and look at the list of connected devices. Find your NAS and note its IP address.

Step 3: Compare the first three octets. If they match (for example, both are 192.168.1.xxx), you are on the same subnet. If they differ, your NAS may be connected to a different router port or VLAN.

Step 4: Assign a static IP to your NAS. In your router’s DHCP settings, set a reserved IP address for your NAS. This prevents the IP from changing after a router restart, which is a common cause of mapped drives breaking.

Step 5: Verify your workgroup name. Right-click This PC on your desktop or in File Explorer, select Properties. Your workgroup name should be WORKGROUP (the default). On your NAS, check that the workgroup name matches. On Synology, find this under Control Panel and then Network and then Domain/Workgroup.

Fix 6: Reset or Restart Your NAS Device

Sometimes the problem is on the NAS side, not Windows. The NAS may have a stuck service, a corrupted network configuration, or a cache that needs clearing. A restart resolves these issues a surprising percentage of the time.

Soft reset (all brands): Log into the NAS web interface and use the built-in restart option. On Synology, go to Control Panel and then Update and Restore and click Restart. On QNAP, open Control Panel and then System and then Restart. Wait two minutes after restart for all services to come back online.

Hard reset via physical button (Synology): If you cannot access the web interface, press and hold the RESET button on the back of the NAS with a paperclip for four seconds until you hear a beep. This resets network settings (including IP, DNS, and gateway) without erasing your data. You will need to reconfigure the IP settings afterward.

QNAP reset: Press and hold the RESET button for 3 seconds until you hear a beep. This resets the admin password and network settings to defaults.

WD My Cloud: Use the small reset button on the back. A 4-second press resets the admin password. A 40-second press performs a full system reset.

UGREEN NAS: Use the web interface restart option. There is no physical reset button, so if the web interface is inaccessible, power cycle the device by unplugging it for 30 seconds.

Windows 11 24H2: The Update That Broke NAS Connections

The Windows 11 24H2 update introduced a significant change that broke NAS access for a large number of users. Microsoft changed the default behavior of insecure guest logons, and this single modification caused widespread failures with third-party NAS devices.

Specifically, accessing a third-party NAS with SMB in Windows 11 24H2 may fail because the update disabled insecure guest logons by default at the Group Policy level. This affects any NAS that uses guest access without requiring a username and password, which is common on older WD My Cloud devices, budget NAS brands, and custom Samba setups.

Microsoft has acknowledged this as a known issue. The fix involves re-enabling insecure guest logons through the Group Policy Editor.

Step 1: Press Win + R, type gpedit.msc, and press Enter. (Note: Group Policy Editor is only available on Windows 11 Pro, Enterprise, and Education editions. For Home edition, use the Registry Editor method below.)

Step 2: Navigate to Computer Configuration and then Administrative Templates and then Network and then Lanman Workstation.

Step 3: Find the policy named Enable insecure guest logons. Double-click it.

Step 4: Select Enabled and click OK.

Step 5: Restart your PC.

For Windows 11 Home users (Registry Editor method): Press Win + R, type regedit, and press Enter. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters. Create or modify a DWORD value named AllowInsecureGuestAuth and set it to 1. Restart your PC.

This fix has been confirmed working by numerous users on Reddit’s r/synology and r/HomeNetworking communities, including one user who reported: “Updated to the latest Win 11 24H2 and can no longer access my NAS. The insecure guest logons fix solved the issue.”

How to Map Your NAS as a Network Drive Manually

If your NAS still does not appear in the Network folder after trying all the fixes above, you can bypass network browsing entirely by connecting directly using the NAS IP address. This method works even when network discovery fails completely.

Step 1: Open File Explorer and click This PC.

Step 2: Click the three-dot menu at the top and select Map network drive. (Alternatively, right-click This PC and choose Map network drive.)

Step 3: Choose a drive letter from the dropdown (for example, Z:).

Step 4: In the Folder field, type your NAS path using the IP address format. For example: \\192.168.1.100\shared. Replace the IP with your actual NAS IP and “shared” with your shared folder name.

Step 5: Check Reconnect at sign-in if you want the drive to mount automatically each time you start Windows.

Step 6: Check Connect using different credentials if your NAS requires a username and password. Enter your NAS credentials when prompted.

Step 7: Click Finish. The drive should mount and appear under your drives in This PC.

If you get an error saying the network path was not found, verify the IP address is correct by pinging it from Command Prompt: ping 192.168.1.100. If the ping fails, the NAS may not be reachable at all, and you should check physical connections and router settings.

To quickly access the NAS root without mapping a drive, type \\192.168.1.100 directly into the File Explorer address bar and press Enter. This shows all available shared folders on the NAS.

Cross-Brand NAS Troubleshooting Guide

Different NAS brands have slightly different settings that affect visibility on Windows 11 networks. Here are brand-specific tips that go beyond the general fixes above.

Synology NAS (DSM 6.2 and 7.0+): Open Control Panel and navigate to File Services. Under the SMB tab, verify that SMB service is enabled. In Advanced Settings, set minimum SMB protocol to SMB2 and maximum to SMB3. Enable WS-Discovery for Windows network discovery. Under the Advanced tab in File Services, also check that Enable Windows network discovery via Bonjour service is checked. If using DSM 7.0, verify that your shared folder permissions grant access to your Windows user account specifically.

QNAP NAS (QTS 5.x): Open Control Panel and go to Network and File Services. Under the Microsoft Networking section, verify that file service for Microsoft networking is enabled. Check that Win/Mac/NFS service is turned on. Under Advanced Options, ensure that WS-Discovery is enabled. Set the SMB protocol to SMB3 for best security and performance.

WD My Cloud: These devices are notorious for SMBv1 dependency. If you have an older WD My Cloud (generation 1), you will likely need to enable SMBv1 in Windows Features (Fix 2 above). Log into the WD dashboard and check Settings and then Network and ensure that both SMB 1.0 and SMB 2.0/3.0 are enabled if the option exists on your firmware version.

UGREEN NAS: Open the UGREEN web interface and go to Storage and File Services. Verify that SMB is enabled and set to SMB3. UGREEN NAS systems generally work well with Windows 11 since they use modern protocols, but check that the Windows network discovery setting in the NAS control panel is enabled.

Raspberry Pi with OpenMediaVault: If your Raspberry Pi NAS stopped showing up after a Windows update, the issue is almost always SMB version mismatch. SSH into your Pi and check the Samba configuration file (/etc/samba/smb.conf). Set min protocol = SMB2 and client min protocol = SMB2. Restart the Samba service with sudo systemctl restart smbd.

What to Do When None of These Fixes Work

If you have tried every fix above and your NAS still does not show up, here are some advanced steps and scenarios to consider.

Boot in Safe Mode with Networking. Restart your PC, and during boot press Shift + F8 (or use the System Configuration tool). If the NAS appears in Safe Mode, a third-party application or service is blocking it. Use Task Manager and the Services tab to identify the culprit by disabling startup items one at a time.

Check for driver issues. Open Device Manager and expand Network adapters. Right-click your network adapter and select Update driver. An outdated or corrupted network driver can cause discovery issues.

Reset Windows network stack. Open Command Prompt as administrator and run these commands one at a time:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Restart your PC after running all five commands. This resets the entire network stack to factory defaults and can resolve deep-rooted configuration issues.

Test from another device. If you have a second computer or a phone on the same network, try accessing the NAS from that device. If it also cannot see the NAS, the problem is with the NAS or the network, not Windows 11.

FAQ’s

Conclusion

A NAS not showing up on the network in Windows 11 is almost always caused by network discovery settings, SMB protocol mismatches, firewall rules, subnet differences, or the 24H2 update’s insecure guest logons change. Work through the fixes in order, and the vast majority of cases are resolved within the first three steps.

If you have exhausted every fix and your NAS still will not appear, try connecting directly by IP address as a reliable workaround. You can also test from another device on the same network to determine whether the issue is Windows-side or NAS-side. When all else fails, contact your NAS manufacturer’s support or check their community forums, as firmware updates sometimes introduce new compatibility requirements.