I'm really new to mac and I'm having some sharing problems with my Vista laptop.
1.
I managed to mount the vista laptop as a server (cmd-K) and was able to access the vista folders but the Vista laptop wasn't showing up as a "computer" (bonjour volume?). I'm not shure if that's ok.
Anyway, a couple of hours later I tried to access the server (shown as an Apple lcd screen whith what a believe is the Vista's laptop ip adress as a name) but it got stucked searching and nothing happend. Since then it kept repeating that behavior. I tried to eject it and a message showed up with something like "A disk in "192.168. etc." is in use and cannot be ejected. Try quitting the aplications and try again". I don't understand it's meaning so there's not much I could do about it. Do you?
2.
A couple of hours later the Vista laptop showed up all by itself (under SHARE) as a computer, not as a server (someone please explain to me what's the difference between this two) whith a CRT bluescreen icon and the laptop network name. But I couldn't access this one either. Same problem as before. (see Attached Thumbnail)
So, same laptop showing up twice under SHARE; once as a mounted server that I can't eject, once as a "computer"; but I cannot access either instance.
3.
I could always see and access the iMac folders from Vista. In fact it shows not only Public and specific Shared folders but also Printers, Macintosh HD and my Mac's user Documents folder. Is this right? shouldn't it be showing only Public and Shared folders?
That would be it for now, sorry for the long post. I will really appreciate any help.
Added data:
Standard new iMac 20", Core2Duo 2.66 GHz, 2Gb RAM, 320 Gb HD.
Connected to previously existing network (Vista/XP) with Airport Extreme.
Firewall set to "allow all income connections" (default)
Attached is an image of the volumes shown in System Profile. "genetica" is a folder I set to "shared" in Vista just to see if I could see selected folders from the Mac, which I could for the short period the "server" instance was accessible.
Vista laptop shows Mac in the network map as an unavailable or available node randomly, but either way it lets me access the Mac folders by double clicking its icon (via user and password input).
Router is a D-Link Dir300 whith WPA2 Only (AES, PSK) and wi-fi protected set up (WCN 2.0 in Vista) enabled. DHCP server is enabled. MAC filtering is ON and allowing all three computers (Mac, Vista and XP).
Seven years old XP SP2 machine had a stroke (Widows blew off) just before I took in the iMac, two days later it's beloved 19" lcd display stopped working as well, that's why I have no data about XP on this network. But it was doing well with Vista after HotFix installation (LLTD Responder).
I´ll keep updating this post, maybe I get to some conclusion. If not, at least this can be taken as precedent for similar issues. Hopefully someone else may find this post helpful with his/her own problem.
Finally I tried shuting down the Mac and turning it on again just to see what happened whith those petrified network volumes. But OS got stucked shuting down, just the wallpaper and the spinning wheel. This went on for a couple of hours so I had to force shutdown pressing and holding the power button. I read a couple of threads about this problem in previous versions of Leopard but no definitive explanations at sight.
When I turned it back on It started whithout delay but the volumes were no longer showing under SHARE in the side panel. I kept working on other stuff for a couple of hours and when I came back to the Finder I found the volume "diana1" had came back and was working just right.
When I click on it I get connected as a guest and I can see Public and Users shared folders. I had changed the "genetica" folder sharing status in between edits of this post and now it's not showing up anymore. Besides, the mounted volume is showing the eject icon which was lacking before the restart.
I don't know what is going on with the network but it appears to have a life of it's own. Luckily for the moment it's feeling healthy so I'll keep it like that and see what happens.
------------------------
Shared volume got stuck again so I started searching again and I found a couple of things that may be of help.
First I learned something about force unmounting stuck volumes but I guess it wont work with stuck SMB shared volumes...
http://www.macosxhints.com/article.php?story=20020426083026328
http://www.creativetechs.com/iq/cant_eject_a_disk_find_which_files_are_open.htm
I found the latter particularly helpful for future use.
Now, there are some procedures that may be better than rebooting, shutting down or, in my case, hard resetting...
https://forums.macrumors.com/threads/530028/
which basically says:
1. Run "lsof" in terminal
2. See about what smb mounts it complaints
3. sudo umount -f [any_failing_smb_mount]
Be aware though, that unmounting a filesystem using the force flag may produce unexpected results, but I guess it's better than hard resetting the Mac and thus hitting the HDDs every day ;-)
http://episteme.arstechnica.com/eve/forums/a/tpc/f/8300945231/m/259004456931
which goes through a couple of simple procedures being the more convincing: (performing a) sudo umount -f /Volumes/Share followed by a sudo rm -df /Volumes/Share dispatches the zombie volume, and I can re-connect without all that Sharename-1 rubbish.
At the bottom of that thread theres a mention to TCP keepalive as a possible solution to this problem and a brief mention to the cause being a network failure. That would make sense with the fact that the laptop Im networking goes to sleep after a while, and that could be taken as a network failure causing the zombie share. If thats the case I would be forced to turn on and off sharing from System Preferences each time I want to share files with the laptop as it connects itself whenever file sharing is enabled, just to become a zombie when the laptop goes to sleep.
If anyone knows how this TCP keepalive thing can help preventing this error Id really appreciate a brief explanation or a link to someone elses explanation.
1.
I managed to mount the vista laptop as a server (cmd-K) and was able to access the vista folders but the Vista laptop wasn't showing up as a "computer" (bonjour volume?). I'm not shure if that's ok.
Anyway, a couple of hours later I tried to access the server (shown as an Apple lcd screen whith what a believe is the Vista's laptop ip adress as a name) but it got stucked searching and nothing happend. Since then it kept repeating that behavior. I tried to eject it and a message showed up with something like "A disk in "192.168. etc." is in use and cannot be ejected. Try quitting the aplications and try again". I don't understand it's meaning so there's not much I could do about it. Do you?
2.
A couple of hours later the Vista laptop showed up all by itself (under SHARE) as a computer, not as a server (someone please explain to me what's the difference between this two) whith a CRT bluescreen icon and the laptop network name. But I couldn't access this one either. Same problem as before. (see Attached Thumbnail)
So, same laptop showing up twice under SHARE; once as a mounted server that I can't eject, once as a "computer"; but I cannot access either instance.
3.
I could always see and access the iMac folders from Vista. In fact it shows not only Public and specific Shared folders but also Printers, Macintosh HD and my Mac's user Documents folder. Is this right? shouldn't it be showing only Public and Shared folders?
That would be it for now, sorry for the long post. I will really appreciate any help.
Added data:
Standard new iMac 20", Core2Duo 2.66 GHz, 2Gb RAM, 320 Gb HD.
Connected to previously existing network (Vista/XP) with Airport Extreme.
Firewall set to "allow all income connections" (default)
Attached is an image of the volumes shown in System Profile. "genetica" is a folder I set to "shared" in Vista just to see if I could see selected folders from the Mac, which I could for the short period the "server" instance was accessible.
Vista laptop shows Mac in the network map as an unavailable or available node randomly, but either way it lets me access the Mac folders by double clicking its icon (via user and password input).
Router is a D-Link Dir300 whith WPA2 Only (AES, PSK) and wi-fi protected set up (WCN 2.0 in Vista) enabled. DHCP server is enabled. MAC filtering is ON and allowing all three computers (Mac, Vista and XP).
Seven years old XP SP2 machine had a stroke (Widows blew off) just before I took in the iMac, two days later it's beloved 19" lcd display stopped working as well, that's why I have no data about XP on this network. But it was doing well with Vista after HotFix installation (LLTD Responder).
I´ll keep updating this post, maybe I get to some conclusion. If not, at least this can be taken as precedent for similar issues. Hopefully someone else may find this post helpful with his/her own problem.
Finally I tried shuting down the Mac and turning it on again just to see what happened whith those petrified network volumes. But OS got stucked shuting down, just the wallpaper and the spinning wheel. This went on for a couple of hours so I had to force shutdown pressing and holding the power button. I read a couple of threads about this problem in previous versions of Leopard but no definitive explanations at sight.
When I turned it back on It started whithout delay but the volumes were no longer showing under SHARE in the side panel. I kept working on other stuff for a couple of hours and when I came back to the Finder I found the volume "diana1" had came back and was working just right.
When I click on it I get connected as a guest and I can see Public and Users shared folders. I had changed the "genetica" folder sharing status in between edits of this post and now it's not showing up anymore. Besides, the mounted volume is showing the eject icon which was lacking before the restart.
I don't know what is going on with the network but it appears to have a life of it's own. Luckily for the moment it's feeling healthy so I'll keep it like that and see what happens.
------------------------
Shared volume got stuck again so I started searching again and I found a couple of things that may be of help.
First I learned something about force unmounting stuck volumes but I guess it wont work with stuck SMB shared volumes...
http://www.macosxhints.com/article.php?story=20020426083026328
http://www.creativetechs.com/iq/cant_eject_a_disk_find_which_files_are_open.htm
I found the latter particularly helpful for future use.
Now, there are some procedures that may be better than rebooting, shutting down or, in my case, hard resetting...
https://forums.macrumors.com/threads/530028/
which basically says:
1. Run "lsof" in terminal
2. See about what smb mounts it complaints
3. sudo umount -f [any_failing_smb_mount]
Be aware though, that unmounting a filesystem using the force flag may produce unexpected results, but I guess it's better than hard resetting the Mac and thus hitting the HDDs every day ;-)
http://episteme.arstechnica.com/eve/forums/a/tpc/f/8300945231/m/259004456931
which goes through a couple of simple procedures being the more convincing: (performing a) sudo umount -f /Volumes/Share followed by a sudo rm -df /Volumes/Share dispatches the zombie volume, and I can re-connect without all that Sharename-1 rubbish.
At the bottom of that thread theres a mention to TCP keepalive as a possible solution to this problem and a brief mention to the cause being a network failure. That would make sense with the fact that the laptop Im networking goes to sleep after a while, and that could be taken as a network failure causing the zombie share. If thats the case I would be forced to turn on and off sharing from System Preferences each time I want to share files with the laptop as it connects itself whenever file sharing is enabled, just to become a zombie when the laptop goes to sleep.
If anyone knows how this TCP keepalive thing can help preventing this error Id really appreciate a brief explanation or a link to someone elses explanation.
