Wodan

Q: Can't connect to AFP server via Finder sidebar

Suddenly I can't connect to my server from the sidebar.

 

Guest access works. But my default user login returns "Connect failed".

I can connect via 'Connect to...' and type in the IP adres.

I can connect via iPad with a file sharing app (like ezShare)

 

The console returns:

Jul 29 04:54:39 myComputer NetAuthSysAgent[774]: AFP error -5014 mapped to EIO

Jul 29 04:54:39 myComputer Finder[282]: SharePointBrowser::handleEnumerateCallBack returned 5

 

I've tried temporary deleting the /Library/Preferences/SystemConfiguration folder... no help.

 

Any ideas?

MacPro 8core Intel Xeon 3Ghz, Mac OS X (10.7), 8GB Ram, ATI Radeon 5870

Posted on Jul 28, 2011 8:32 PM

Close

Q: Can't connect to AFP server via Finder sidebar

  • All replies
  • Helpful answers

  • by Martyin,

    Martyin Martyin Jul 29, 2011 12:27 AM in response to Wodan
    Level 1 (15 points)
    Jul 29, 2011 12:27 AM in response to Wodan

    Try this:

     

    Uncheck Remote Management

    Check Screen sharing

    Add user(s)

    When finished check the remote management again.

    It has something to do with updating / resetting the cache files...

    It worked for me.

     

    HIH

     

    M.

     

    (PS, i found it by coincidence. I had the same trouble and was "playing" with these settings

    which resolved the other problem.. 

  • by Wodan,

    Wodan Wodan Jul 29, 2011 2:20 AM in response to Martyin
    Level 1 (105 points)
    Jul 29, 2011 2:20 AM in response to Martyin

    Thanks for the tip Martyin,

     

    I can't check it right now, 'cause eventually the whole server broke down due to a malfunction with the fan of the MacMini Server... :-/

     

    But thanks anyway, I'll keep it in mind for the future.

  • by Wodan,Solvedanswer

    Wodan Wodan Aug 8, 2011 5:28 PM in response to Wodan
    Level 1 (105 points)
    Aug 8, 2011 5:28 PM in response to Wodan

    Deleting Library/Preferences/com.apple.AppleFileServer.plist did the trick.

  • by Dreyfuzz,

    Dreyfuzz Dreyfuzz Oct 18, 2012 10:30 AM in response to Wodan
    Level 1 (5 points)
    Oct 18, 2012 10:30 AM in response to Wodan

    Didn't work for me.

  • by osxconor,

    osxconor osxconor Sep 19, 2013 3:10 AM in response to Wodan
    Level 1 (0 points)
    Sep 19, 2013 3:10 AM in response to Wodan

    I found that the user's home folders (which we've emptied and use for quota'ed dropboxes) were taken offline. when they were back up everything went back to normal. I guess there is something hidden related to their login and permissions info in there.

  • by Wodan,

    Wodan Wodan Sep 19, 2013 10:17 AM in response to osxconor
    Level 1 (105 points)
    Sep 19, 2013 10:17 AM in response to osxconor

    Sorry, your question is a bit off topic. And, the problem is already solved. :-)

     

    But I can advice you, never to empty the home folders. They contain a default folder structure, needed by many applications. After Lion, Apple has hidden the Library folder too... so I don't know is you just emptied or trew the whole home folder away... but that folder is also necessary for the system.

  • by PhilMaul,

    PhilMaul PhilMaul May 8, 2014 12:59 PM in response to Wodan
    Level 1 (0 points)
    May 8, 2014 12:59 PM in response to Wodan

    This is still happening on 10.8.5 Server and clients. Deleting the Library/Preferences/com.apple.AppleFileServer.plist from the client machines didn't help. I'm getting the same messages in the system.log that were posted above:

     

    May  8 14:21:01 XXXX NetAuthSysAgent[3209]: AFP error -5014 mapped to EIO

    May  8 14:21:01 XXXX NetworkBrowserAgent[563]: SharePointBrowser::handleEnumerateCallBack returned 5

  • by AJ 2010,

    AJ 2010 AJ 2010 Jun 25, 2014 2:27 PM in response to PhilMaul
    Level 1 (4 points)
    Jun 25, 2014 2:27 PM in response to PhilMaul

    I had this issue with with client running 10.7.5 connecting to a Mac server running 10.8.5. I created the user in the server app which then made the user's home folder at /Users. After logging in to Workgroup Manager I was able to go to the problem user and set their home folder to None. That fixed the issue.

     

    Oddly, connecting directly to the IP of the server worked fine every time.