I work in a small company where I have a NAS4Free (version -9.2.0.1.943 ) server on a venerable board VIA Epia Mini-ITX (x86) at 600 Mhz with a couple of drives in RAID 1 using UFS updates coming from FreeNAS. We have been using it for years without problems. With this distribution the system worked correctly but now I get and error with Mac users.
Our working environment combines Apple computers (Mac OS X Mavericks and Mountain Lion) and PC (Windows XP and Windows 7) and the server works as a workgroup.
The NAS has a group of folders in which any user can read and write. It does not require any security because it is a place where users can put whatever they want. It's like a "temporary" folder or area data transfer...
The system is activated only SMB (AFP is off) with the following settings :
- Authentication: Anonymous (default user is ' ftp')
- Protocol: NT1
- Create Mask : 0777
- Mask of directory : 0777
- Great read / write : ON
- Sendfile : ON
- Store DOS attributes : ON
- AIO : ON
- Visible : ON
- Guest: activated
- Inherit Permissions : ON
- Recycle Bin : ON
- Hide dot files : ON
- Auxiliary parameters : create mask = 0777 directory mask = 0777 force create mode = 0777
Under Windows the folder is created with right permissions but under Mac OS X folders and files are created with 0755 and users are unable to delete them.
Mac users connects to the NAS using 'Command + [K]' adding the path "smb ://NAS-name"
Why Mac OS X does not give us the desired forced permissions?
Are there any changes we can make in configuration files to skip this behavior?
Sorry for my English. It is not my usual language.
Best regards
[Update 04/04/2014]
I have solved the problem. In addition to the above settings you must be used in Mac OS X the connection string 'cifs ://' instead of 'smb ://'
Since Mountain Lion version Apple switched to its own code and uses SMB2/port 445 to connect to Windows Vista/7/8/8.1