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 seeing the device in the Network section , but it's not always that easy: sometimes the device doesn't appear, it asks for credentials and fails, or Windows simply says the destination isn't responding. If this sounds familiar, don't worry, there are several common causes and proven solutions you can try.

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

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

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

If your NAS or USB router doesn't meet the security requirements (for example, it doesn't support SMB signing) , Windows 11 24H2 may deny the connection. This results in access errors or messages stating that "the cryptographic signature is invalid." The only real solution is for the manufacturer to release patches or firmware updates; otherwise, these devices will be incompatible in environments requiring mandatory SMB signing.

This hardening isn't 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 be dependent on whether or not the manufacturer releases an update. 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 delving into fine-tuning, it's advisable 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 doesn't appear in Explorer, you can still access it via a UNC path by typing \\NAS-IP\FolderName in the address bar or by assigning that folder to a drive letter; you'll see this alternative step by step below.

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

In modern Windows environments, well-configured WS-Discovery and SMB on the NAS make all the difference . Synology makes this easy with clear options, although these 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) so that the NAS advertises 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 using DSM 6.1 or earlier, enabling the Local Master Browser can help when dealing 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, verify that the SMB service is active and using a version supported by your equipment . 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 can "hide" computers if network discovery is disabled or policies block unsafe guests . These changes are quick and usually resolve visibility issues in many cases.

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

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

Enable 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 in all windows.

If the DNS cache is corrupted or there are discovery conflicts, disable and re-enable discovery and clear the DNS cache . Disable network discovery, apply the changes, 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 (e.g., 192.168.1.29) is online but not responding to connection attempts . In Synology scenarios, the system may complain about port 5000 (DSM HTTP) or 8080 if you changed the configuration, pointing to possible policies or a firewall on the remote machine.

If Windows claims that its own firewall is not the problem and other computers can access it without issue , 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 blocks on that PC.

Check the correct DSM port : By default, DSM listens on 5000 (HTTP) and 5001 (HTTPS). If you reset network settings and tried 8080 without success, try https://NAS-IP:5001/ and verify that there are no port forwarding settings on the router that might be affecting internal access.

If you are using a DNS blocker or a custom DNS on your router , try: 1) temporarily stopping the blocker (such as Pi-hole), 2) setting public DNS servers on your PC or router, and 3) connecting by direct IP address instead of hostname to rule out resolution issues.

Verify that no third-party software is 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 often occurs because SMBv1 is not active or the device requires it . Microsoft disabled SMBv1 in Windows 10/11 for security reasons and advises against using it except when absolutely necessary.

To enable “SMB 1.0/CIFS File Sharing Support” in Windows 10/11 (useful on some older NAS/storage devices such as certain WD drives), go to Control Panel > Programs > Programs and Features > Turn Windows features on or off > check “SMB 1.0/CIFS File Sharing Support” and restart your system.

Keep in mind that SMBv1 is no longer available by default in many modern editions , and although it can still be enabled in Home/Pro, the official recommendation is to update the NAS's SMB server to use modern and secure versions.

If enabling SMBv1 resolves the access issue, use it as a stepping stone to migrate to a more modern 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 appropriate.

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

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

If the NAS appears but you can't log in with the correct password , check the security policies, the SMB signature in Windows 11 24H2, and the NAS date/time (time discrepancies 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 can "fix" the connection in File Explorer, even if discovery fails: this way, you can access it via \\NAS-IP\Resource with persistence upon login.

Rebooting and physical checks of the NAS

When the software doesn't provide any clues, go back to basics : cabling, ports, and a controlled NAS reboot 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 accessing via direct IP address, verify that it responds to 5001/HTTPS, and check network visibility . If other computers can access it but this PC cannot, focus on Windows (discovery details, GPO, SMB, and DNS).

Practical alternative: assign a drive letter to your resource

When the network browser fails, mapping the resource to a drive saves you searches and stabilizes access . In Windows, open File Explorer > This PC > Map Network Drive, choose a drive letter, and in the Folder field, type \\NAS-IP-Number\FolderName. Check "Reconnect at logon."

If you're using credentials other than your Windows credentials , select the "Connect using different credentials" option and enter the NAS username. This approach also helps when network visibility is intermittent but the NAS is responding via IP address.

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.