Welcome to the MacNN Forums.

Jeff698 · Sep 6, 2006, 10:27 AM

I'm having difficulty accessing an external HD connected to a Mac mini via my iBook over an AirPort Express wireless network. I can access the internet just fine on all computers over the network. I can see the Mac mini and even the external HD but when I try to mount the volume, I get the following error: "Server Connection Interupted: miniStack" where miniStack is the external HD. The only button on the error box is 'disconnect'.

Once I click on this, I've noticed that personal file sharing gets turned off on my mini. I have never been able to establish this connection.

I found another thread on this forum refering to PFS getting turned off when the machine reboots or looses its network connection. This isn't happening in my case, however. There's no rebooting involved and the network connection is solid throughout.

I've turned on personal file sharing on the mini using my administrator log in. This is the same login information I'm using on my iBook when I try to connect. I've also activated AppleTalk via the Airport settings in the Network preference settings, although I've tried this with and without AppleTalk active.

I've also activated AppleTalk on my iBook and turned on personal file sharing.

All my Macs are running the latest version of OS X (10.4.7).

This exact same thing happens when I try to access the native internal HD on my mini so it isn't just the external HD that's the problem.

I've searched high and low through the Apple support fora and here and can't find anything addressing this.

Does anyone have any idea what I'm doing wrong?

Thanks and take care,
Jeff

indigoimac · Sep 6, 2006, 02:45 PM

I'd first try to repair permissions, I'd be willing to bet something is out of whack, especially if it never worked.

Jeff698 · Sep 7, 2006, 04:28 PM

Originally Posted by indigoimac

I'd first try to repair permissions, I'd be willing to bet something is out of whack, especially if it never worked.

Thanks for the reply.

That's probably what I should have done. Instead, I overreacted with an Archive and Install. Fortunately, that did the trick and the system works like a charm now.

I still have no clue what the problem was.

Take care,
Jeff