The 2 minute time out is per connection. 2 lost connections 4 minutes...

Some else who needs to read more slowly....

I did mention that the hung Finder starts taking out the rest of the GUI, and that force-quitting doesn't work. In light of this, what magic do you think is going to happen after my two minutes are up?

Two minutes on crack.....


Well, two minutes is not the answer. As others have said... I have exactly ONE connection I mount on my laptop at work. If I forget to unmount it before I leave for the day (from a MacOS X Server 10.2) and I go home and wake up the computer, I'm hosed.

I let it sit for over two hours one day with the spinning beachball... No luck at all.

The only thing I've found to be of any help at all is if you first notice the problem in an app other than Finder (when they try to write to disk is when the problem hits), and you still can switch your network connection over to where the server is, SOMETIMES it will reconnect and continue normally. However, when I go home, this is never an option, and so a reboot is the only fix.

This is the only remaining type of "crash" or "freeze" I encounter on MacOS X, at least with the work I do.