Folder Permissions vs File Permissions

[Matt Bruce]

Hi All,

I have a problem that I was hoping could be resolved with
some advice from you folks. I have been going nuts trying
to set up permissions that will allow our users to create,
rename, delete, copy, move, append files but NOT the
folders they are in nor do I want them to be able to
create folders. The basic idea is that we want to set up a
folder structure that is unchangeable by the users
(including them not being allowed to create their own
folders). I have been trying to use special permissions to
do so but even if I apply read only permissions to "this
folder only" it still affects the files within that
folder...any ideas?

Thanks for your help,

M. Bruce

 

[Steven L Umbach]

Try this. Give them read/list/execute permissions for the folder.
Then go into advanced/add select the same group. In apply onto select "files
only". Then check off everything but the last two for allow - change
permissions and take ownership. Then hit OK. When your are back in other
window hit apply and then OK. You should see your group listed twice in
advanced permissions - once for folder only and once for files only. Test it
out and see if it helps. --- Steve

 

[Matt Bruce]

I tried that and other methods and they work fine on a
windows 2000 workstation when dealing with local
folders/files. The problem is that our file server is an
NT build while our workstations are windows 2K. I know
that NT does not support the special permissions that
Win2K does which is what, I think, is causing the problem.
When I implement the special permissions on the network,
users are getting access denied messages (even though they
do have modify perms for files, read only for the folder)
and then their files are being deleted by the server! Not
even an option to save as. Anyone have any ideas to get
around this?