I have 2 x MacBook Pro's (OSX 10.6.7) that access files stored on a 64-bit and a 32-bit Windows 7 PC.
The MBP clients can connect to the Windows shares and transfer files with no problem.
However, after a day or so, the shares become unresponsive. If you click on the server name under "SHARED" in Finder, you get a "Connecting…" status message. Once this happens neither PC can be accessed.
In Terminal, the network shares show as mounted. If you try to access the mounts, e.g. "ls /Volumes/data", the command hangs and cannot be ctrl/C'd.
The shares cannot be unmounted, eg. sudo umount -f /Volumes/data" hangs as well.
The only way to restore access to the Windows computers is to reboot the MBP's.
Any suggestions on how to prevent this happening, diagnose the cause, or restore service without a reboot would be much appreciated.
Best Answer
Nope, Apple is replacing Samba in 10.7 because it's GPLv3. (And Apple is avoiding GPL like plague. See, they're also slowly moving away from GCC).
Now, to answer the original question, it seems like the connection is "simply" lost. And as the mounting is done at the kernel level, it can completly hang the machine.
I think your issue comes from a sudden loss of network connectivity. Here's what I would look for :