Users are not able to modify NTFS files and folders on File Server
We have a shared drive set up via NTFS but users are not able to save to that drive. The top level drive called 'E:\staff' with the following permissions for "Domain Users":
(This folder, subfolders and files) Traverse folder/List folder/read data/ Read attributes/create files/write data/create folders/append data (not inherited). Users are able to see inside the 'Staff' folder but can only access folders that they have permissions to within that folder as it should be.
However, users are not able to modify anything within the folder that they have 'modify' permissions to.
Example: Karen has modify permissions on E:\staff\Billing but once she is in the Billing folder, she cannot add, modify or remove anything within the 'Billing' folder.
I have tried this 100 different ways and I know that I am overlooking a step but not sure what that is. Thanks
Permission-Error.png
(This folder, subfolders and files) Traverse folder/List folder/read data/ Read attributes/create files/write data/create folders/append data (not inherited). Users are able to see inside the 'Staff' folder but can only access folders that they have permissions to within that folder as it should be.
However, users are not able to modify anything within the folder that they have 'modify' permissions to.
Example: Karen has modify permissions on E:\staff\Billing but once she is in the Billing folder, she cannot add, modify or remove anything within the 'Billing' folder.
I have tried this 100 different ways and I know that I am overlooking a step but not sure what that is. Thanks
Permission-Error.png
Probably a read only permission on the share itself, switch that to full control
ASKER
Nope, on the shared folder that they have access to, they have modify. On the upper level, it is set to "Domain User" with Traverse folder/List folder/read data/ Read attributes/create files/write data/create folders/append data (not inherited. Are you saying to set the "Domain User" to full?
Hi,
when setting up shared folder, it is always easier to set Full Access on share folder, for either everyone, or domain users and such, and then to tweak permissions via NTFS permissions (Security tab).
That way you will always know that problem is with NTFS permissions and not bother your self with "where is the problem thing" :)
PS: Users coming via network will always be limited via NTFS permissions, no metter what type of permissions then have on Shared Folder permissions..
Regards,
Ivan.
when setting up shared folder, it is always easier to set Full Access on share folder, for either everyone, or domain users and such, and then to tweak permissions via NTFS permissions (Security tab).
That way you will always know that problem is with NTFS permissions and not bother your self with "where is the problem thing" :)
PS: Users coming via network will always be limited via NTFS permissions, no metter what type of permissions then have on Shared Folder permissions..
Regards,
Ivan.
ASKER
Thanks, yes, it is already set to Full Access on share folder for everyone. Is it possible to have the NTSF system corrupt? If so, how would you check/know?
To diagnostic:
From the server, right click on billing -> properties -> tab security -> bt advanced -> tab effective access
Select user to test: Karen click bt: View Effective Access.
Then if it appears good, try the same from the workstation
From the server, right click on billing -> properties -> tab security -> bt advanced -> tab effective access
Select user to test: Karen click bt: View Effective Access.
Then if it appears good, try the same from the workstation
Is it possible to have the NTSF system corrupt?it is highly unlikely, but you test for that condition witch chkdsk
Traverse folder/List folder/read data/ Read attributes/create files/write data/create folders/append data (not inherited. You are missing modify which implies delete permissions
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Didn't fix the issue. Workaround was to use VMWARE, create another server, move the data and added the permissions (worked).