You log into your Synology or QNAP dashboard without a problem, click around DSM or QTS like normal, and everything looks healthy. Then you open File Explorer, type in your NAS address, and nothing. The shared folders simply will not open. If you are dealing with a situation where your NAS web interface loads but shared folders won’t open, you are far from alone. This is one of the most reported issues across the r/synology and r/qnap communities, and the good news is that it is almost always fixable without factory resetting anything.
The short answer: your NAS runs the web admin interface (HTTP/HTTPS on ports 5000, 5001, or 8080) as a completely separate service from SMB file sharing (TCP port 445). When the web interface loads but shared folders won’t open, the web server service is running fine, but the SMB service, permissions, network discovery, or Windows client settings have a problem. The two systems are independent, which is why one can work perfectly while the other fails silently.
In this guide, I will walk you through exactly why this happens and how to fix it across Synology DSM, QNAP QTS, ASUSTOR ADM, TerraMaster TOS, and Windows 10/11 clients. I have pulled together the best solutions from official brand knowledge bases, Microsoft Learn, and hundreds of forum threads so you do not have to hunt through a dozen tabs. Let us start with understanding the root cause, then move into a quick diagnostic checklist, and finally work through brand-specific fixes.
Table of Contents
Why Does My NAS Web Interface Load but Shared Folders Won’t Open: The Root Cause
To fix this problem properly, you need to understand why it happens in the first place. Your NAS is not a single program. It is a mini-server running dozens of independent services, each communicating over different network ports. The web interface you access through your browser is one service, and file sharing through SMB is a completely different service. When the NAS web interface loads but shared folders won’t open, the web server daemon is healthy while the SMB daemon or its supporting infrastructure is not.
Here is a quick breakdown of what runs what. The web admin panel runs on an embedded web server (typically Apache or Nginx) listening on HTTP port 5000 or HTTPS port 5001 for Synology, port 8080 for QNAP QTS, and similar ports for other brands. You access it by typing the NAS IP address followed by the port number in a browser. This service handles authentication through the web application itself and has nothing to do with Windows file sharing protocols.
SMB (Server Message Block) file sharing, on the other hand, is handled by a separate service. On Synology DSM, this is the Samba daemon. On QNAP QTS, it is also Samba under the hood. SMB communicates over TCP port 445 (and historically ports 139 for NetBIOS). It requires its own authentication system, its own permission structure, and its own protocol version negotiation between the NAS and your client computer. If any link in that chain breaks, the web interface will still load fine because it is an entirely separate process.
What is SMB? SMB (Server Message Block) is the network file sharing protocol used by Windows, macOS, and Linux to access files over a network. CIFS (Common Internet File System) is an older dialect of SMB, and the two terms are often used interchangeably even though modern systems use SMB 2.0 or SMB 3.0.
What is TCP port 445? TCP port 445 is the standard network port used by SMB for direct file sharing over IP. If this port is blocked by a firewall, the NAS web interface will still load on port 5000/5001, but no shared folders will be accessible.
What is NetBIOS? NetBIOS is an older naming and discovery protocol that runs over TCP ports 137, 138, and 139. Modern Windows versions can use SMB over port 445 without NetBIOS, but some discovery features still rely on it.
So when your NAS web interface loads but shared folders won’t open, one of these five root causes is almost always responsible. First, the SMB service on the NAS is disabled or misconfigured. Second, shared folder permissions or user access rights are blocking the connection. Third, Windows network discovery or SMB client settings are preventing the connection. Fourth, a firewall or security application is blocking TCP port 445. Fifth, stale credentials in Windows Credential Manager are causing authentication failures. The diagnostic checklist below will help you pinpoint which one applies to your situation.
Quick Diagnostic Checklist: Identify the Problem in 5 Minutes
Before diving into deep troubleshooting, run through this seven-step diagnostic checklist. These steps will tell you exactly which layer is failing so you can jump to the right section of this guide instead of trying every fix blindly. I have seen users spend hours resetting their NAS when the problem was simply a wrong credential stored in Windows.
Step 1: Ping the NAS by IP address. Open Command Prompt and type ping 192.168.1.100 (replace with your NAS IP). If you get replies, the NAS is reachable on the network. If you get request timeouts, you have a network connectivity problem, not an SMB problem.
Step 2: Test SMB port connectivity. Type telnet 192.168.1.100 445 in Command Prompt. If you see a blank screen, port 445 is open and the SMB service is listening. If the connection fails, either the SMB service is not running on the NAS or a firewall is blocking the port. This single test eliminates half the possible causes.
Step 3: Try accessing by IP instead of hostname. Open File Explorer and type \\192.168.1.100 (your NAS IP). If this works but \\NAS-Name does not, you have a name resolution (NetBIOS or DNS) problem, not an SMB service problem. This is extremely common and one of the most frequent reports on the r/synology subreddit.
Step 4: Try the net use command. Type net use \\192.168.1.100\ShareName /user:yourusername yourpassword in Command Prompt. This bypasses File Explorer entirely and tests SMB directly. If this works, your issue is with Windows File Explorer browsing, not SMB itself.
Step 5: Check if the issue is on one PC or all PCs. If SMB works from one computer but not another on the same network, the problem is on the client side, not the NAS. Focus on the Windows client settings section below.
Step 6: Check if the web interface shows SMB as enabled. Log into your NAS admin panel and navigate to the file services or SMB settings page. Confirm the SMB service is actually toggled on. It sounds obvious, but DSM updates and QTS upgrades have been known to toggle this off.
Step 7: Clear stored credentials. Open Windows Credential Manager (Control Panel > Credential Manager > Windows Credentials) and remove any entries related to your NAS. Stale credentials from an old password are a top cause of authentication failures that look like permission problems.
Once you have run through these seven steps, you should have a clear picture of where the failure is happening. The sections below address each layer in detail, starting from the NAS side and moving to the client side.
Fix NAS-Side SMB Service Configuration
If your diagnostic showed that port 445 is not responding or the SMB service appears disabled, you need to fix the NAS-side configuration. The exact steps depend on your NAS brand, so I have broken this down for the four most common systems. These steps assume you can access the web interface, which is the case if you are reading this guide.
Synology DSM SMB Configuration
Synology DiskStation Manager makes SMB configuration straightforward. Log into DSM and open Control Panel. Navigate to File Services > SMB (in DSM 7.x, this is under File Services > SMB tab). Ensure the Enable SMB service checkbox is ticked. If it was already enabled, toggle it off, click Apply, then toggle it back on and click Apply again. This restarts the Samba daemon and clears stuck connections.
Under the SMB settings, check the SMB protocol version. Set the minimum SMB protocol to SMB2 and the maximum to SMB3 for the best balance of compatibility and security. Do not set the minimum to SMB1 unless you have a legacy device that absolutely requires it, as SMB 1.0 has known security vulnerabilities. Also verify that the Workgroup name matches your Windows workgroup (typically WORKGROUP for home networks).
In DSM 7.2 and later, also check the Advanced settings. Enable WS-Discovery if your Windows machines need the NAS to appear in the Network folder of File Explorer. Enable NTLMv2 authentication support for Windows 10 and 11 compatibility. If you recently updated DSM, these settings may have been reset during the update process.
QNAP QTS SMB Configuration
For QNAP NAS running QTS, log into the admin panel and open Control Panel. Navigate to Network and File Services > Win/Mac/NFS. Under the Microsoft Networking section, confirm Enable file service for Microsoft networking is checked. This is the master toggle for SMB on QNAP systems.
Click the settings gear next to the SMB toggle to configure protocol versions. Set the minimum SMB version to SMB2 and maximum to SMB3, matching your Synology configuration. Verify the workgroup name and check that the authentication mode is set to user-level (not share-level) for proper per-user permissions.
If you are running QuFirewall on your QNAP, check that it is not blocking TCP port 445. QuFirewall is aggressive by default and some rulesets block internal LAN SMB traffic. Navigate to QuFirewall > Rules and verify that your local subnet is whitelisted for SMB access. A surprising number of QNAP SMB failures trace back to QuFirewall rules applied after a firmware update.
ASUSTOR ADM SMB Configuration
On ASUSTOR NAS devices running ADM, log into the admin portal and open Services. Navigate to File Services > Windows (SMB). Ensure Enable Windows file service (SMB/CIFS) is checked. Click Settings to configure the SMB protocol version, workgroup name, and authentication options.
Set the maximum SMB protocol to SMB3 for compatibility with modern Windows systems. Check the local master browser setting if your NAS needs to appear in the Windows Network folder. Apply changes and wait for the service to restart before testing access again.
TerraMaster TOS and Other Brands
TerraMaster TOS follows a similar pattern. Open the Control Panel > File Services > Windows (SMB) section and verify the SMB service is enabled. Set the protocol version appropriately and confirm the workgroup matches your Windows configuration. For OpenMediaVault and TrueNAS systems, check the SMB/CIFS settings under Services and verify the service is running.
After making any NAS-side SMB changes, restart the SMB service or reboot the NAS entirely. I have seen cases where the service says it restarted but did not actually clear the stuck state until a full NAS reboot. Once the NAS side is confirmed working, move on to permissions.
Verify Shared Folder Permissions
Even if the SMB service is running correctly, you will not be able to access shared folders if permissions are not set up properly. NAS permission systems have two layers: share-level permissions (who can access the share itself) and file-level permissions (who can read or write specific files within the share). Both must be correct for SMB access to work. When users report that the NAS web interface loads but shared folders won’t open, permission misconfiguration is the second most common cause after SMB service issues.
Synology DSM Permission Check
In Synology DSM, open Control Panel > Shared Folder. Select the folder you cannot access and click Edit. Go to the Permissions tab. Verify that your user account has Read/Write access. Check both the local user and any group permissions. If the shared folder shows a lock icon, it is encrypted and needs to be mounted before it can be accessed via SMB.
To mount an encrypted shared folder in DSM, go to Control Panel > Shared Folder, select the encrypted folder, and click Mount. Enter the encryption key. The folder will only be accessible via SMB after it has been mounted. If your NAS rebooted and the encrypted folder did not auto-mount, that explains why SMB access broke while the web interface continued working normally.
Also check Control Panel > Shared Folder > Advanced. Verify that the Hide sub-folders and files from users without permissions option is not preventing visibility. If you are using domain users instead of local users, verify the domain connection is healthy in Control Panel > Domain/LDAP.
QNAP QTS Permission Check
In QNAP QTS, open Control Panel > Shared Folders. Select the shared folder and click Edit Shared Folder Permissions. Choose Microsoft networking access mode. Verify that your user account or group has Read/Write or Read Only access as appropriate.
QNAP also has a separate folder permission system accessed by clicking the folder icon next to each share. Check that subfolder permissions are inherited correctly. If permission inheritance is broken, top-level access may work but subfolders will return access denied errors. This is a common issue after QTS firmware updates.
Guest Access Considerations
If you are trying to access the NAS without entering credentials (guest access), be aware that Windows 10 and 11 block insecure guest logons by default. This means the NAS web interface loads fine, but SMB connections fail silently because Windows refuses to send unauthenticated guest credentials. To resolve this, either create a proper user account on the NAS for SMB access or configure Windows to allow insecure guest authentication (covered in the advanced troubleshooting section below).
Fix Windows Client-Side SMB Settings
If your NAS-side SMB service and permissions are correct, the problem likely sits on the Windows client side. Windows 10 and 11 have become increasingly restrictive about SMB connections due to security concerns, and Windows updates frequently reset or change SMB-related settings. Many users report that SMB worked fine until a Windows update, then suddenly stopped while the web interface continued loading without issue.
Enable Network Discovery and File Sharing
Open Settings > Network and Internet > Status > Properties (for your active network adapter). Set the network profile to Private, not Public. Public network profiles disable network discovery and file sharing by default, which would prevent SMB browsing even if the service itself works.
Then open Control Panel > Network and Sharing Center > Advanced sharing settings. Under the Private profile, enable Turn on network discovery and Turn on file and printer sharing. Under All Networks, you may need to enable file sharing for devices that use 40-bit or 56-bit encryption depending on your NAS configuration. Disable password-protected sharing only if you are intentionally using guest access.
Start Required Windows Services
Several Windows services must be running for SMB browsing to work. Open Services (services.msc) and verify the following services are running with automatic startup type. Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery, UPnP Device Host, TCP/IP NetBIOS Helper, and Workstation.
If any of these services are stopped, right-click and select Start. Also check their startup type is set to Automatic, not Manual or Disabled. Windows updates and third-party system optimization tools sometimes disable these services to save resources, which breaks SMB discovery. I have seen multiple cases where a user ran a system cleaner tool and lost NAS access because it disabled Function Discovery Resource Publication.
Clear Windows Credential Manager
Stale or incorrect stored credentials are one of the most overlooked causes of SMB failures. When you connect to a NAS share and enter credentials, Windows stores them in Credential Manager for future use. If you later change your NAS password or the NAS was reconfigured, the old credentials remain and cause silent authentication failures.
Open Control Panel > Credential Manager > Windows Credentials. Look for any entries containing your NAS IP address or hostname. Remove all of them. The next time you try to access the shared folder, Windows will prompt you for fresh credentials. This single fix resolves a surprising percentage of SMB access issues, and it is completely free and safe to do.
Map a Network Drive Instead of Browsing
Browsing the Network folder in File Explorer relies on discovery protocols like WS-Discovery and SSDP, which are notoriously unreliable. Mapping a network drive directly bypasses discovery entirely and connects via SMB using a specific path. Right-click This PC and select Map Network Drive. Choose a drive letter and type \\192.168.1.100\ShareName using your NAS IP and share name. Check Reconnect at sign-in and Connect using different credentials if needed.
If mapped drives work but Network browsing does not, you have confirmed a discovery protocol issue, not an SMB service issue. This is the most common scenario reported on Reddit, and the fix is simply to use mapped drives instead of relying on the Network folder.
Toggle SMB 1.0 Feature (With Caution)
Open Control Panel > Programs > Turn Windows features on or off. Look for SMB 1.0/CIFS File Sharing Support. For security reasons, SMB 1.0 should be left disabled unless you have a very old NAS that only supports SMB 1.0. If your NAS is from 2026 or earlier, it supports SMB 2.0 or higher and you should not need SMB 1.0.
However, some users have found that toggling SMB 1.0 off, restarting Windows, then ensuring it stays off clears cached SMB state that was causing connection problems. If nothing else has worked, try this toggle cycle. Just be sure to leave it disabled when you are done, as SMB 1.0 is vulnerable to attacks like EternalBlue.
Fix SMB Access from macOS
Most NAS troubleshooting guides focus exclusively on Windows, but macOS users face SMB issues too. If you are on a Mac and your NAS web interface loads but shared folders won’t open, the fixes are similar but use different tools. macOS has native SMB support built into Finder, but its SMB client implementation can be finicky with certain NAS configurations.
Open Finder and press Command+K (or go to Go > Connect to Server). Type smb://192.168.1.100 using your NAS IP address. Click Connect and enter your NAS credentials when prompted. Using the IP address instead of the hostname avoids mDNS/Bonjour name resolution issues that commonly affect macOS SMB connections.
If the connection fails, check the SMB protocol version your NAS is offering. macOS supports SMB 2.0 and 3.0 natively. If your NAS is configured to require SMB 3.1.1 or a dialect your macOS version does not support, the connection will fail silently. Try lowering the maximum SMB version on your NAS to SMB 3.0 as a test.
For stubborn macOS SMB issues, try accessing the share from Terminal using mount_smbfs //[email protected]/ShareName /tmp/mountpoint. If this works but Finder does not, the problem is with Finder’s SMB implementation, not the NAS or network. Restarting Finder (Option+Right-click Finder icon > Relaunch) sometimes clears stuck SMB state.
Error-Specific Troubleshooting Guide
Different error messages point to different root causes. If you are seeing a specific error when trying to access your NAS shared folders, find it below and apply the targeted fix. These are the most commonly reported errors across Synology, QNAP, and Windows forums.
Network Path Not Found (System Error 53)
System error 53 means Windows could not resolve the NAS name or could not establish a connection on TCP port 445. The most common cause is a name resolution failure. Try accessing the NAS by IP address instead of hostname (\\192.168.1.100 instead of \\NAS-Name). If the IP works, you have a NetBIOS or DNS name resolution problem.
To fix name resolution, ensure TCP/IP NetBIOS Helper service is running on Windows. Open Network Adapter Properties > IPv4 Properties > Advanced > WINS tab and enable NetBIOS over TCP/IP. Also verify your NAS workgroup name matches your Windows workgroup exactly. On the NAS side, enable NetBIOS announcement in the SMB settings if the option exists.
Error 0x80004005 (Unspecified Error)
Error 0x80004005 is a generic error that usually indicates a permission or authentication failure. First, clear all NAS-related entries from Windows Credential Manager. Then try accessing the share with explicit credentials using net use \\192.168.1.100\ShareName /user:username password. If this works, the issue is cached credentials.
If clearing credentials does not help, check if the shared folder permissions include your user account. Also verify the folder is not encrypted and unmounted on the NAS. Error 0x80004005 frequently appears when a Synology encrypted shared folder failed to mount after a reboot, which leaves the SMB service running but the share inaccessible.
Permission Denied / Access Denied
Access denied errors mean SMB connected successfully but your user account lacks permission to access the share. Log into the NAS web interface and verify your user has read/write permission on the shared folder. Check both share-level and file-level permissions.
On Synology, also check File Station to see if you can access the folder through the web interface. If File Station works but Windows SMB does not, the SMB service permissions are misconfigured even though the file permissions are correct. Re-check the SMB service settings and restart the service.
Organization Security Policies Block Unauthenticated Guest Access
This error appears when Windows is configured to block guest access and the NAS is offering guest authentication instead of requiring a login. The proper fix is to create a real user account on the NAS and use those credentials for SMB access. Do not disable this security policy on Windows as it protects against certain attack vectors.
If you absolutely must use guest access, open Local Group Policy Editor (gpedit.msc on Windows Pro/Enterprise). Navigate to Computer Configuration > Administrative Templates > Network > Lanman Workstation. Enable the policy Allow insecure guest logons. Note that this reduces security and should only be done on trusted home networks.
Cannot Obtain a List of Shared Folders (Synology Assistant)
This error appears in Synology Assistant when it can detect the NAS but cannot enumerate shares. It typically means the SMB service is running but misconfigured, or there is an authentication mismatch. Restart the SMB service in DSM, verify the workgroup name, and try connecting from File Explorer directly using the IP address.
Advanced Troubleshooting for Stubborn Cases
If none of the standard fixes have resolved your issue, the problem may require deeper intervention. The solutions in this section address edge cases that affect a smaller percentage of users but are notoriously difficult to diagnose. I recommend trying these only after you have worked through the diagnostic checklist, NAS-side fixes, and Windows client fixes above.
NTLM Authentication Level (Windows 11 Specific)
Windows 11 enforces stricter NTLM authentication policies than Windows 10. If your NAS is configured to use an older NTLM version, Windows 11 will reject the authentication silently. Open Local Security Policy (secpol.msc). Navigate to Local Policies > Security Options. Find Network security: LAN Manager authentication level.
Set this to Send NTLMv2 response only. Refuse LM and NTLM. This is the most secure setting that still works with modern NAS systems. If your NAS is older, try Send NTLMv2 response only. Refuse LM. On the NAS side, ensure NTLMv2 is enabled in the SMB advanced settings. The mismatch between Windows expecting NTLMv2 and the NAS offering NTLMv1 is a common cause of SMB failures on Windows 11 that do not occur on Windows 10.
Registry Editor: AllowInsecureGuestAuth
For Windows 10/11 Home users who do not have Group Policy Editor, you can configure guest access through the Registry. Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters. Create or modify the DWORD value AllowInsecureGuestAuth and set it to 1. Restart the Workstation service or reboot.
This allows Windows to send guest credentials to NAS devices configured for guest access. Only do this if you have a specific need for guest access on a trusted network. For most users, creating a proper user account on the NAS is the better approach.
Firewall and Security Software Interference
Beyond QuFirewall on QNAP, check Windows Defender Firewall and any third-party antivirus software. Windows Defender Firewall sometimes blocks outbound SMB traffic on public networks. Open Windows Defender Firewall > Allow an app through firewall and verify File and Printer Sharing is allowed for Private networks.
Third-party antivirus suites like Bitdefender, McAfee, and Norton include network protection modules that can block SMB traffic. Several users on Experts Exchange reported that disabling Bitdefender’s network shield resolved SMB access issues immediately. If you are running third-party security software, try temporarily disabling its network protection module to test whether it is the culprit.
VPN and Subnet Conflicts
If you use a VPN on your Windows machine, it may route SMB traffic through the VPN tunnel instead of your local network. This causes SMB to fail because the NAS is on your local subnet, not the VPN subnet. Check your VPN settings and enable split tunneling or add an exception for your NAS IP address.
Similarly, if your NAS and computer are on different subnets (for example, NAS on 192.168.1.x and computer on 192.168.2.x), SMB discovery protocols may fail even though SMB itself works across subnets. Use direct IP access (\\192.168.1.100) rather than relying on network discovery in multi-subnet environments.
PowerShell SMB Diagnostics
For advanced users, PowerShell offers detailed SMB diagnostics. Run Get-SmbConnection to see active SMB connections. Run Get-SmbClientConfiguration to verify client settings. Run Test-NetConnection -ComputerName 192.168.1.100 -Port 445 to test port connectivity with more detail than telnet. These commands help identify exactly where the SMB negotiation is failing.
FAQ’s
Why am I not able to access a shared folder on my NAS?
Why is my shared folder not accessible even though the NAS is online?
How do I access my NAS shared folder from Windows?
Why is my QNAP NAS not accessible via SMB?
How do I access my NAS web interface?
How do I make a shared folder accessible via LAN?
Can I access my NAS shared folders without using SMB?
Conclusion
When your NAS web interface loads but shared folders won’t open, the problem almost always comes down to the separation between the HTTP web service and the SMB file sharing service. They run on different ports, use different authentication systems, and depend on different layers of configuration. By working through the diagnostic checklist, NAS-side SMB settings, permission verification, and Windows client fixes in this guide, you should be able to identify and resolve the issue without resorting to a factory reset.
The most common fixes, in order of frequency, are clearing stale credentials from Windows Credential Manager, toggling the SMB service off and back on in DSM or QTS, accessing the NAS by IP address instead of hostname, and ensuring the required Windows services (Function Discovery, TCP/IP NetBIOS Helper, Workstation) are running. If you have tried everything in this guide and SMB still fails, check for VPN interference, third-party antivirus network shields, and NTLM authentication mismatches specific to Windows 11.
If all else fails, contact your NAS manufacturer support with the specific error messages you are seeing and the results of the telnet port 445 test. Synology, QNAP, and ASUSTOR all offer direct support channels, and having detailed diagnostic information will help them resolve the issue faster. Most users resolve this problem within the first three fixes, so start with the quick diagnostic checklist and work your way through systematically.