Mapping network drive fails because already mapped

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

Guest

When I try to map a network drive and logon to the mapped drive as a different user, it gives me an error message saying that it is already mapped when it isn't. The problem is described exactly in Microsoft Knowledge Base Article - 812793 and it says there is a fix but it doesn't say what the fix is. I'm using XP Home and have all the available downloadable updates. Anybody know how to fix this problem?
 
Make sure no network documents are being used, including
email.
Run these commands:
c:
cd \
net use * /d /y
NET USE /persistent:no
nbtstat -R
nbtstat -RR
ipconfig /release
ipconfig /flushdns
arp -d *
ipconfig /renew

What you have is Microsofts extremely persistent
connections.
Search the registry for "persistent connections". Change
all yes values to "no" as shown:
[HKEY_CURRENT_USER\Software\Microsoft\Windows
NT\CurrentVersion\Network\Persistent Connections]
"SaveConnections"="no"

After this, you ought to be able to map again.
-----Original Message-----
When I try to map a network drive and logon to the
Click to expand...
mapped drive as a different user, it gives me an error
message saying that it is already mapped when it isn't.
The problem is described exactly in Microsoft Knowledge
Base Article - 812793 and it says there is a fix but it
doesn't say what the fix is. I'm using XP Home and have
all the available downloadable updates. Anybody know how
to fix this problem?
 
Jeff, you are my hero! Your solution worked like a charm. One other interesting thing I found is that I still get the same error message if I use the "Browse" button to find the network drive I want to map but if I type in the path to the same drive it works... Gotta love Windows!!

----- JeffO wrote: -----

Make sure no network documents are being used, including
email.
Run these commands:
c:
cd net use * /d /y
NET USE /persistent:no
nbtstat -R
nbtstat -RR
ipconfig /release
ipconfig /flushdns
arp -d *
ipconfig /renew

What you have is Microsofts extremely persistent
connections.
Search the registry for "persistent connections". Change
all yes values to "no" as shown:
[HKEY_CURRENT_USER\Software\Microsoft\Windows
NT\CurrentVersion\Network\Persistent Connections]
"SaveConnections"="no"

After this, you ought to be able to map again.
-----Original Message-----
When I try to map a network drive and logon to the
Click to expand...
mapped drive as a different user, it gives me an error
message saying that it is already mapped when it isn't.
The problem is described exactly in Microsoft Knowledge
Base Article - 812793 and it says there is a fix but it
doesn't say what the fix is. I'm using XP Home and have
all the available downloadable updates. Anybody know how
to fix this problem?
 
Back
Top