When my MacBook wakes up, away from a network it was previously connected to, it shows the "server connections interrupted" window. When I click "disconnect all", I get a spinning beach ball of death. Restarting the finder doesn't help. Logging out and restarting is not possible anymore. The only thing I can do is a hard reset.

Or is there a way to kill the process from the terminal or from the activity monitor?

Strange fact: when the interrupted connection window is beachballing, I'm also unable to invoke the 'About this mac...' command in the apple menu. Nothing happens...

interrupted connections

unable to reopen the finder after force quit

alt text

  • What kind of connections did you have before you disconnected? Sep 18, 2010 at 14:27
  • What OS are you on? Mac OS 10.6 has much improved disk management than the previous versions. Sep 30, 2010 at 13:48
  • 1
    I guess you are using DHCP, right? Some people report setting IP manually fixes the problem Sep 30, 2010 at 13:54
  • My office and home networks use DHCP and the disconnection issue went away with the upgrade to 10.6. Sep 30, 2010 at 14:08
  • 2
    I'm guessing he is using 10.6 since he tagged the question with "snow-leopard". Oct 1, 2010 at 11:29

6 Answers 6


If the issue is not common enough to find a solution on the Apple Knowlegde Base then it is most probably a rare issue caused by a corruption in the operating system or a 3'rd party application. Under these circumstances I would recommend one of the following:

  • Reinstalling OS X (after performing a backup, preferably with Time Machine).
  • Find someone else with identical hardware and software to see if their laptop does the same thing under the same circumstances (might be a compatibility issue with your wireless access point or router?)
  • Make a reservation at the Apple Genius Bar, they are great troubleshooters and will be able to tell you if there is something wrong with your laptop hardware or software.
  • A lot of troubleshooting information can be written to the OS X Console. Just have it running (and visible) while replicating this issue and it might print some information related to the issue.

I hope one of those steps can help you diagnose the issue, as it does not seem to be common enough to find a single solution for :-)

UPDATE: Since it appears that you are running "ADMitMac" which probably integrates with OS X in a significant way, and considering your issues are network related, there is a rather large red flag surrounding this software. I would strongly recommend uninstalling it as a trial to diagnose the issues you are encountering.


Good advice has already been given, however, in order to determine if there’s a specific share causing the issue, I’d suggest two things:

1) Create a new blank user, connect from there and try to see if this new user exhibits the same problem/behavior.

2) Additionally, disconnect all shares and start connecting one by one and perform the voodoo magic to reproduce the “disconnect” dialog (with each individual connection). That way you could see if the problem only manifests in some connections but not others, or all.

Do you have any server log or anything that could be an indication of a process hanging or waiting for a server response that never comes? (already suggested)

UPDATE: Today I made a test. I connected my 10.6.4 to a Samba box running an ancient version of Fedora (probably 3-4 years old). And when I had the connection open, I halted the server to get the Server connections interrupted dialog:

Here’s how my dialog looked like:

Disconnect Dialog

public is the name of the share and nippur is the name of the server.

Now that’s why your dialog looked weird. Are you sure you’re running 10.6.x?

UPDATE 2: You’re running 10.6.4 but using ADMitMac, which "turns a Mac into a true Active Directory client”. I suspect that’s where the problem lies. I’d disable or remove that and start from there. I’m 99% sure that without it, the problem will go away. The problem will then turn onto a new question… why? But that’s an entire new world and only Console Logs will help (plus, of course, ADMicMac’s tech support).

  • 1) My MacBook is brand new - using it since 1 week. 2) It happens with ALL server connections. 3) A server log is irrelevant, as I wake up my mac away from any servers.
    – Anton
    Oct 4, 2010 at 19:41
  • What is not irrelevant is 2) Does it happen with ANY server connection? 3) By server connection I meant console output from YOUR computer. Oct 4, 2010 at 21:44
  • "About this mac" says I'm running 10.6.4. I'm also forced to use ADMitMac, maybe that's why the eject button looks weird.
    – Anton
    Oct 6, 2010 at 19:23
  • So, you are using Active Directory Mac (ADMitMac) and you have problems when you resume your Mac from sleep after being connected to (among other things) windows share on an Active Directory? I think you’ve found your answer. If it’s a brand new Macbook Pro with 10.6.4, I suggest you try a fresh install without ADMitMac and see from there. I suspect that that is the root of all evil here. Which would then turn the tables into talking to them about the issue. I don’t have that (nor a server) to try. I’m sure Console output could be helpful if you can capture some. Oct 7, 2010 at 2:38
  • Sorry I didnt see your update before updating my answer ... I know it looks suspicious but I didnt copy you :) Oct 7, 2010 at 5:12

Try killing /System/Library/LoginPlugins/FSDisconnect.loginPlugin as described at http://whatsamknows.tumblr.com/post/37368603810/get-rid-of-server-connections-interrupted

  • Whilst your answer may theoretically answer the question, it would be preferable to include the essential parts of the article in an answer below, and provide the link for reference
    – Pfitz
    Dec 7, 2012 at 7:29
  • even with sudo my mac won't allow me to move this directory
    – Mugen
    Mar 1, 2022 at 12:11

If you are running 10.2 or 10.0 then what you are describing appears to be covered by the Apple Knowledge Base Article TA21171 (Interruption of Server Connection Can Cause Computer to Stop Responding). The solution they outline in the article:

To resolve the issue, you may have to force restart your computer using the power or interrupt button.

Avoid the issue in the future by ejecting any shared volumes before taking the actions described above.

If you accidentally trigger this issue, restoring connectivity to the server might eliminate the need for a forced restart.

  • Nice research, but I doubt the OP (or anyone) is currently running 10.2. I believe most old Macs have Panther at least and those still having Jaguar are too old to even have problems :) Oct 1, 2010 at 7:07
  • The solution is what I do now. But I want something other than force restart. Restoring connectivity is only possible if I travel back to the office. I'd rather force restart. :)
    – Anton
    Oct 4, 2010 at 19:47

I haven't had problems with disconnected network drives, but I have seen myself the Finder error -10810 and have always just restarted my Mac (saving all work beforehand).

This thread here suggests though, that Finder will recover itself in a matter of few minutes so give that a try.


I have exactly same problem. I get this aprox 75% of time when I wake my MacBook Pro from sleep. Everything works thou, so if I click share it's up and running. I guess my problem is related that network hasn't really woken up from sleep and therefore I get this annoying message dialog.

So my preferably solution would be that message box would be ignored. Does anyone know a way to do this? Or maybe shell script which would kill this message box..

I'm running 10.6.4 and not running any third party Active Directory or Network software

  • Kriz

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .