Originally posted by jh31480
so it would be chmod -R 770 (whatever folder).. this is great and all, however, while the linux side clearly shows that group has read write and execute access.. i can't get any users to actually open the folder or create anything in the folder
Ok, so setting rwx permissions for the group on a folder will allow those users to read the contents of that folder, navigate to it, and create files. However, all of those abilities are broken if there is any directory
in the path that does not allow both read and execute permissions for the users. An example might illustrate what I'm saying. Suppose you have this directory:
owner=root,group=AD, 770: /system/backup/windows
So now root and users in group AD should
be able to do anything their hearts desire in that directory. However, throw this into the mix:
owner=root,group=admin, 770: /system/backup
All of a sudden the chain is broken, and AD users are left in the cold. For the /system/backup directory, users in the AD group fall into the "others" category regarding permissions. And those permissions are 0 (no read, no write, no execute). It no longer matters what permissions are on /system/backup/windows, because the AD users can't get through /system/backup. To access /system/backup/windows, the users in group AD need read and execute permissions on every directory in the path. So /system needs to give them rx and /system/backup needs to give them rx.
Double check those permissions and see if you're falling into that trap.