aaronadams
Dabbler
- Joined
- Apr 17, 2014
- Messages
- 23
Hi, just a quick question from a new FreeNAS user.
I'm configuring a share for an office full of Macs; however, they still have one stray Windows PC that also needs access to the share.
I can't seem to figure out how to get the Windows machine to play nice. It seems like no matter what I do, the Windows machine doesn't understand that it's allowed to modify files – even though it understands that it can create them!
Dataset permissions:
If I turn off, say, inherit owner and inherit permissions, then looking at a file created by another user, the Windows machine understands that the owner and group have read/write, but it doesn't understand that it's a member of the group.
Ideally this would work like it does in OS X; when I connected to the volume, it would just tell me I'm the owner of all of the files, and would tell me I could edit the ones I could edit. Instead it seems like CIFS is trying really hard to allow Windows to view the permissions, which is just causing problems.
Should I really switch to a Windows ACL just for one Windows machine?
I'm configuring a share for an office full of Macs; however, they still have one stray Windows PC that also needs access to the share.
I can't seem to figure out how to get the Windows machine to play nice. It seems like no matter what I do, the Windows machine doesn't understand that it's allowed to modify files – even though it understands that it can create them!
Dataset permissions:
- Owner: nobody:allstaff
- Mode: 770 (though I've tried 777 to no avail)
- Type of ACL: Unix
- File mask: default (0666)
- Directory mask: default (0777)
- Inherit owner: yes (have also tried no)
- Inherit permissions: yes (have also tried no)
- Inherit ACLs: yes (have also tried no)
If I turn off, say, inherit owner and inherit permissions, then looking at a file created by another user, the Windows machine understands that the owner and group have read/write, but it doesn't understand that it's a member of the group.
Ideally this would work like it does in OS X; when I connected to the volume, it would just tell me I'm the owner of all of the files, and would tell me I could edit the ones I could edit. Instead it seems like CIFS is trying really hard to allow Windows to view the permissions, which is just causing problems.
Should I really switch to a Windows ACL just for one Windows machine?