Mac OS X 10.4: AFP access problems: AppleTalk no longer supported, workaround; more

There are a number of new issues with AFP (Apple fileshare protocol) access under Mac OS X 10.4 (Tiger). Mac OS X 10.4 (Tiger) does not support AFP networking over AppleTalk. Users must instead turn on File Sharing over TCP/IP (in the File Sharing Control Panel on Mac OS 9 systems) in order to enable networking.

As noted by MacFixIt reader Michael Lettini:

"On the OS 9 server, go to the File Sharing Control Panel and turn on File Sharing with TCP/IP. Just click the box and Tiger will connect with it. It's that simple."

Chris Wiley adds:

"Just thought I'd mention that according to my tests here, If your client computer is running Tiger and you want to connect to a pre-Mac OS X file server, on the file server you'll need turn on the option in the File Sharing control panel which says, 'Enable File Sharing clients to connect over TCP/IP.' If the version of the classic Mac OS you are running as a file server doesn't support the TCP/IP option -- previous to Mac OS 9 I believe -- than you may need to upgrade the file server's OS."

However, this workaround will not work for systems running Mac OS 8.6 or earlier, necessitating an upgrade to Mac OS 9.

A number of readers have now noted that OpenDoor's ShareWay IP will provide connectivity for systems that cannot be upgraded to Mac OS 9.

MacFixIt reader Guillaume Gete writes:

"OpenDoor sells ShareWay IP which was then bought in a limited license by Apple to be integrated in... Mac OS 9. So, if you need Mac OS 8.6 or a previous version and can't upgrade it for any reason, you should have a look at Shareway IP (though it is really a bit pricey)."

If you are still having problems after switching to TCP/IP, there may be another factor at play -- such as an errant Mac OS 9 extension, as in MacFixIt reader Joseph Finnel's case:

"After about 2.5 hours of phone time with AppleCare Support, (and reinstalling Tiger with no improvement) the technician finally had me revert the Extensions on the Mac OS 9 system to the 'locked' Mac OS 9.2.2 All configuration. It worked! I was then able to connect and log on to the Mac OS 9 system from the G5 just like before.

"After comparing the original OS 9 system extensions with the 'All' configuration, I discovered my problem was Norton's Personal Firewall on the Mac OS 9 system. I disabled the firewall to permit all Appletalk/TCP/ IP access and problem solved."

Deleting aliases and re-creating MacFixIt reader Tracy Valleu reports that deleting, then re-creating any AFP aliases restores access for initially problematic shares in some cases

"I had been accessing my other computers via Alias icons on my main computer's desktop. Trashing those; using the 'Go..' menu, and re-creating them solved all my problems."

Possible solution: Re-establishing Keychain authentication Jeff Silvestris, meanwhile, reports that re-establishing keychain passwords (deleting then re-entering them) resolved the issue in his case:

"Every time I tried to connect to the SMB/CIFS file share here at work this morning it kept defaulting to my old username... even though I would make the manual change as I logged in, I kept getting a read/ write error -36.

"I fixed the problem by using Keychain Access to remove any keys associated with my old login. (Not sure, delete all the keys for that share). This fixed it and everything is working again."

Resources