PDA

View Full Version : iMac can't browse MacBook Pro on the network


LarryM
15th November 2007, 03:12 PM
I know there are still problems in networking with Leopard, but this is basic networking and still doesn't work. I'm an experienced computer user, own a computing business, and "thought" I was well-versed in networking (obviously not <g>).

I have an iMac and a MBP on my home office network, both wirelessl connected to an Airport Extreme, and with Tiger both worked perfectly. I upgraded both machines to Leopard at the same time and ever since I've not been able to browse the MBP from the iMac. BOTH machines are shared absolutely identically in Preferences, including all settings under "Options".

On the MBP the iMac shows up as it should automatically in the Finder and when opened, display the shared contents of the iMac perfectly. On the iMac the MBP does show up in the Finder, but when opened just sits there "connecting" and never displays the shared contents of the MBP.

Even more oddly, I "can" connect from the iMac to the MBP using afp://192.168.1.XX and then it display the login credentials dialog box...I add them, tick the "Save to Keychain" and it then properly displays the shared contents of the MBP. This is the only way I can browse the MBP...it never just opens up automatically like the MBP opens up the iMac shared files.

But like a bad infocommercial...it gets better! When I do browse the MBP using afp://192.168.1.XX it displays the following (as it should per the sharing preferences):

larrymcjunkin - Home
MacIntosh HD - Obvious
Untitled - Boot Camp partition for Windows Vista
USB Drive - Directly connected USB drive

Now...when I open "larrymcjunkin" it displays the contents proplerly. But if I close the Finder and open the shared MBP again, I am forced to use the "Go To afp://192.168.1.XX" procedure again, but it then displays the same four items above, but "larrymcjunkin" is now grayed out and I can't open it. If I then open "MacIntosh HD" it opens just fine (but again I'm forced to use the "Go To afp://192.168.1.XX" procedure)...I can browse it...but if I close the Finder and reopen it, the "MacIntosh HD" is also grayed out and I can't browse it. Same scenario for the last two shared entries until I have all four shared items on the MBP now grayed out and not accessible from the iMac.

On the MBP...everything just works. The iMac shared items are in the Finder anytime I want them, but from the iMac it just doesn't work. Any ideas would be greatly appreciated. Many thanks.

LarryMcJ

zarmanto
15th November 2007, 04:04 PM
I'm not entirely sure that I know the solution to your dilemma... but I am curious about a couple of things: Why are you force-quiting the Finder so often? Is this just something that you do as a matter of course all the time, or are you having some other technical difficulties besides the network issues?

MacOS or Windows makes no difference... if you're repeatedly killing processes without ever logging out or rebooting the machine, then you're eventually going to destabilize the OS and cause it to crash. Force Quit is only intended to be a temporary fix to an application lock-up, so that you can save your work in other programs and reboot.

LarryM
15th November 2007, 04:07 PM
I never said I'm force-quitting the Finder...where did you read that in my post? I don't force-quit anything unless it becomes unresponsive.

LarryMcJ

zarmanto
15th November 2007, 04:09 PM
...But if I close the Finder...

Then what did you mean by this?

LarryM
15th November 2007, 07:42 PM
Just in case someone else is having this same problem, I finally gave up and called Apple Care, and they figured it out.

Somehow, something got munged in the Finder preferences. The fix was simply going to Home|Library|Preferences and deleting "com.apple.finder.plist" then logging off and back on again. Instantly everything was fixed.

LarryMcJ

zarmanto
16th November 2007, 05:26 PM
Deja vu... back in OS9 days, removing the preference folder from the system folder used to always be the first thing I'd tell people when they had any kind of application instability. Too bad my brain doesn't automatically reach back that far in the archival memory... ;)

Oh well. Glad you figured it out.