Comments on: MAC OS Error code -6602

By: Greg

Greg — Thu, 08 Oct 2009 20:44:57 +0000

I had a similar issue with an existing share that stopped working reporting the same issue
while other shares to the server worked fine from the mac

I tried changing to server IP address – no help

I went into the keychain manager and found one entery for JUST the server
example
192.168.10.x

username

I changed it to domain\username – no help
I then added another entry for 192.168.10.x
so that there were two entries as follows

one : username
two: domain\username

That fixed it – no server reboot

By: network diagnostic tools

network diagnostic tools — Tue, 22 Sep 2009 11:48:59 +0000

I also found using the IP fixed the problem as well, but once the normal naming is used, the problem returns.

By: nemesis

nemesis — Mon, 11 May 2009 05:50:11 +0000

Kinda late to the party, but I was having this issue writing an apple script to automatically mount my home network shares located on my NAS upon login to my Mac. One share just refused to mount with -6602 error. Its embarrassingly trivial but I had forgotten the case of the first letter in the network share name was significant. Once I changed it the script worked…often its the obvious thing!

By: admin

admin — Tue, 06 Jan 2009 20:48:43 +0000

I can’t stand AFP. If possible, create a new share then copy the files you want to share (that you can’t access) to that newly created shared folder. Hopefully that will work. Our problem occurred Mac to PC, but if it is DNS that causes this then the protocol is probably not the issue…

By: computeruser.ca

computeruser.ca — Mon, 05 Jan 2009 13:00:19 +0000

I’m getting the same 6602 error using afp to connect to an AFP server on a Linux box that is running netatalk. The error only occurs trying to mount one sharepoint on the server. Other shares on the box mount just fine. The broken share appears to be configured exactly the same as those that work – same owner, group, permissions, AppleVolume definition, etc etc. I’ve checked everything I can think of. Clearly, something I haven’t thought of it preventing the connection.

The 6602 error occurs with both Tiger and Leopard (Connect to Server…) so it’s not an OS incompatibility.