Fix SMB File Share Access Denied on Windows Server 2025

Updated on Nov 17, 2026
Mila H
7 MINS READ
Table of Contents
SMB Access Denied on Windows Server 2025

Windows Server 2025 SMB access denied errors usually come from share permissions, NTFS permissions, a wrong sign-in, blocked guest access, or a firewall issue. This guide builds a test share and checks each cause in order.

New SMB Defaults in Windows Server 2025

Windows Server 2025 has stricter SMB rules than older versions, so errors are more common after an upgrade. SMB signing is now required by default for outbound connections. Also, guest access stops working when signing is required. A setup that worked on Server 2019 can fail here.

Every test below uses these example names. Change them to match your server:

  • Server name: SRV01
  • Folder: D:\Shares\Finance
  • Share name: Finance
  • Groups: FinanceRW (can edit) and FinanceRO (read-only)
  • Test user: mila

Create a Test SMB Share With Least Privilege

Before we fix an error, we create a test share. Then, you know the setup is correct, and any Windows Server 2025 SMB access denied error you see has a real cause. 

Open PowerShell as Administrator on the server, and run:

PowerShell
Install-WindowsFeature FS-FileServerNew-Item -Path D:\Shares\Finance -ItemType DirectoryNew-LocalGroup -Name FinanceRWNew-LocalGroup -Name FinanceROAdd-LocalGroupMember -Group FinanceRW -Member mila

Now create the share. Give access to the two groups only, and don't add Everyone:

PowerShell
New-SmbShare -Name Finance -Path D:\Shares\Finance `  -ChangeAccess "SRV01\FinanceRW" `  -ReadAccess "SRV01\FinanceRO" `  -FolderEnumerationMode AccessBased

Next, set the NTFS permissions. This removes the old permissions from the parent folder and adds only the access each group needs:

PowerShell
icacls D:\Shares\Finance /inheritance:ricacls D:\Shares\Finance /grant "Administrators:(OI)(CI)F" "SYSTEM:(OI)(CI)F" "SRV01\FinanceRW:(OI)(CI)M" "SRV01\FinanceRO:(OI)(CI)RX"

This gives you a simple least-privilege model:

  • FinanceRW gets Change on the share and Modify on NTFS.
  • FinanceRO gets Read on the share and Read and Execute on NTFS.
  • Administrators and SYSTEM keep Full Control on NTFS only.
  • Everyone else gets nothing.

Share vs NTFS Permissions: What's the Difference?

A user must pass two checks, which are the share permission and the NTFS permission. If either one blocks the user, you get Windows Server 2025 SMB access denied messages. The stricter permission wins. For example, if the share gives Full Control but NTFS gives only Read, the user can only read. A mismatch between the two is a common cause when only some users are denied.

You can check the share rights with the commands below:

PowerShell
Get-SmbShare -Name FinanceGet-SmbShareAccess -Name Finance

You can check the NTFS rights with the command below:

PowerShell
icacls D:\Shares\Finance

A "Deny" entry always wins over an "Allow" entry. If you find one, you must remove it. Also, check that the user is in the right group. A new group membership only works after the user signs out and signs in again.

Check Effective Access for a User

Don't guess when you debug Windows Server 2025 SMB access denied errors. Let Windows show you what one user can really do:

  1. Right-click the folder and open Properties.
  2. Go to Security, then Advanced.
  3. Open the Effective Access tab.
  4. Click Select a user, pick mila, and click View effective access.

This tab shows NTFS rights only, not share rights. If a needed right is missing, fix it in NTFS. Then, run Get-SmbShareAccess -Name Finance to check the share rights.

Troubleshoot Windows Server 2025 SMB Access Denied

If your permissions are correct, the problem is usually in how the connection is made. The cause can be an old saved login, blocked guest access, or a new signing rule. It can also be a closed port or the wrong network profile.

Check these things in order, and stop when one fixes the error.

Fix Share Access Errors Caused by Sign-In Problems

Many cases of Windows Server 2025 SMB access denied come from the wrong account, not the wrong permission. On the client, list the open connections and clear old ones:

PowerShell
Get-SmbConnectionnet use * /deletecmdkey /listcmdkey /delete:SRV01klist purge

Then, connect again with a full username:

PowerShell
net use \\SRV01\Finance /user:SRV01\mila *

Windows allows only one set of credentials per server for each session. If you see error 1219, an old connection is still open. Delete it and try again.

For a workgroup server, always use SERVERNAME\username. For a domain, use DOMAIN\username. If the account has a blank password, remote sign-in may fail, so you must set a password.

Also, you must check the logs on both sides in the Event Viewer:

  • On the server: open Applications and Services Logs > Microsoft > Windows > SMBServer > Security.
  • On the client: open Applications and Services Logs > Microsoft > Windows > SMBClient > Security.

Fix Guest Logon and SMB Signing Errors

Guest access means no user name and no password. Windows blocks it by default, which is a top cause of Windows Server 2025 SMB access denied on new servers. Signing and guest access cannot work together. If signing is required, a guest sign-in fails.

You can check the client settings with the commands below:

PowerShell
Get-SmbClientConfiguration | Select EnableInsecureGuestLogons, RequireSecuritySignatureGet-SmbServerConfiguration | Select RequireSecuritySignature, EnableSecuritySignature

The best fix is to stop using guest access and sign in with a real account. Avoid turning on insecure guest logons. Use them only for a short test, and only if you accept the risk.

If the error says "unauthenticated guest access", look for Event ID 31017 in the SMBClient log.

If the other device is a NAS or a third-party device, turn on SMB signing. If it can't sign, you can lower the setting on the Windows client. This is less safe, so do it only if you accept the risk.

Windows Server 2025 can also block NTLM for outbound SMB. This setting is off by default. If a policy turned it on, a connection by IP address can fail. IP connections can't use Kerberos, so they fall back to NTLM. You can test with the server name instead:

PowerShell
Get-SmbClientConfiguration | Select BlockNTLM

Check Firewall and Network Profile

The problem may not be a permission problem. If the port is blocked, you usually see "network path not found" instead of "access denied". You must test it anyway. Run this on the client:

PowerShell
Test-NetConnection -ComputerName SRV01 -Port 445

You should see TcpTestSucceeded : True. If it is False, check the server:

PowerShell
Get-NetConnectionProfileGet-NetFirewallRule -DisplayGroup "File and Printer Sharing" | Select DisplayName, Enabled, ProfileEnable-NetFirewallRule -DisplayGroup "File and Printer Sharing"Get-SmbServerConfiguration | Select EnableSMB2Protocol

If the profile is Public, you can change it to Private. Do this only on a network you trust:

PowerShell
Set-NetConnectionProfile -InterfaceAlias "Ethernet" -NetworkCategory Private

Also, on a cloud server, you must check the provider firewall. Open port 445 only between the two machines. Never open SMB to the whole internet. A private network or a VPN is safer.

To test this setup, you can use a Windows VPS with Windows Server 2025. You get web console access if a firewall change locks you out. Also, you can reinstall the server from the panel to start clean.

SMB Access Denied Troubleshooting Checklist

Use this checklist when you don't know where the problem is. Each step tests one cause and tells you what to do next. Go in order and stop when the error is fixed.

Step What to Run or Check If It Fails or Is Wrong If It Passes
1 Test-NetConnection SRV01 -Port 445 Fix DNS, the firewall, the network profile, or the provider firewall. Go to step 2.
2 Get-SmbShare -Name Finance If the share is missing, create it. Go to step 3.
3 Get-SmbShareAccess -Name Finance If the user or group has no rights, add them. Go to step 4.
4 icacls and the Effective Access tab If a right is missing or a Deny entry exists, fix it. Go to step 5.
5 On the client: net use * /delete, cmdkey /list, klist purge. Then connect again with SRV01\alice. If it still fails, go to step 6. The cause was cached credentials.
6 Read the SMBClient Security log. Event ID 31017: stop using guest access. Signing error: turn on signing on the other device. NTLM issue: connect by server name or check the Block NTLM setting. Go to step 7.
7 Check Access-Based Enumeration if the share is visible, but the folder is empty or hidden. Users only see files they can read, so fix their read rights. The issue is solved.

Conclusion

SMB access denied errors look complicated, but the cause is usually simple. Start with the network, then check share permissions, NTFS permissions, and saved logins. After that, look at guest access and signing. Use groups and give each one only the access it needs, so problems are easy to find and the server stays safe. 

If you need full control over disks and the network for bigger file loads, a private dedicated server is a good option.