Solved: Odd Duo v2 Read Only Access Problem

[jgrahamiii]

I have a ReadyNAS Due v2 with the 5.3.5 firmware hooked up to a Windows Network. everyone is using Windows XP to access the drive.

There are about 15 users, all of whom need the same access to the shares. We are using "Local Users" for access, not AD. The plan was eventually to add everyone's windows username and password to the ReadyNAS to prevent someone from just plugging in a laptop and seeing all the shares, but so far, only two users, User1 and User2, are set up with usernames and passwords.

The share involved has a checkmark in the Everyone Read/Write box, as well as in Allow Anonymous Access. Further, it has a checkmark in "Automatic Permissions" and all four of the folder/file creation boxes has Read/Write selected. Nothing else is checked off except SMB.

If User3 (anonymous access) creates a file, anyone can open it in read/write mode. However, if User1 (username/password) creates a file, User2 (username/password) can only open it in read only mode. However, User1 and Users3-15 can open read/write mode. Same thing if User 2 creates a file. Everyone but User1 can open in read/write, User1 readonly.

There are no checkmarks under share permissions next to any of the users or groups. Only checkmark here is the Everyone Read/Write.

If I "reset folder permissions), the problem is fixed for all existing files, but any new file created after that has the same issue.

Now I'm afraid to create other usernames. I need everyone to have access to files anyone else creates. Note, the only difference between the two users, if this matters, is that both are primary members of the Users group, and one is also a secondary member of the administrators group.

Any help would be greatly appreciated. -John

[jgrahamiii]

Here's an update. After playing around a bit, I started to look at the Security Tab on the file and folder properties. For a file created by an anonymous user, new files have three permission groups defined -- nobody (Unix User\nobody) -- Full Control,nogroup (Unix Group\nogroup) - Read & Execute, and Everyone - Full Control. groups defined

When a defined user creates a file there are also three groups defined - user1@email.com (NASname\user1) - Full Control, users (Unix Group\users) - Read & Execute, and Everyone Full Control

For both files, the permissions of Everyone are inherited from the drive letter that's mapped to the share. For the other two groups, the permissions are inherited from the folder in which the file is created. If I were to use Dashboard to reset permissions on the share, the file created by User1 would look exactly like the file created by an anonymous user, except nogroup will have full control, and none of the permissions will be inherited.

It appears that the problem I'm experiencing comes from the permission group users (Unix Group/users) having only Read & Execute access. Anyone defined as part of the users group on the NAS cannot read a file created by anyone else in the users group. Am I doing something wrong here? Thanks. -John.

[jgrahamiii]

Found the problem. When I originally created the shares and mapped the drives and copied the files to them, I had the special permissions in Dashboard set to Read Only. This caused the CREATOR GROUP entry in the driver letter to be Read & Execute. I guess this was inherited down the line to the Unix Group/user entry. Fixed that, and it all seems to work fine now. To tell the truth, not sure why, but there are both inherited and non-inherited rights in almost all folders. Very odd. The non-inherited CREATOR GROUP is always READ & EXECUTE, but with the inherited copy of the same group, we get Full Control