Problem with READ only permissions

Hello Guys,

This problem has recently become apparent on my ReadyNAS 1100:

I configured share and folder permissions as recommended in Post http://www.readynas.com/?p=1987 ('Setting up Active Directory folder permissions on the ReadyNAS') and, for the sake of completeness, I even created the same folder structure as outlined in this document.

I created two AD user accounts: User1 and User2.

I also created the following AD security groups (in place of the Sales group used as an example in the document): ProtectedFolderAccess_DLG (Domain Local Group) and ProtectedFolderAccess_GG (Global Group) as per Microsoft best practices.

ProtectedFolderAccess_DLG was added to the ACL of the \\nas1\data\protected folder with Allow-Full permissions.

ProtectedFolderAccess_GG was made a member of ProtectedFolderAccess_DLG.

User1 and User2 were added as members of ProtectedFolderAccess_GG.

Now here's what happens:

I log-on to a client machine as User1 and can access the \\nas1\data\protected folder fine. I create a new Word Document and save it as TestDoc.doc.

I view the ACL for this word document and can see that User1 is the owner and has full control. I can also see that the ProtectedFolderAccess_DLG group has full control. ALL GOOD.

I log off the client machine and log back on as User2. I access the \\nas1\data\protected folder and open up TestDoc.doc fine. I make some changes to the document and can save the changes without any problems.

However, I look at the ACL for TestDoc.doc and can now see that User2 has been added with READ permission only. NOTE that the ProtectedFolderAccess_DLG group is still there, and allowed full control.

I try to open TestDoc.doc (still logged on as User2) and now the file opens as read-only, and I'm forced to save a copy of it when saving changes.

STRANGE!

I remove the READ ACL entry and can now open TestDoc.doc with write permissions again. However, apon saving it the READ permission is again applied to the ACL and same thing happens.

I log on the client machine as User1 and can open TestDoc.doc and save changes multiple times with no problems.

I created the exact same scenario on a Windows file server and everything works as expected.

Has anyone come across this problem - and is there a solution?

Thanks.