How to access your NAS from Windows 11: how-to guide and solutions

Accessing a NAS from Windows 11 can be as simple as opening File Explorer and viewing the device under the Network section., but this isn't always the case: sometimes the device doesn't appear, asks for credentials and fails, or Windows simply says the destination isn't responding. If this situation sounds familiar to you, don't worry; there are several typical causes and proven solutions you can apply.

In this text we review, in detail and point by point, what is essential for Windows 11 to see and open your NAS., recent security changes affecting the SMB protocol, recommended settings for both the NAS (Synology DSM as a reference) and Windows itself, and the most common issues blocking access (ports, DNS, network discovery, firewalls, or SMB incompatibilities).

What's changed in Windows 11 with SMB and why it might affect your NAS

Microsoft has strengthened SMB security in Windows 11 24H2 enabling SMB signing by defaultThis move, announced by Microsoft's own software team, seeks to mitigate attacks that exploit insecure devices on the network, such as routers with USB or certain older NAS that do not implement current security measures.

If your NAS or router USB does not meet security requirements (e.g., does not support SMB signing)Windows 11 24H2 may deny the connection. This results in access errors or messages indicating that "the cryptographic signature is invalid." The real solution is for the manufacturer to issue patches or firmware updates; otherwise, these devices will be unavailable in environments with mandatory SMB signing.

This hardening is not intended to “break” your network, but rather to prevent tampering in transit and unauthorized access.Even so, if you have an older, unsupported model, you'll depend on whether the manufacturer releases an update or not. Microsoft has even provided a contact channel to report specific cases of blocked models.

Basic requirements for the NAS to appear and be accessible

Before going into the nitty-gritty of fine-tuning, it's a good idea to check the essentials.: that the NAS and PC are on the same network and subnet, that discovery and file services are active, and that there is no third-party software interfering.

• Same LAN and subnet: Ensure that the PC and NAS have compatible IPs on the same network (e.g. 192.168.1.x) and masks.
• Network Discovery in Windows: In Control Panel > Network and Internet > Network and Sharing Center > Change advanced sharing settings, turn on network discovery.
• File Services and Discovery on the NAS: On Synology, enable SMB and WS-Discovery (we explain where to do this according to DSM).
• Avoid interference from third-party firewalls: Temporarily disables non-Microsoft security suites to prevent crashes.
• Functional DNSIf you are using local resolvers (such as Pi-hole), try temporarily disabling them or using public DNS to resolve name resolution issues.

If the NAS still does not appear in Explorer, you can still access it via UNC path. by typing \NAS-IP\FolderName in the address bar or assigning that folder to a drive letter; you'll see this step-by-step option below.

Set up Synology DSM: WS-Discovery, SMB and Master Browser

In modern Windows environments, properly configured WS-Discovery and SMB on the NAS make all the difference.Synology makes it easy with clear options, although they vary depending on the DSM version.

If you are using DSM 6.2 or later (including DSM 7.0), enable Windows Network Discovery (WS-Discovery) To make the NAS announce itself correctly on the Windows network:

• DSM 6.2: Control Panel > File Services > SMB tab > check WS-Discovery.
• DSM 7.0: Control Panel > File Services > Advanced tab > WS-Discovery.

If you are on DSM 6.1 or earlier, it may help to enable the Local Master Browser. When you live with older versions of Windows or networks with irregular discovery:

• DSM 6.0 and 6.1: Control Panel > File Services > SMB/NFS/AFP > SMB > Advanced Settings.
• DSM 5.2: Control Panel > File Services > Win/NFS/Mac > Windows File Service > Advanced Settings.

Also check that the SMB service is active and with a version supported by your devices.Avoid using SMBv1 unless absolutely necessary (see specific section), and prioritize secure versions compatible with Windows 10/11 and your NAS.

Key Settings in Windows 10/11: Discovery, Policies, and NetBIOS

Windows 11 may “hide” computers if network discovery is disabled or policies block unsafe guests.These changes are quick and often resolve visibility issues in many cases.

Turn on network discovery in Control Panel > Network and Internet > Network and Sharing Center > Change advanced sharing settings > Turn on network discovery and save the changes.

Allow insecure guest logins (if your NAS requires them) From the Group Policy Editor: Computer Configuration > Administrative Templates > Network > Lanman Workstation > Enable insecure guest logons > Enabled. Use this only if absolutely necessary.

Enables NetBIOS over TCP/IP When NetBIOS discovery is required on your network: Control Panel > Network and Internet > View network status and tasks > Change adapter settings > Open your connection properties > Double-click Internet Protocol Version 4 (TCP/IPv4) > Advanced > WINS tab > Check “Enable NetBIOS over TCP/IP”. Click OK on all prompts.

If the DNS cache is corrupted or there are discovery conflicts, disable and re-enable discovery and flush DNS.. Disable network discovery, re-enable it, and clear the DNS cache before attempting to connect again.

When the NAS is “online” but not responding: the case of port 5000/8080

A typical Windows diagnostic indicates that the resource (for example, 192.168.1.29) is online, but is not responding to connection attempts.In Synology scenarios, the system may complain about port 5000 (DSM HTTP) or 8080 if you changed the settings, pointing to possible policies or firewall issues on the remote computer.

If Windows claims that its own firewall is not the problem and other computers access it without error, it is most likely a client setting: policies, disabled SMB features, network discovery, NetBIOS, or a local resolver (such as Pi-hole) that is introducing locks on that PC.

Check the correct port of the DSMBy default, DSM listens on 5000 (HTTP) and 5001 (HTTPS). If you've reset your network settings and tried 8080 without success, try https://NAS-IP:5001/ and verify that there are no port forwardings on your router that could affect internal access.

If you use a DNS blocker or custom DNS on your router, try to: 1) temporarily stop the blocker (like Pi-hole), 2) put public DNS on the PC or router, and 3) connect by direct IP instead of hostname to rule out resolution.

Check that there is no third-party software filtering traffic on that specific PC.Temporarily disabling the external firewall or security suite helps rule out perimeter conflicts, especially with ports 5000/5001.

SMBv1: Only if there is no other option (and knowing the risks)

The “NAS not visible” error is often triggered because SMBv1 is not active or the device requires it.Microsoft has disabled SMBv1 in Windows 10/11 for security reasons and recommends against using it unless absolutely necessary.

To enable “SMB 1.0/CIFS File Sharing Support” in Windows 10/11 (useful on some older NAS/storage like certain WDs), go to Control Panel > Programs > Programs and Features > Turn Windows features on or off > check “SMB 1.0/CIFS file sharing support” and reboot.

Please note that SMBv1 is no longer available out of the box in many modern editions., and although it can still be enabled on Home/Pro, the official recommendation is to update the NAS SMB server to use modern and secure versions.

If enabling SMBv1 resolves the issue, use it as a stepping stone to migrate to a current security level.The goal should be for your NAS to support modern SMB and, if you're using Windows 11 24H2, to work with SMB signing where applicable.

Other settings that make a difference: caches, guest and mapping

On mixed networks, clearing caches and reviewing guest access can resolve visibility without touching the NAS.. Toggle network discovery, clear DNS cache, and check if your environment requires insecure guest logins (Lanman Workstation GPO) for credential-less resources.

If the NAS appears but you don't log in with the correct password, check security policies, SMB signing in Windows 11 24H2, and the NAS date/time (time mismatches can invalidate signatures). Also confirm that the account and permissions on the NAS are valid for that shared folder.

Mapping the shared folder to a drive letter may “fix” the connection in File Explorer, even if discovery fails: this way, you access it by \\NAS-IP\Resource with persistence when logging in.

Rebooting and physical checks of the NAS

When software doesn't give clues, go back to basics: : Cabling, ports, and a controlled reboot of the NAS can resolve intermittent issues.

• Same network and subnet: Check that the NAS has not jumped to another VLAN or a different subnet by DHCP.
• Temporarily disable your PC's firewall (or third-party software) to bypass local filters.
• Try another Ethernet cable to eliminate doubts of faulty wiring.
• If the NAS has multiple ports, change the cable to another port to rule out a damaged NIC.
• Short Reset on Synology: Press the button RESET about 4 seconds (until you hear a beep) to restore the network without losing data; consult the official guide if needed.

After these checks, retry access via direct IP, check that it responds in 5001/HTTPS and check visibility on the Network.If other computers log in and that PC doesn't, focus on Windows (discovery details, GPO, SMB, and DNS).

Practical alternative: assign a drive letter to your resource

When the web browser fails, mapping the resource to a drive saves you searches and stabilizes access.. In Windows, open Explorer > This team > Connect to a network drive, choose a letter, and in Folder, type \\NAS-IP\FolderName. Select “Reconnect at login.”

If you use credentials other than Windows, select the “Connect using different credentials” option and enter the NAS username. This approach also helps when “Network” visibility is spotty but the NAS is responding via IP.

Typical mistakes and how to interpret them

• “The resource is online, but not responding”: This usually points to ports (5000/5001/8080) blocked at the destination or SMB policies/signatures preventing the session. Try HTTPS:5001, check the SMB signature in 24H2, and rule out security software blocking.
• “The cryptographic signature is invalid”: A symptom is that the NAS or USB router doesn't support the SMB signing required by Windows 11 24H2. The solution is to update the firmware or replace the device with a compatible one.
• It does not appear in “Network”, but opens by \\IP\Folder: The problem is discovery (WS-Discovery/NetBIOS). Enable WS-Discovery on the NAS, NetBIOS over TCP/IP on Windows, and network discovery.
• Other computers can access it, this PC can't.: Focuses on the client. Checks guest GPOs, SMB features in Windows, DNS caching, and the presence of resolvers like Pi-hole, which sometimes only affect a single machine.