Discussion Locked

mapped drive shows as disconnected, but isn't

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have mapped a server drive as g: on my WIN XP machine. After reboot, it shows as disconnected, but click on it and it opens. I can't remove the mapping and the g: doesn't show up in the list of mapped drives. I have full administrative rights to the PC. I have logged in as the administrator of the PC and the mapped drive still shows, even though I am not connected to the server.

9 replies

by master3bs

do you want to make the connection go away, or do you want to have it added to your list of mapped drives?

what happens when you try to remove the mapping? what process are you using?

by bmcglohon

The drive shows as disconnected. A right click mon it also shows it is disconnectred. I want to remove it completely, then I will want to map it back. We recently did a migration of our system from an old server to a new one. We moved from Windows 2000 to 2003. The mapped drive is on a n addditional server that did not change. The disconnected mapping happened as a result of this apparently.

by danaf

I have exactly the same problem. I've checked the event logs, but can't find anything that might cause them to (apparently random) appear.

by jwilliams

I am having the same issue on a 2003 SBS. I have even tried going into the registry and removing them this way (HKEY_CURRENT_USER\Software\Microsoft\CurrentVersion\Explorer\MountPoints2) then right clicking the drive i want to remove and deleting it. This may work for some of you others with this issue but didn?t work for me. Microsoft offer the explanation the Symantec may be the culprit (http://support.microsoft.com/kb/932463) If anyone has another suggestion for solving this issue, I would love to hear it.

by jwilliams

The last post with registry entry changes works fine after a restart. I posted too quickly. Sorry about that. Enjoy.

by mkilpatric

Within Group Policy, there is a setting that controls fast logon. This setting controls whether a user is initially logged on using cached credentials, and then group policy settings are processed in the background. This fast logon (on XP and greater) can affect redirected home drives, logon scripts that map drives, etc. It will not list them as active until the connection is actually established.

MK

This discussion is closed to new replies.