| | |
Network Drive Volume Label
![]() |
I've been having this issue (at two separate clients) where all of the volume labels for the network drives that a user is connecting to get renamed as "Disconnected Network Drive." The icon shows that the drive is connected, and if you can access files on the network drive with no problem. This has happened at both locations in the past week so it seems to me that a recent MS update may have triggered this. All of the workstations with this issue are running Windows XP SP2 and the file servers at both sites are Windows Server 2003 (pre SP1).
I haven't found any solutions (though similar issues) on either Google, or on the MS support site.
Has anyone else come across this issue, even if you haven't found a fix yet?
Thanks in advance,
Brandon
I haven't found any solutions (though similar issues) on either Google, or on the MS support site.
Has anyone else come across this issue, even if you haven't found a fix yet?
Thanks in advance,
Brandon
PARANOIA:
A healthy understanding of the way the universe works.
A healthy understanding of the way the universe works.
•
•
Join Date: Jul 2005
Posts: 1
Reputation:
Solved Threads: 0
•
•
•
•
Originally Posted by i686-linux
I've been having this issue (at two separate clients) where all of the volume labels for the network drives that a user is connecting to get renamed as "Disconnected Network Drive." The icon shows that the drive is connected, and if you can access files on the network drive with no problem. This has happened at both locations in the past week so it seems to me that a recent MS update may have triggered this. All of the workstations with this issue are running Windows XP SP2 and the file servers at both sites are Windows Server 2003 (pre SP1).
I haven't found any solutions (though similar issues) on either Google, or on the MS support site.
Has anyone else come across this issue, even if you haven't found a fix yet?
Thanks in advance,
Brandon
Good luck and hope it works for you.
•
•
Join Date: Jul 2005
Posts: 1
Reputation:
Solved Threads: 0
Did this work for you guys?
I assume you had to reenable the Workstation Service after it was done.
I found a way to get rid of thsoe drives by using RegEdit at:
HKCU/Software/Microsoft/Windows/CurrentVersion/Explorer/MountPoints2
And deleting all the keys (Note keys, not Values) that have ## infront of them.
Explorer will now show (seemingly random) drivers at those points, but you can Disconnect them.
I'm just wondering if this is a longterm fix?
I assume you had to reenable the Workstation Service after it was done.
I found a way to get rid of thsoe drives by using RegEdit at:
HKCU/Software/Microsoft/Windows/CurrentVersion/Explorer/MountPoints2
And deleting all the keys (Note keys, not Values) that have ## infront of them.
Explorer will now show (seemingly random) drivers at those points, but you can Disconnect them.
I'm just wondering if this is a longterm fix?
![]() |
Similar Threads
- Mapping a network drive (Windows NT / 2000 / XP)
- Help on dedicated network drive please. (Networking Hardware Configuration)
- Windows 98se not able to map to network drive after demoting server (Windows 95 / 98 / Me)
- cannot format network drive problem (Windows 95 / 98 / Me)
- Set Performance Options in Windows XP (Windows tips 'n' tweaks)
Other Threads in the Windows NT / 2000 / XP Forum
- Previous Thread: XP Home: PC won't boot
- Next Thread: Gotcha!
| Thread Tools | Search this Thread |
.net 2007 2010 a.exe address alaris apache appstore arm auto automatically black blue book bulletin cellphones chkdsk collaboration computer computerfreezes crash cursor deployment desktop desktops dns dotnetnuke drive eartlink error errors explorer features folder fontmanagers format framework gadgets intel internet interoperability killprocess laptop linux load login mac memory microsoft mobile monitor motionle1600 netbooks novell nvidia open operatingsystems osx palm partition patch port printer product proxy remotedesktop remotedesktopconnection repair replacingraiddrive retrieve screen sharepoint simplifiedchinese sitetositevpn sp1 technology unreadable update usb verizon videodrivers videogames virtual virus vista visual vulnerability wab webos weecam win win32/heur window windows windows7 windowsxp windowsxpnotstartingup. worm xp xpde





