08-17-2013, 05:37 AM
But here's the thing -- most of the people new getting this message DO NOT have more than 10 connections open.
If you enter the following command in Terminal:
netstat -f inet | grep afp | open -f -a TextEdit
a TextEdit window will open with all your active AFP connections listed in it. When I run that on my "server" machine, for example, it shows four connections, all from my wife's Mac (the only way she uses the server is in Time Machine), all in CLOSE_WAIT. (The last time she successfully connected to the TM server was TWO DAYS ago, so these have been hung for some time!) Other people seeing this problem are showing one or two connections open, and another handful stuck in CLOSE_WAIT.
in all cases I have seen, there are a lot of connections hung in CLOSE_WAIT, but even so, nothing approaching 10 connections.
Apparently, the only way to flush the dead connections is to stop/restart File Sharing.
If you enter the following command in Terminal:
netstat -f inet | grep afp | open -f -a TextEdit
a TextEdit window will open with all your active AFP connections listed in it. When I run that on my "server" machine, for example, it shows four connections, all from my wife's Mac (the only way she uses the server is in Time Machine), all in CLOSE_WAIT. (The last time she successfully connected to the TM server was TWO DAYS ago, so these have been hung for some time!) Other people seeing this problem are showing one or two connections open, and another handful stuck in CLOSE_WAIT.
in all cases I have seen, there are a lot of connections hung in CLOSE_WAIT, but even so, nothing approaching 10 connections.
Apparently, the only way to flush the dead connections is to stop/restart File Sharing.