Are you trying to connect from the Finder Sidebar, Cmd-K, .....??
I have found the one of my Lion Macs cannot connect to the other Lion 0ac via the Finder Sidebar, but it can connect via cmd-K.
In looking at the log of the target achine i,e, the one I;m trying to connect ot I find that the AFPFileServer has crashed. Perhaps this is the problem??
It has been reported to Apple.
Trying to connect from sidebar.
I have a newer laptop that the Apple file server also crashed on, but have two desktop imac that don't show any file server crashes.
I've tried repairing permissions, turning off file sharing, restarting.
I have one imac that I can connect to from my other 4 macs.
When I try to use cmd-k or sidebar - I get following message:
This file server will not allow any additional users to log on. Try to connect again later.
I have multiple machines with Lion installed (Mid 2010 MacBook Pro, 2.66 GHz Mac Mini & a late 2010 iMac) and several more runing Snow Leopard. I cannot make AFP connections to any Lion machine from any other machine, Lion or not. At the same time I can make Screen Sharing connections and several other types of connection to the Lion machines, and can make any type of connection (including AFP) from the Lion machines to the Snow Leopard machines.
After I enter my password, attempted AFP connections to Lion invariably draw the "This file server will not allow any additional users to log on" alert.
Yet the target Lion machine shows "Number of users connected 0". I don't know how to find the crash log, but no AFPFileServer process appears in the Activity Monitor's All Processes list on the 2 Lion machines I checked, so this might be the problem. I've tried repairing the file system & permissions, to no avail.
=> Spettinger's workaround - switching AFP off and SMB on - does indeed allow me to make file sharing connections to my Lion machines. Thanks spettinger!
But, how can this be? There is nothing unusual about my configuration: its all recent Apple hardware & system software, with no 3rd-party protocols & no hacking. Why doesn't everyone who shares files have this exact problem?
I am having the same problem and my home folder is not shared so that is not the cause. I've posted separately about this but there don't seem to be any new solutions out there. As it seems to be a fairly common problem, I suppose we just have to wait and hope Apple will fix this in the 10.7.1 update.
I had what seems to be the same problem, and I think I solved it: In /Library/Preferences/com.apple.AppleFileServer.plist there were two keys, maxConnections and maxGuests, that were set to 0. Looked like this:
I changed the values to 10, and it seems to be working now.
I could find no keys like that in the preference files on either my MacBook Pro or my iMac. Trashing that preference file on the MacBook Pro did cure the problem though, well almost! I can now connect as a guest or registered user, but for some reason, I still can't connect using my Apple ID. Anyway, I can now connect my Macs in both directions so many thanks for pointing me towards the solution.
Thanks pbDixon! Here's my variation on the problem, for others' reference:
I initially had no success when I changed the plist key settings from 0 to 10 as you instructed. But then I tried also removing my home folder from the Shared Folders box, and then Apple filesharing started working again! For me, both steps were necessary to get things back on track. Hooray!
Note 1: even though I removed my home folder from being shared, it still shows up and is accessible (along with all its subfolders) anyway when I am connected from my other mac.
Note 2: I am now able to make/maintain network connections to shared items with both AFP and SMB enabled. Before pbDixon's fix, I could share files via SMB only. If I tried to turn AFP on (with plist keys set to 0), the SMB connection seemed to become disrupted as well.
Opps! I meant to thank pbDixon, who solved the mystery. It's also now clear why trashing the /Library/Preferences/com.apple.AppleFileServer.plist fixes the problem, too, though less elegantly.
But RG24 and yas2253 also had a piece of the problem: having made the 0 -> 10 fix, if I explicitly share my home folder on the target machine, I can no longer connect. If I remove my home folder from the sharing list, I can connect once again, and my home folder is automatically available.
So, two separate ways to break AFP, *both* of which need to be set right. Yikes!!