Installed VPN/RAS/Routing, Can't map local drives again

Hi,

On a Windows 2003 server, I just installed routing/ras and enabled VPN access. Now
local workstations that have a drive mapped to a server share via "m:" get the "The
local device name already in use..."

I have heard about some conflicts with credentials if you map the same drive via the
VPN, then map the drive from a local workstation.

None of the users have yet accessed the VPN. Disabling the VPN/ras service was the
only way for them to get the mapping back.

This is only workgroup, no domains.

Anyone have ideas, or hit this problem before??

Thanks in advance,


JNK

It could be the name resolution issue because VPN is a virtual multihomed
server. This search may help.

Name resolution on VPNThat reason is that VPN server is a Virtual Multihomed
Server. The resolution is to disable NetBIOS Over TCP/IP and DNS register on
all interfaces including ...
www.chicagotech.net/nameresolutionpnvpn.htm


--
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


"jnk" <(E-Mail Removed)> wrote in message
news:O4UBD$(E-Mail Removed)...
> Hi,
>
> On a Windows 2003 server, I just installed routing/ras and enabled VPN
> access. Now local workstations that have a drive mapped to a server share
> via "m:" get the "The local device name already in use..."
>
> I have heard about some conflicts with credentials if you map the same
> drive via the VPN, then map the drive from a local workstation.
>
> None of the users have yet accessed the VPN. Disabling the VPN/ras service
> was the only way for them to get the mapping back.
>
> This is only workgroup, no domains.
>
> Anyone have ideas, or hit this problem before??
>
> Thanks in advance,
>
>
> JNK

Thanks Robert.

I followed the instructions on KB292822, and added the key ....DisableNetbiosOverTcpip.

One thing that did not fit the scenario was that this machine has no Active
Directory, and it does not have the role of WINS server, so I couldn't "clear the
WINS database" according to the arcticle.

After entering that key and re-enabling RRAS/VPN, a workstation or two just started
complaining again about not being able to map the network drives.

What might I be missing here?

Thanks,

Joel


Robert L (MS-MVP) wrote:
> It could be the name resolution issue because VPN is a virtual multihomed
> server. This search may help.
>
> Name resolution on VPNThat reason is that VPN server is a Virtual Multihomed
> Server. The resolution is to disable NetBIOS Over TCP/IP and DNS register on
> all interfaces including ...
> www.chicagotech.net/nameresolutionpnvpn.htm
>
>