A volume failed to mount (Error code -6602)

Yesterday morning I started work as usual as ran into a problem mounting one of the shares from my XP PRO machine on my Macbook Pro.  Obviously the first question I asked was WTF? Everything worked yesterday, and not today.

I did some Googling and found mention about opening some UDP ports, but my TCP/IP settings currently has all ports open, so that didn’t help.  Then just for giggles I decided to turn off simple file sharing.  That fixed it!

So if you receive the message “A volume failed to mount”, and then another one with “Error code -6602″ in it, you should check your PC’s file sharing settings.  You would do this by following these steps.

How to disable simple file sharing on XP

  1. Open Windows Explorer ( Win+E  or  double click My Computer )
  2. Click Tools > Folder Options
  3. Click the View Tab
  4. Scroll down to the bottom, and uncheck “Use simple file sharing (Recommended)”
  5. Then retry mounting the share on OSX

Tags: , , , , , , , , , ,

This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.

5 Responses to “A volume failed to mount (Error code -6602)”

  1. FJ1 says:

    Thank you for this. This and other expert threads talk over my head.

    But I was able to connect from a MacBook to an XP box with a Go>Connect to Server using smp://xx.x.x.x only after creating an account on the XP box that matched the current user name on the MacBook. Otherwise it wouldn't connect with an account set up with a diff. name and password. After turning off simple file sharing and setting up a shared folder on the XP box, of course. FJ

  2. Eric Fickes says:

    @FJ1 – Sweet! Glad this helped somebody out. If you have access to the XP administrator account, you can always hit the built in shares like so "smb://x.x.x.x/C$", just be ready to enter the user / pswd.

    Another tip, command + K is the shortcut for the 'Connect to Server' dialog box.

    ( for some reason the reply feature isn't working for me )

  3. VinceSamios says:

    Another solution to this problem – My hard drive was completely full (0kb remaining) – which is the reason I was trying to connect to the share (to dump some data) – made some space (just closed firefox – which is a resource hog) and was able to connect.

  4. EAB says:

    I have just recently had this issue with connecting my Mac to my PC. This has worked perhaps up to 3 months ago. I had to reinstall XP (drive failed). Now I can’t connect to the PC from the MAc. I can interestingly use the remote logon from the mac to the PC. I can from the PC connect to the Mac.

    This suggest that Apple has screwed something up and have not told anyone they screwed up!!!!!!

    I don’t know how much longer I can support Apple, They have become worse, it that’s possible then MS. Wow!!

Leave a Reply