Disconnected Network Drives

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have several Windows XP machines that are acting very strange. Every
available drive letter is showing "Disconnected Network Drive." You cannot
disconnect these using the net use command. You also cannot map any new
drives because there are no available drive letters because all letters (E-Z)
are showing up as disconnected. I don't know what is causing this or how to
fix it. Any help would be appreciated.
 
We have several Windows XP machines that are acting very strange. Every
available drive letter is showing "Disconnected Network Drive." You cannot
disconnect these using the net use command. You also cannot map any new
drives because there are no available drive letters because all letters (E-Z)
are showing up as disconnected. I don't know what is causing this or how to
fix it. Any help would be appreciated.
Click to expand...

What exact error do you get if you do "net use e: /delete"? Are all of the
letters pointing to the same disconnected drive?
 
I have the same problem. This is the error that I get...

H:\>net use o: /delete
The network connection could not be found.

More help is available by typing NET HELPMSG 2250.
 
I had the same problem on a couple of my machines. Here is how I fixed my computer:

I went into the registry and looked under:
HKEY_USERS\..\Software\Microsoft\Windows NT\CurrentVersion\Network\Persistent Connections
for each user listed. In one of the users, it had a key named Save Settings. The value of this key was NO. I deleted the key and rebooted my machine.

My login script ran fine this time and the "Disconnected Network Drive" disappeared and I was able to map a new drive to that drive letter.

Hope this helps.

Dale
 
Anyone get an answer on this. I am having the same problem. It seems to be
machine related rathing than profile. I login in as domain admin on the
machine and get the same thing.
 
I have the issue too. It doesn't happen with the administrator and in
my case it DOES follow the user from computer to computer but
thankfully only affects this one user. I've killed their profile and
rebuilt it from scratch and it comes back. I'm afraid it will affect
more users. We use PC DOCS and it maps and unmaps a drive as it
accesses files. It can't function if all the drives are tied up with
this problem.

Ben
 
Did you ever find a solution for this problem? I am having the same problem
but am not finding any answers. Hopefully you'll see this right away and
have a solution for me.

Thanks.
 
[This followup was posted to microsoft.public.windowsxp.network_web and
a copy was sent to the cited author.]

We have several Windows XP machines that are acting very strange. Every
available drive letter is showing "Disconnected Network Drive." You cannot
disconnect these using the net use command. You also cannot map any new
drives because there are no available drive letters because all letters (E-Z)
are showing up as disconnected. I don't know what is causing this or how to
fix it. Any help would be appreciated.
Click to expand...

Here is the fix I used

1. Using regedit, delete entire key in the registry on XP machine

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explore
\MountPoints2

2. Reboot

Then remaps of drive can occur without issue.

Still NOT sure what caused it.

rick
 
I went from Novell to 2003 server and since I still have a few 98 systems
running I wasn't able to do a .vbs script. So in the container I put a batch
file using the net use command. On the 98 systems it shows the network
drives as being connected. On the 2000 and XP systems it shows them as being
disconnected but they're accessible. I've searched the group here and have
seen multitudes of people with the same problem, however I've only seen a few
guesses as answers. I've looked in the host file, checked the registry for
entries and some other things. Spyware isn't an option, or would a virus be.
I can't unmap these drives either and I've got too many users to want to go
to each system do tinker with them.

I will add this though, I looked up some info and wrote a .vbs script file
that had different drive letters then the 3 I use normally. They mapped when
I ran it from my desktop and don't show disconnected whereas the net use
command in a batch file does. I could use a login script for each user and
remedy this if I could get these drives disconnected.

Here's the .vbs script I used:

Dim objNet, strUserName

Set objNet = CreateObject("Wscript.Network")


strUserName =objNet.UserName

objNet.MapNetworkDrive "U:", "\\Picasso\Users\" & strUserName
objNet.MapNetworkDrive "R:", "\\Picasso\Public"
objNet.MapNetworkDrive "K:", "\\Picasso\SHARED"
WSCript.Quit

So if anyone knows how to get the disconnected drives removed, that would be
a big help and probably more than I've seen this error recieve in here.

Thanks,
gcobb

SFU Newbie said:
[This followup was posted to microsoft.public.windowsxp.network_web and
a copy was sent to the cited author.]

We have several Windows XP machines that are acting very strange. Every
available drive letter is showing "Disconnected Network Drive." You cannot
disconnect these using the net use command. You also cannot map any new
drives because there are no available drive letters because all letters (E-Z)
are showing up as disconnected. I don't know what is causing this or how to
fix it. Any help would be appreciated.
Click to expand...

Here is the fix I used

1. Using regedit, delete entire key in the registry on XP machine

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explore
\MountPoints2

2. Reboot

Then remaps of drive can occur without issue.

Still NOT sure what caused it.

rick
Click to expand...
 
I am not sure if this is the solution for all of these cases, but in my case,
Symantec client 10.0."something" caused this issue. Once I upgraded to
10.0.1."something" the problem went away.

Not exactly sure on the version numbers, but get the newest version...

gcobb said:
I went from Novell to 2003 server and since I still have a few 98 systems
running I wasn't able to do a .vbs script. So in the container I put a batch
file using the net use command. On the 98 systems it shows the network
drives as being connected. On the 2000 and XP systems it shows them as being
disconnected but they're accessible. I've searched the group here and have
seen multitudes of people with the same problem, however I've only seen a few
guesses as answers. I've looked in the host file, checked the registry for
entries and some other things. Spyware isn't an option, or would a virus be.
I can't unmap these drives either and I've got too many users to want to go
to each system do tinker with them.

I will add this though, I looked up some info and wrote a .vbs script file
that had different drive letters then the 3 I use normally. They mapped when
I ran it from my desktop and don't show disconnected whereas the net use
command in a batch file does. I could use a login script for each user and
remedy this if I could get these drives disconnected.

Here's the .vbs script I used:

Dim objNet, strUserName

Set objNet = CreateObject("Wscript.Network")


strUserName =objNet.UserName

objNet.MapNetworkDrive "U:", "\\Picasso\Users\" & strUserName
objNet.MapNetworkDrive "R:", "\\Picasso\Public"
objNet.MapNetworkDrive "K:", "\\Picasso\SHARED"
WSCript.Quit

So if anyone knows how to get the disconnected drives removed, that would be
a big help and probably more than I've seen this error recieve in here.

Thanks,
gcobb

SFU Newbie said:
[This followup was posted to microsoft.public.windowsxp.network_web and
a copy was sent to the cited author.]

We have several Windows XP machines that are acting very strange. Every
available drive letter is showing "Disconnected Network Drive." You cannot
disconnect these using the net use command. You also cannot map any new
drives because there are no available drive letters because all letters (E-Z)
are showing up as disconnected. I don't know what is causing this or how to
fix it. Any help would be appreciated.
Click to expand...

Here is the fix I used

1. Using regedit, delete entire key in the registry on XP machine

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explore
\MountPoints2

2. Reboot

Then remaps of drive can occur without issue.

Still NOT sure what caused it.

rick
Click to expand...
Click to expand...
 
At trick

Hi,
after spending an hour looking for a solution online, here's the one I found to work in my case:

the twist is to use a regular net use X: /delete command, but preceeded by the magical "at" xx:xx

you have to make sure that the task scheduler service is running on your machine, and then type this in a "cmd" window: (assuming the time is now 12:00)

at 12:01 net use X: /delete

this "at" schedule command will use NT AUTHORITY\SYSTEM to impersonate the following "net use" command, and thus will succeed where your domain admin account might fail.

wait till 12:01 and your disconnected network drive should disappear !

Regards,
 
Logout - login

Hi,
I had the same issue on a server I cannot restart. But the ghost drive disappeared after a logout/login.

Best Regards
 
pichosse said:
Hi,
after spending an hour looking for a solution online, here's the one I found to work in my case:

the twist is to use a regular net use X: /delete command, but preceeded by the magical "at" xx:xx

you have to make sure that the task scheduler service is running on your machine, and then type this in a "cmd" window: (assuming the time is now 12:00)

at 12:01 net use X: /delete

this "at" schedule command will use NT AUTHORITY\SYSTEM to impersonate the following "net use" command, and thus will succeed where your domain admin account might fail.

wait till 12:01 and your disconnected network drive should disappear !

Regards,
Click to expand...

oh, that's bloody brilliant.
thx. :thumb:
 
Back
Top