Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

"Access is denied" or "You do not have permission to access \\server\share" on an SMB share (System error 5)

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Microsoft's page "Access Denied when you access an SMB file share in Windows" lists six causes for this fault, and says that most modern cases come from security defaults that changed, not from misconfiguration. Starting with Windows 11, version 24H2 and Windows Server 2025, several SMB security features are enforced by default, so if Access Denied began after an upgrade and the share used to work, check those changes first.

The six causes are: unauthenticated guest access blocked, SMB signing required but not supported by the target, NTLM blocked or unavailable, repeated failures throttled by the authentication rate limiter, a share or NTFS permission mismatch, and a missing SYNCHRONIZE entry on a NetApp or similar server. The checks below separate them without changing anything.

What the error means

Microsoft's page gives these symptoms when you connect to a shared folder on a Windows file server, a third-party device or a NAS: "Access is denied." or "You do not have permission to access \\server\share." or "You can't access this shared folder because your organization's security policies block unauthenticated guest access." The mapping can fail with System error 5 from net use, or with status codes such as 0x80070035 (network path not found) or STATUS_ACCESS_DENIED (0xC0000022).

Microsoft's table of behaviour changes lists what applies from which version. Insecure guest access is disabled from Windows 10 1709, Windows 11 and Windows Server, with SMBClient event 31017. SMB signing is required, inbound and outbound, from Windows 11 24H2 and Windows Server 2025, and connections to devices that do not support signing are rejected. NTLM blocking is available on Windows 11 24H2, and its symptom is Access Denied to IP-address, workgroup or NAS targets where Kerberos is not available. The authentication rate limiter delays repeated failed sign-ins by about 2 seconds, which Microsoft says can look like lockout or slowness.

Microsoft's signing page is more specific about which edition does what: "Windows 11, version 24H2 Enterprise, Pro, and Education require both outbound and inbound SMB signing", "Windows Server 2025 requires outbound SMB signing only", and "Windows 11, version 24H2 Home edition doesn't require outbound or inbound SMB signing."

Likely causes

Cause What you see How to confirm
Unauthenticated guest access blocked The message mentions "unauthenticated guest access" SMBClient event ID 31017
Signing required and the target does not support it A third-party server or NAS, and a client on Windows 11 24H2 or Server 2025 Microsoft's signing page lists 0xc000a000 and STATUS_INVALID_SIGNATURE, "The cryptographic signature is invalid."
NTLM blocked or unavailable Connecting by IP address, to a workgroup device or to a NAS where Kerberos cannot be used, on a client with SMB NTLM blocking configured The Block NTLM setting; the target is addressed by IP
Authentication rate limiter Intermittent Access Denied or slow authentication after several failed sign-ins Failed sign-in attempts in the same period; server version (see below)
Share or NTFS permission mismatch One user or group is denied while others succeed, or folders are hidden Both share and NTFS permissions, and Access-Based Enumeration
Missing SYNCHRONIZE entry Access denied through SMB2 to a folder on a NetApp Filer or other SMB2 server Network trace shows a DesiredAccess failure on the SMB2 CREATE for the folder

One version detail differs between Microsoft's pages. The Access Denied page gives the rate limiter as "Windows Server 2022+" in its table. The rate limiter page says the feature is enabled by default beginning with Windows Server 2025 and Windows 11, version 24H2, and lists those as its prerequisites. Check the actual server version before you blame the limiter.

Prove the cause before changing anything

Microsoft's page gives three read-only commands for the SMB client. Run them on the client that fails:

net use
Get-SmbConnection
Get-SmbClientConfiguration

net use shows what error and target are involved. Get-SmbConnection shows existing or attempted SMB sessions and the dialect. Get-SmbClientConfiguration shows the client's security posture: signing, guest, NTLM and encryption.

Then open Event Viewer and go to Applications and Services Logs, Microsoft, Windows, SMBClient. Microsoft names both the Connectivity and Security channels and says the event ID and message point directly to the causes it lists.

Work through the causes in this order:

  1. Read the message. If it mentions unauthenticated guest access, or event 31017 is present, it is the guest cause.
  2. Note whether the target is on a third-party server or NAS and whether the client is Windows 11 24H2 or Windows Server 2025. If so, signing is a candidate.
  3. Note whether you connect by IP address or to a workgroup device. Microsoft's signing page also recommends using Kerberos instead of NTLMv2 and not connecting to shares by IP address.
  4. Check both share and NTFS permissions for the user, and Access-Based Enumeration.

Example (illustrative): at contoso.com.au, a laptop lt22 on Windows 11 24H2 maps \\10.0.20.50\finance on a network storage box, and net use fails with System error 5. The same user has no trouble on \\fs01\finance. The failing path is an IP address. Get-SmbClientConfiguration shows NTLM blocking switched on by policy, and the NAS is not joined to the domain. That matches Microsoft's NTLM cause.

Fix

Take one cause at a time and test after each.

Guest access blocked

Microsoft's resolution: "Connect with valid credentials to the server or NAS instead of relying on guest access." It warns not to re-enable insecure guest logons as a fix except as a temporary, risk-accepted workaround, because it exposes the client to rogue-server and man-in-the-middle attacks. The details and the discouraged policy override are on Microsoft's guest-logon page.

Signing required, target does not support it

Microsoft's resolution is to enable SMB signing on the server or NAS, which is its preferred route. If the device cannot support signing, Microsoft says to evaluate the security impact before changing the client requirement. Its signing page says "We don't recommend disabling SMB signing as a workaround for third-party servers." This is a change on the server or device and belongs to whoever runs it.

NTLM blocked

Microsoft's resolution: connect by the server's Kerberos-capable name (FQDN) rather than by IP, make sure name resolution and service principal names are correct, or configure an NTLM exception list for required legacy targets. Microsoft's NTLM page describes the exception list as a Group Policy setting, "Block NTLM Server Exception List" under Computer Configuration, Administrative Templates, Network, Lanman Workstation, that holds IP addresses, NetBIOS names or FQDNs. Microsoft's page gives the steps; they change security for the whole client, so they belong to whoever manages that policy. Connecting by FQDN changes nothing on the machine.

Rate limiter

Microsoft's resolution is to fix the underlying bad-credential or mapping problem, and to adjust or disable the limiter only for a legitimate high-volume scenario. Microsoft's limiter page documents a PowerShell setting and a Group Policy setting for it, and the steps belong to whoever manages that policy. Microsoft describes the limiter as a defence against brute force password guessing, so the first job is to find the failing credential.

Share or NTFS permission mismatch

Verify that both share and NTFS (Security) permissions grant the user the access needed, and check Access-Based Enumeration. Microsoft points to its page on shared folders in File Explorer for the steps.

Missing SYNCHRONIZE entry (NetApp Filer or other SMB2 server)

Microsoft's fix is to grant permissions that include the Synchronize bit with ICACLS. First save the folder's current permissions to a new file. Create C:\Temp first if it does not exist. In the commands below, <folder> is the full path of the folder as you reach it through the share:

icacls <folder> /save C:\Temp\<foldername>-acl-before.txt

Risk: the next command changes the permissions on one folder, adding rights for one user or group. Anyone relying on the folder's existing permission set could see a different result.

icacls <folder> /grant <domain>\<user>:(RC,RD,REA,RA,X,S)

Microsoft's page explains the rights: RC read control, RD read data or list directory, REA read extended attributes, RA read attributes, X execute or traverse, S synchronize. The ICACLS page says /grant without :r adds to previously granted explicit permissions.

To undo it: restore the saved permissions. The ICACLS page's example applies /restore to the directory that contains the saved items, so use the parent of the folder:

icacls <parent directory of the folder> /restore C:\Temp\<foldername>-acl-before.txt

To verify, Microsoft's page uses AccessChk, a separate Sysinternals tool that the page links to and that is not part of Windows: accesschk.exe -ld <folder> should list SYNCHRONIZE.

Confirm the fix

  • The same net use mapping succeeds.
  • Get-SmbConnection shows the session and the dialect.
  • The SMBClient events you saw before no longer appear after a new attempt.

What to watch afterwards

  • Upgrades to Windows 11 24H2 and Windows Server 2025, because Microsoft says several SMB security features are enforced by default there.
  • Third-party NAS devices that share a folder. Microsoft's pages say to enable SMB signing on the server, and to evaluate the security impact before turning signing off on the client.
  • Logs on the server side. Microsoft's data-collection step asks for the SMBClient and, on the server, SMBServer event logs for the repro window.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's Access Denied page says "Supported versions of Windows Client" and gives its causes in a decision list; it does not say how many cases each explains, and it does not cover every cause of Access Denied, such as an expired account. Its page gives the SYNCHRONIZE case only for NetApp Filers and other SMB2 servers. ICACLS changes permissions, so save them first, use a new file name for each folder so that no saved copy is overwritten, and change one folder at a time. Microsoft's pages describe the rate limiter version differently, so confirm the server version before you adjust any limit.

Sources