Between L4D2 happening in New Orleans, and Dead Rising 2 happening in Vegas, this holiday season is going to be packed with zombies that want to party.

I haven't directly diagnosed this issue since 10.3, but it still might be an issue:

OSX does support SMB pretty well (they actually use the samba suite under the hood for client and server). There's a catch though. In MacOS (classic and X), there are two parts to the file: the "data fork" (what you would normally think of as the file), and the "resource fork" (contains meta data, and executable code for "classic" programs). Over SMB, the resource forks are stored as a separate file; example.txt's resource fork would be stored as ._example.txt.

This by itself is not a problem. The problem is that many OSX programs will lock the resource fork, but never unlock it. AFP never has an issue with this (I assume its built into the protocol, as it is into HFS). The net result is that if you're running multiple users trying to successively modify a file, they're going to get locking errors when they go to save.

I ran into this issue trying to maintain an all Linux development environment for a team of web developers. In the end I had to just get a dedicated OSX box so all the mac clients could work happily. Also, netatalk was an option, but at the time it was too immature, and did things like enforce a small (15?) character filename limit.