Mac OS X 10.4.1: Problems with Mac OS 9 system access to Mac OS X Server-stored files
MacFixIt reader Brian Poppe reports an issue that has been confirmed by other readers where Mac OS 9 clients fail to properly access files stored on a Mac OS X Server 10.4.x system despite normally working network connectivity.
When the issue occurs, the Mac OS 9 user is presented with an error message indicating that the file is corrupt, or not recognizable.
Brian writes:
"Mac OS 9 clients users can no longer work with Quark files that are stored on a Tiger server.
"Double clicking file icons does allow Quark 4 or 5 users to open the documents but they are unable to save or save as. In addition, files can not be opened by navigating to the server from the Quark: File menu: Open method. 'Bad File Format' is the resulting error. Running the update from Tiger Server 10.4 to 10.4.1 did not help.
"They're stuck copying files to local drives before working on them."
Index:
- AFP Issues: Not inheriting permissions, can't set file attributes
- Distorted prints from Preview.app caused by ColorSync changes
- System freezes occurring when in/entering full-screen mode; QuickTime-related
- Problems creating disk images from Mac OS X 10.3.x (Panther)- burned media
- iSync 2.0: Problems synchronizing; potential solution
- Kernel panics when copying large files
- Live spell-checking problem, solution
- Loss of AirPort connectivity/weaker signal, solutions
- Problems with Mac OS 9 system access to Mac OS X Server-stored files
- Mail.app 2.0: Bundles now disabled; Problems with POP accounts, more
- Problems mounting disk images
- Printer Problems: Launching Epson's Printer Utility
- Problems with some internal modems
- Release Notes, difference between Software Update/download versions
- Safari 2.0: Downloads window re-sizing bug
- Problems with sleep; Solutions
- Spotlight: Tips for faster searches, problems with .DAT files; more
- Third-party applications
- Widgets: Conflict with Helvetica Neue; Dashboard crashes


4 to 4.11 and removing third party XTensions (don;t have time to deal with
WHICH XT might be involved).
Hope this helps
are having the same problem. DIsabling all of the XTs did not affect our
problem. Has anyone had success fixing this issue?