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 - email@example.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.