As I can see from your description you want to share a directory.
Since you use Windows 8 and I can see the "Security" tab you are using NTFS-filesystem.
It seems like you didn´t configure NTFS-permissions.
- Click on the "Security" Tab of the Folder you want to share.
- Then "Edit..."
- In the new window click "Add..."
- In the new window click "Advanced..."
- In the new window click "Find Now..."
- Select the user who needs the permission to acces the folder.
- Go back to the "Permissions for " dialog.
- Choose the user you added.
- Set permission to "Allow" / Full controll (Or at least read permission)
- Click Apply.
On the sharing tab, the only entry you Need is:
- Everyone
- With permission "Full Controll".
You can manage the permissions with the NTFS-Permissions of the Security Tab.
The rest of the configuration looks correct.
Answer from Andie2302 on Stack ExchangeAs I can see from your description you want to share a directory.
Since you use Windows 8 and I can see the "Security" tab you are using NTFS-filesystem.
It seems like you didn´t configure NTFS-permissions.
- Click on the "Security" Tab of the Folder you want to share.
- Then "Edit..."
- In the new window click "Add..."
- In the new window click "Advanced..."
- In the new window click "Find Now..."
- Select the user who needs the permission to acces the folder.
- Go back to the "Permissions for " dialog.
- Choose the user you added.
- Set permission to "Allow" / Full controll (Or at least read permission)
- Click Apply.
On the sharing tab, the only entry you Need is:
- Everyone
- With permission "Full Controll".
You can manage the permissions with the NTFS-Permissions of the Security Tab.
The rest of the configuration looks correct.
Just a quick heads-up. When using an AD and sharing something to multiple people, using the authenticated users group over the everyone group is slightly more secure.
This is a default group when you do have an AD. It just means that if someone were to plug into a wall outlet they would also need a login that matches with your AD to get to your share.
Access Denied to Share Folder
Access denied for shared folder when it WAS working
access denied while accessing shared folder
SMB File Share Access is Denied HyperV Cluster
Videos
Clear out any cached passwords you have on the client side.
Is this a domain network? If not, and it is workgroup, are you using the same username on the server and client side for logins?
When a workgroup PC authenticates, if you dont specifiy the domain\ in the login then it can actually try to login as a user account on the remote server.
Such that if the computer had user1, and the server had user1… Even though they have separate workgroups, if you had the same password on both computer and server… you’d be able to login between the devices simply as user1 without specifiying the domain/workgroup at all.
The reason that I raise this… Is to query if you are using workgroups, and if so, do both devices have an identical user account and is that account using the same password.
If you have identical accounts but wish to maintain separate passwords, then you must specify the hostname\user when logging in instead of just username on its own.
Also it appears that you’re using a Public network profile. Is this server side? Why?
Servers should be on domain/private network profiles. Public is intended largely for laptops on untrustworthy shared networks like airports/cafe/hotels etc.
When you have your device on a Public profile a whole bunch of services are shut down.
Your screen shots show EVERYONE permissions, its not unusual to have this at the network level as a bunch of dodgy applications dont handle it if you try to be more restrictive. Also share permissions are a rather legacy thing from back in the FAT days.
But you need to be mindful of what your actual filesystem level permissions are on those shares. Do NOT use EVERYONE permissions at the filesystem level. Its just begging for a crypto to come and fuck up your data.
You have displayed the Network Share Permissions, in the RDP session look at the Folder Permissions to make sure everyone has access.
If you have connected previously to the Server (ie with another mapped driive) it may be trying to connect using a different Username Password
Classically, this can be caused by users cutting and pasting files into a share. This means that if the files (at source) were set to not inherit permissions from the parent folder, when they are cut & paste to the destination, they keep their old permissions.
This is not really an answer but further information (can't use comment due to char limit). I'm still trying to understand and solve this issue.
Here's what a "bad" file's permissions looks like in CACLS ( the permissions prevent copying from another machine):
C:\...\Mail\descmap.pce BUILTIN\Administrators:F
NT AUTHORITY\SYSTEM:F
MARS\Tim:F
BUILTIN\Users:R
Here's what a "good" file looks like:
C:\...\Mail\In.mbx Everyone:C
BUILTIN\Administrators:F
NT AUTHORITY\SYSTEM:F
MARS\Tim:F
BUILTIN\Users:R
Here's what the "Mail" (parent) folder's permissions look like:
C:...>cacls mail C:...\Mail Everyone:(OI)(CI)C BUILTIN\Administrators:F BUILTIN\Administrators:(OI)(CI)(IO)F NT AUTHORITY\SYSTEM:F NT AUTHORITY\SYSTEM:(OI)(CI)(IO)F MARS\Guest:F CREATOR OWNER:(OI)(CI)(IO)F BUILTIN\Users:R BUILTIN\Users:(OI)(CI)(IO)(special access:) GENERIC_READ GENERIC_EXECUTE BUILTIN\Users:(CI)(special access:) FILE_APPEND_DATA BUILTIN\Users:(CI)(special access:) FILE_WRITE_DATA
The "Everyone:C" and the "BUILTIN\Administrators:F" attributes somehow get removed from the problem files. Different files are affected at different times. There doesn't seem to be any consistency.
Hello Vencel,
This issue is caused by a mismatch between NTFS permissions on the HDD and the share permissions. Even if “Everyone” has full control on the share, the NTFS security on the drive must also grant access to the same user or group. When you test locally, the server account context is used, which is why it works there but fails remotely.
Check the drive’s Properties > Security tab and ensure the specific user or group has at least Read permissions. Add the account explicitly rather than relying on “Everyone,” since newer Windows Server versions don’t include authenticated users in that group. Then verify the share permissions under Advanced Sharing > Permissions match the NTFS rights. The most restrictive setting always applies.
From the client, confirm authentication with net use \\servername\sharename /user:domain\username. If login fails, the account may not exist or be disabled. Also review SMB settings and firewall rules, as Windows Server 2025 enforces SMB signing/encryption that can block older clients. Event Viewer under Security and SMBServer logs will show if policy is rejecting the connection.
Aligning NTFS and share permissions, confirming authentication, and checking SMB policies should resolve the access denied error without using the administrator account.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
Harry.
This worked: https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/cannot-logon-access-administrative-share
I have this same issue, and found a workaround/fix:
Machine: Windows 10 21H2
Office: 365 Apps for enterprise
Powerpoint: Version 2302 (Build 16130.20218 c2r)
Dell: HP wolf software is not involved.
In our case, the symptoms were as follows:
Error "You do not have access to view this file. Would you like to request permission on Sharepoint?" occurs when opening Powerpoint files through folder redirection.
Affected folder was on desktop.
Folder preview was enabled.
The fix I found was:
- Disable the preview pane in File Explorer (View > click Preview Pane to turn it off.)
As soon as I turned of the preview pane, the issue stopped happening. I tested multiple times turning the preview pane on and off, and it consistently stopped the issue from occurring.
Just experienced this issue for a user on a local domain. Any files from the subdirectories of a particular mapped drive for the user were throwing errors. PDF files firing 'Access Denied' when opened on the user's machine, Office files saying "Access denied you do not have access to view this file would you like to request for permission on SharePoint". Checked on the fileserver and the user is indeed the owner on this particular directory and has all necessary permissions to access the share and Read/Write.
What ended up fixing was repropagating the ownership of the directory to the user, adding the user into the advanced share permissions (even though everyone has read/write access on this particular folder).
I got a second laptop and want to transfer files by sharing folder from first laptop. Both laptops are Win 10.
I have read articles and followed this video https://www.youtube.com/watch?v=3-C3v82zOgE, BUT sharing option is greyed out: https://i.imgur.com/r4iX9iZ.png , so I used the "Advanced sharing options" with these permissions set to "Everyone" "Read".
On second laptop I can see shared folder, but when I double click the folder I get the message:
Windows cannot access \shared\folder. You do not have permission. Contact network administrator
I have followed solutions from this thread : https://answers.microsoft.com/en-us/windows/forum/all/you-do-not-have-permission-to-access-pcname/704f39f0-a03e-4f1c-bead-a45df97e455d
but nothing is working.
Do you have any idea?
UPDATE: to make "Share" button not greyed out you have to enable "Sharing wizard" in "Folder and search options"