"The local device name is already in use" error on dial up

  • Thread starter Thread starter rvanloon
  • Start date Start date
R

rvanloon

I have a strange one.

A user running Windows XP on his laptop. Everything works fine when
connected to the LAN. When he dials-up to a partnered ISP that has a
direct connection to our internal WAN though he gets the following
error when trying to access network drives mapped by the login script:

An error occurred while reconnecting DRIVE to \\SERVER\SHARE

Microsoft Windows Network : The local device name is already in use.

This connection has not been restored.

If he tries to use drives he has mapped himself (to the same servers)
then he is prompted for a username and password and after putting it in
that drive mapping works. If now goes to use the drive mapping from
the login script they produce the same error.

The login script maps the drives as follows:


net use i: /del /yes > NUL

net use n: /del /yes > NUL

net use p: /del /yes > NUL

net use s: /del /yes > NUL

net use w: /del /yes > NUL

net use i: \\SERVER\SHARE > NUL

net use n: \\SERVER\SHARE > NUL

net use p: \\SERVER\SHARE > NUL

net use s: \\SERVER\SHARE > NUL

net use w: \\SERVER\SHARE > NUL

None of these mappings conflict with local drives. I have tried
dialling up, disconnecting all the drives and then running the login
script manually but it simply hangs at the first drive mapping. I have
tried pinging the SERVER over dial-up and no problem there.

I highly doubt the issue is with the login script, RAS config, or
server because over a hundred other users are set up in the same way
and do not have any issues.

Interestingly enough, whenever an attempt is made to access the login
script mapped drives via dial up there are errors logged on the servers
indicating a bad username and password. The username and password in
the log shows the username and password used for his dial-up
connection. After I found this I tried the hotfix in this article as
it sounded exactly like my issue:

http://support.microsoft.com/default.aspx?scid=kb;en-us;326570&Product=winxp

Unfortunately, no luck. I also upgraded him to Service Pack 2 and no
difference. Finally, I disabled "Client for Microsoft Network" from
the dial-up connection bindings but again it made no difference. The
same mapped drive error occurs and authentication errors come up on the
server. Yet, manually mapped drives using other letters work fine and
all works well when connected directly to the LAN.

The laptop is part of the domain so he uses cached credentials before
dialing up. Those cached credentials do match his current username and
password.

Any ideas?
 
since he is only person has this issue and other users work fine, he may has a manual persistent mapping. Try this command: net use * /del. that will delete all mapping and then run the logon script. Please post back with the result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I have a strange one.

A user running Windows XP on his laptop. Everything works fine when
connected to the LAN. When he dials-up to a partnered ISP that has a
direct connection to our internal WAN though he gets the following
error when trying to access network drives mapped by the login script:

An error occurred while reconnecting DRIVE to \\SERVER\SHARE

Microsoft Windows Network : The local device name is already in use.

This connection has not been restored.

If he tries to use drives he has mapped himself (to the same servers)
then he is prompted for a username and password and after putting it in
that drive mapping works. If now goes to use the drive mapping from
the login script they produce the same error.

The login script maps the drives as follows:


net use i: /del /yes > NUL

net use n: /del /yes > NUL

net use p: /del /yes > NUL

net use s: /del /yes > NUL

net use w: /del /yes > NUL

net use i: \\SERVER\SHARE > NUL

net use n: \\SERVER\SHARE > NUL

net use p: \\SERVER\SHARE > NUL

net use s: \\SERVER\SHARE > NUL

net use w: \\SERVER\SHARE > NUL

None of these mappings conflict with local drives. I have tried
dialling up, disconnecting all the drives and then running the login
script manually but it simply hangs at the first drive mapping. I have
tried pinging the SERVER over dial-up and no problem there.

I highly doubt the issue is with the login script, RAS config, or
server because over a hundred other users are set up in the same way
and do not have any issues.

Interestingly enough, whenever an attempt is made to access the login
script mapped drives via dial up there are errors logged on the servers
indicating a bad username and password. The username and password in
the log shows the username and password used for his dial-up
connection. After I found this I tried the hotfix in this article as
it sounded exactly like my issue:

http://support.microsoft.com/default.aspx?scid=kb;en-us;326570&Product=winxp

Unfortunately, no luck. I also upgraded him to Service Pack 2 and no
difference. Finally, I disabled "Client for Microsoft Network" from
the dial-up connection bindings but again it made no difference. The
same mapped drive error occurs and authentication errors come up on the
server. Yet, manually mapped drives using other letters work fine and
all works well when connected directly to the LAN.

The laptop is part of the domain so he uses cached credentials before
dialing up. Those cached credentials do match his current username and
password.

Any ideas?
 
Back
Top