NAS Codex › Synology › Can't access a Synology shared folder via SMB: what Synology says to check

Can't access a Synology shared folder via SMB: what Synology says to check

A shared folder on a Synology NAS will not open over SMB from a Windows PC or a Mac. Synology's Knowledge Center has a troubleshooting article for this, and two more for specific cases: access lost right after updating to DSM 7, and Windows reporting "System error 53 has occurred. The network path was not found." This page collects what those three articles say, NAS side first.

Written against: Synology Knowledge Center articles for DSM 7 series, DSM legacy versions and DSM Enterprise (PAS). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.

Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.

Fast Answer

Check Control Panel > File Services has SMB enabled, the user has the SMB privilege in Control Panel > Application Privileges and permission on the shared folder, the firewall is not blocking ports 137-139 and 445, and the PC is not on the block list in Control Panel > Security > Protection. On Windows, remove the NAS's saved credentials in Credential Manager, avoid Windows Hello sign-in, close File Explorer and run net use * /delete /y. If access stopped right after updating to DSM 7, Log Center may show "NTLMv1 not permitted".

On the Synology NAS

Synology's troubleshooting article for a shared folder that cannot be accessed via SMB or AFP says to confirm each of these:

On SMB versions, Synology notes that SMB1 has been disabled by default since Windows 10 version 1709, so the minimum should be SMB2 for Windows 10 PCs. Some legacy systems and devices, such as Windows XP, multi-function printers, IP cameras and network media players, only support SMB1.

On a Windows PC

  1. Avoid signing in to Windows with Windows Hello if you want to use SMB file services.
  2. Try mapping the network drive with Synology Assistant.
  3. Reset the saved credentials: in Control Panel > User Accounts > Credential Manager > Windows Credentials, remove every saved credential for the NAS (its IP address and server name), then connect again. If the list is already empty and you still cannot connect, use Add a Windows credential with the NAS's IP address or server name, user name and password.
  4. Connect by both the IP address and the server name in File Explorer. If the IP address works but the name does not, run ping with the server name and check that the address after "Reply from" matches the NAS. If it does not, run nbtstat -R or restart the PC.
  5. Make sure no one else is connected to the NAS from the same PC under a different name.
  6. Close all File Explorer windows and run net use * /delete /y to remove all mapped drives, then set them up again.

Synology also notes that File Explorer cannot connect by UNC path to a shared folder whose name ends in a dot. If the NAS is joined to a domain, try another account type; a local user signs in by adding localhost\ before the user name.

On a Mac

Synology says to connect through Finder > Go > Connect to Server with smb:// and the NAS's IP address (SMB is recommended for macOS 11 and above), disconnect any unresponsive connections to the NAS from the Finder sidebar, use Force Quit to restart Finder, or restart the Mac. If the user name has lowercase letters with umlauts, such as ä, ö or ü, and SMB sign-in fails, replace them with uppercase letters (for example "Käte" to "KÄte"): Synology explains that SMB NTLMv2 converts them to uppercase and Macs cannot do this conversion correctly.

Access lost right after updating to DSM 7

Synology has a separate article for this. The Connection Log in Log Center shows an entry saying the user failed to log in via SMB due to "NTLMv1 not permitted". Starting with DSM 7.0, NTLMv1 authentication is deactivated for security reasons and only NTLMv2 is allowed. The clients affected are Windows computers that support SMB1 but do not allow NTLMv2, and legacy devices that only support SMB1 without NTLMv2, such as IP cameras, multi-functional printers and multimedia players.

Synology highly recommends upgrading to Windows 10 or later and using SMB2 or SMB3. If you understand the risks and must keep SMB1, set the minimum SMB protocol to SMB1 in Control Panel > File Services > SMB > Advanced Settings, then either change Windows to NTLMv2 (in secpol.msc, set Network security: LAN Manager authentication level to "Send NTLMv2 response only\ refuse LM & NTLM" and restart) or, as a last resort for legacy devices, tick Enable NTLMv1 Authentication under Advanced Settings > Others. Synology warns that both lower security, and notes that Windows Home edition does not provide secpol.msc.

"System error 53 has occurred. The network path was not found."

For this Windows error, shown when connecting through Synology Assistant or with net use, Synology says to:

  1. Ping the NAS's IP address from Command Prompt. If there is no reply, or the PC and NAS are not in the same LAN, check with your network administrator.
  2. Make sure Client for Microsoft Networks is ticked in the Ethernet adapter's properties (in Windows 10: Settings > Network & Internet > Change adapter options).
  3. Make sure the group policy Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers is not set to Deny All. On a personal PC, check it in gpedit.msc; on a domain, in Group Policy Management on the domain controller.
  4. For net use, close all File Explorer windows, run net use * /d /y, and try the net use command again.
  5. Try connecting the PC to a Windows file server. If the error remains, Synology says the problem is with the client computer.

When to stop and get help

Do not open SMB to the internet as a quick fix: Synology says exposing network ports has security risks and recommends a VPN. If you must forward SMB ports, it says to set the minimum to SMB2, the maximum to SMB3 and Transport encryption mode to Force. If the NAS itself cannot be found on the network, see NAS not found on the local network.

Questions

Why can't I access my Synology shared folder over SMB?

Synology says to check SMB is enabled in File Services, the user has the SMB application privilege and folder permission, the firewall allows ports 137-139 and 445, the PC is not on the auto block list, and the SMB versions suit the client.

I lost SMB access after updating to DSM 7. Why?

Synology says DSM 7.0 deactivates NTLMv1 and allows only NTLMv2. Log Center shows NTLMv1 not permitted. Upgrade Windows and use SMB2 or SMB3; as a last resort for legacy devices, Enable NTLMv1 Authentication lowers security.

How do I fix System error 53 with a Synology NAS?

Synology says to ping the NAS, make sure Client for Microsoft Networks is enabled, check the Restrict NTLM outgoing traffic policy is not Deny All, and rerun net use after net use * /d /y. If a Windows file server fails too, the PC is the problem.

Sources

Every fact on this page comes from the vendor documents below, opened on 2026-11-17.