Called Apple, on our support contract, and spoke to a very helpful person though he couldn’t replicate the behavior.
As soon as I can, I’ll call back in, because I believe I’ve found the crux: resource forks.
Or, probably, any extended attributes, since I can replicate on demand now, simply by the presence of a “._” file – if there is one, I can only drag a copy off the server when I’m the owner of the file AND have Write access; under ALL other circumstances, it fails with the earlier-noted error message.
Not that it also appears necessary for the server in question to be an AFP server, and it’s almost certainly necessary for the volume being shared to NOT be HFS – such as an Xsan volume (which results in those “._” files to hold the reource forks and such.
Is anyone able to confirm any of this?
(BTW: I’ve been able to find _very_ little info on the “._” files – anybody have any clues?)
.
.
Comments are closed