*

[TinTIn]

Although the manual says:

"Note while the GUI will let you do it, it is a bad idea to share the same volume or dataset using multiple types of access methods. Different types of shares and services use different file locking methods."

Practically I need to be able to offer datasets to users of both Mac and Win so I would be interested to hear your personal experiences of this and how you find it is best and most reliable to do so.

SMB seems the most obvious choice but do you create a Win dataset with Win permissions and then offer it CIFS or perhaps UNIX dataset with UNIX permissions and then offer it CIFS. Or do you create your dataset however you do and offer it both CIFS and AFP?

Look forward to reading your replies.

Thanks


Sent from my iPhone using Tapatalk

 

[Ericloewe]

Simultaneous accesses via different protocols are almost guaranteed to break something.

The default solution is to use CIFS (including Windows permissions) whenever you need access from Windows and something else. SMB is the default on OS X these days, anyway, with AFP hanging on as a zombie because of Time Machine and little else.

 

[SweetAndLow]

I use cifs shares and Unix permissions across window, osx and several Linux machines. Unix permissions are simpler for me to manage so that is why I use Unix permissions.

 

[TinTIn]

Thanks both. You may have seen another post I made yesterday explaining the issues I'm having with the accessing a dataset from and Apple client over SMB. When I launch a word doc from the share and make an edit and save it back to the share a word work .tmp file appears on the share and never goes away. Every edit you make creates another one of these .tmp files. Is that something you've seen before?

Thanks


Sent from my iPhone using Tapatalk

 

[TinTIn]

I've managed to get this working so many thanks anyway.


Sent from my iPhone using Tapatalk