It doesn't pull the fruit:model value from the SMB service's aux params, nor does it pull mimic model or hostname from the AFP service's aux params - it's always set to RackMac. The second screenshot shows the same server after upgrading to FreeNAS 11.3, which always broadcasts a _device-info record regardless of whether AFP is running. The 'zfstest' server is retaining its cached icon from before adding the aux params relaunching the Finder will revert it to a generic one. But in this case, I have set hostname = ZFS-Test-NAS and mimic model = AirPort in the AFP service's aux params, causing both the mDNS records for AFP ('Personal file sharing') and _device-info to present an alternate hostname, resulting in a separate icon in Finder just for that service. With this version, a _device-info record with the default value of RackMac (the Xserve icon) will be broadcast only if the AFP service is running.

In this first screenshot, my zfstest server is running FreeNAS 11.2. The following screenshots use the Flame utility to show exactly what's being returned, although you can also inspect a record's value in Terminal with dns-sd -L servername _device-info._tcp. As mentioned above, the primary factor is the string presented in the _device-info._tcp. The same issue arises when I attempt to use AFP.I want to document exactly what changed between 11.2 and 11.3 with respect to how icons are shown for a FreeNAS server in the Finder. The parameter is rejected by the 'testparm' command on the the version of Samba I am running (3.4) The compiling issue is resolved by changing the parameter to 'unix extensions = no' but still fails to resolve the issue. I found a thread that describes my problem almost exactly suggesting to use the 'unix extensions = off' parameter in the global section of the smb.conf file, but to no avail. Other clients should be able to read the file during this time, but not be able to write to it. My goal is to be able to lock a file (744) from other users when its in use or open on a client machine. No matter which permissions I set for a file on the server, the Mac ignores them and changes the permissions back to 766. I'm having some serious permission issues with Mac client machines (OS X Snow Leopard) connected to a UNIX server (running CentOS) through Samba.

Macos samba client