I have an error connecting my powermac 10.5.1 to my xp sp2 machine. i use the connect to server feature and type smb://(ip)/d$ a username/password box appears and i can log on successfully and all is well. some time later i may reopen the share but get an error saying the share is unavailable. i dismount the share and reconnect where again i supply the password but this time i get error:
a volume failed to mount. the volume "D$" could not be mounted. then another windows saying sorry, the operation could not be completed because an unexpected error occurred. (error code -6602)
the only way around is for me to restart the windows machine and i can reconnect again. there is no problem connecting from other windows machines. why is this happening?, i cant keep restarting windows
After Anton Schep installed a security update in Leopard, mounted Windows shares disconnect after a few minutes:
I have been using "Connect to Server" to mount a SMB share from a Windows 2003 without a problem since I upgraded to Leopard (which resolved the digital signing issue). However as of Monday, which coincides with me having applied the latest Security Update, I can no longer keep the share mounted longer than about 5 minutes. Then it disconnects and I cannot reconnect at all. After a restart I can reconnect and it appears that after a couple of hours I can reconnect again, but in both cases I get kicked of after 5 minutes. Linux machines don't have a problem mounting the same share.
thanks for that, but why would i have to restart the pc if it is a mac problem? also, i have the 2 machines cabled with a netgear gs108 gigabit switch. no wifi involved. i have also got both machines on static ip addresses. incidently my mac is on 10.5.2 now and still has the same issue.
If you read the posts, the security update came out on the 18th of March. The description of the problem is this: "I no longer can keep a smb share mounted on the desktop. After about 5 minutes it disconnects and I can not reconnect for quite awhile"
This is your problem, it has nothing to do with your PC, when you reboot your PC, you are fixing it because you are causing the Mac to reconnect and re-authenticate. If you waited long enough, you could probably reconnect from your Mac, but the article says there is no preset amount of time you have to wait.
When did you notice the problem occurring? Recently? Record the amount of time it takes to get disconnected, I bet it is 5 minutes.
If you had a Linux machine you could try connecting to the share from that to see if it stays connected - if it does then you know for sure it is the Mac with the problem.
Also, the one forum says to turn off your Airport adapter. I know you do not use it, but is it on and enabled on the Mac? The problem seems to be related to having more than one network adapter enabled on the Mac. Try disabling it and see if you can stay connected to the share.
Since the update just came out, there is little on the net as for what is fixing the issue besides what I have posted. My best guess is that another update will fix this issue or there will be an official work around from Apple as news of this issue gets spread around the internet.
my airport adapter is disabled. since i dont need it.
Also the length of time before disconnection can be several hours. for example i can stream several hours of audio into itunes or move several gigs of data, but if i dont use the connection after a while of inactivity it fails. also i have another windows machine which does not seem to have the same problem i.e. the connection hasnt dropped yet. recently on the windows machine i upgraded d:drive to 1TB. could this be an issue. unfortunately the update and the upgrade happened about the same time, so it makes it hard to tell but i have the same issue with my 80G c: drive.
The only other thing I can think of for you to try would be using a third party software to manage your SMB file share connections, like SMB manager and seeing if the disconnect issue persists:
This sucks. You aren't the only one with this issue. It has something to do with Leopard and the way it handles SMB file shares, and this was changed from how Tiger handled them. Hopefully this gets addressed in the next update. I sent this forum post to macwindows.com to be put on the site, please leave it open as we can add this to the list of affected computers and hopefully Apple will do something about it.
One other thing, is this XP machine something that needs to be secured? can we try messing with the share permissions and the NTFS permissions to see if that keeps you connected? Normally I would not tell anyone to do this, but if you are behind a good firewall and not worried about others on your network, you can set the share permissions to allow the special identity ANONYMOUS USER and the EVERYONE identity full access, then give them read, write, and execute NTFS permissions on the shared folder. Then in local security policy (administrative tools>Local Policies>Security Options) add the share name to "Network access: Shares that can be accessed anonymously". Reboot XP, and connect the Mac to the share. See if it disconnects this time. If you still have the issue, just undo everything you just did and put it back the way it was.
