Question Locked

windows server 2k3 permission problems

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Right now, I have a remote desktop user that need access to a specific folder nested within other folders. This is my current setup.

H:\hello\world\
Permissions are handled using groups.
I want user 1 to have access to the "world" folder, but no access to the "hello" folder. Currently I am able to use a shortcut to "h:\hello\world\" which will allow User into the folder and list contents. User cannot go up a level nor can User access h:\.

User is not apart of any groups that have access to other parts of this drive, and is only apart of the "remote users" group which grants User access via mstsc.

Currently User can view contents as well as contents of all subfolders within "world," create new folders and new files with default names (ie, "new folder," or "new text document.txt"). However, User is not able to rename folders, move folders, or rename files.

I disabled inherited permissions on the "World" folder, and added User to the access list. User has modify permissions, but even when I give User full access, the same problem persists.

how do I solve this problem? I need User to be able to move folders around and rename newly created files.

3 replies

by nimmo

Hopefully this will point you in the right direction.

All you need to remember about permissions is that the most restrictive apply.

You have file sharing permissions and NTFS permissions, it is recommended that you set restrictions at the NTFS level because they are more granular.

Also to make life easier you should try where possible to assign the NTFS permissions to groups rather than individuals.

This way you can simply modify the group's rather than every user.

References that may help:

http://www.windowsecurity.com/articles/Understanding-Windows-NTFS-Permissions.html

http://www.windowsecurity.com/articles/Share-Permissions.html

by 45geek

sounds like your problem resides in the "hello" parent folder. You might want to make sure that the "inherant permissions" check box is not checked in the Hello parent folder also this user will have to have "List folder contents" access to the parent folder. Plus from what you discribe you will have to use NTFS permissions for this user only for this file. You might want to create a seperate group for this user that allows the permissions for this folder. But most importantly if the user isn't allowed to "walk through" the parent folder they will have no permissions no granted them by the parent folder. Another solution is to do a restricted share for this folder for this user with a global(universal) user profile, but if you do this it is better to make it a parent folder allow access and restrict the children it is easier to restrict the children than to walk through a parent with more access to the children. Hope that helps.

This discussion is closed to new replies.