Because Mac OS X 10.4 Tiger doesn't work with AppleShare (AFP) over AppleTalk, if you start Classic and try to access an AppleShare-based server (or an alias to the server is accessed by you or by an application), you will see this alert:
"Connection failed, the server may not exist or is not operational at this time. Check the server name or IP address and try again."
Classic applications that rely on any AppleShare-over-AppleTalk services may also fail.
A good workaround is to configure the server to use AFP over TCP/IP, if possible, instead of AppleTalk.
Tip: If the issue occurs again when you open an application with Classic (because it needs to access an AppleShare-based server), consider using a Mac OS X version of the application instead.
If the server can't be configured to use TCP/IP, you may be able to prevent Classic from attempting to connect to the server by removing aliases to that server or to files on that server. Look for aliases to the server in these locations, then remove them:
Tip: If you don't know where your System Folder that's used by Classic is, open Classic preferences. You'll see your selected System Folder in the "Select a System Folder for Classic" box.
If the issue persists, and you can't locate any other server aliases or resolve the issue by changing the server to use TCP/IP, try these steps:
This document will be updated as more information becomes available.