Strange Access issues on Windows Server 2022 share

Question

Hi,

I have setup a new Windows Server 2022 and shared my first folder.
I joined one PC to the domain and all is good so far.
However, the user can see the folder on the server if I access \domain however it is showing an empty folder. However if I map it to the PC it does show the files. This is ok with me.
But the strange thing is that if I click on any file in this folder (these are all PDF Files) than it tells me the file does not exist. But I can copy it to my PC and than nopen it no problem. I can also copy files i9nto the shared folder and can then access them. I have set the permissions to everyone with full access but still I cant access the existing files.
This drive was previously in a Server 2016 and I now connected it to the new server.
I did also try to reset the drive permissions with icacls to see if this works.
in the share the owner is administrator, everyone Read/Write, my user account read/write still cant open any pdf. It says "file not found"

Any ideas what the issue could be on this?

Best wishes,
Thomas

Answer 1

File shares have 2 levels of access. The file share itself defines who can access the file share and what they can do. Please confirm that you have configured the share to allow read access to the files on the share.

The second level is on the file system itself. The NTFS permissions apply if the user can access the share. You also need to ensure that anyone accessing the share also has read permissions to the folder (and subfolders) of the share. Based upon your description it almost sounds like they have read file rights but not list rights to the directory which I didn't even think was possible. In the NTFS permissions UI go to the Effective Access tab under the Advanced settings and type in the name of the user attempting to use the share. Confirm they have all the necessary read rights to the folder and subfolders. I wonder if maybe they only have root folder access.

Answer 2

I am sorry, this was not a issue with the server. I noticed than when I added a other application or text document into the folder, all was working perfect. In the end it was a security setting in Adobe Acrobat that had the issue. Took me a day to figure this out ;-)

Thank you for the help.