I've done both tcp and ddp services and while it seemed to be much better in OS9 when we started I'm not sure that the OSX file errors didn't cause future problems with OSX access to them.
The files themselves are intact and can be opened, but copying them back to the server causes the errors. I have set up netatalk prior to using osx on a few mac-based linux machines without a problem.
My work has a support vendor to handle the maintenance for our fileserver. I've asked that they update the software first. Then if that doesn't cut it to recompile the package with the option '--with-did=cnid' or '--with-did=last' as I've read in the sourceforge forum that these two options seem to work.
The kicker was an earlier version of netatalk seemed to work with OSX. I believe it was a 1.4 release and would have been around the time of OSX10.1.3 or so.
Anyhow, If anyone else has an idea please share. I'll post back when I have a working solution.
The files themselves are intact and can be opened, but copying them back to the server causes the errors. I have set up netatalk prior to using osx on a few mac-based linux machines without a problem.
My work has a support vendor to handle the maintenance for our fileserver. I've asked that they update the software first. Then if that doesn't cut it to recompile the package with the option '--with-did=cnid' or '--with-did=last' as I've read in the sourceforge forum that these two options seem to work.
The kicker was an earlier version of netatalk seemed to work with OSX. I believe it was a 1.4 release and would have been around the time of OSX10.1.3 or so.
Anyhow, If anyone else has an idea please share. I'll post back when I have a working solution.