Discussion Locked

Net Use strange behavior in VPN

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Win2000 server stand-alone and I am trying to connect through a VPN connection to an NT4 network. After establishing the connection, I try to map a drive using net use * \\servername\sharename /user: domain\admin password. But it always responds that the network path was not found. Now, the machine is able to query the WINS server and so pinging any server by name is fine. When I dial-in to the network and I map a drive through the same procedure (it works fine) and I disconnect the dial-in the mapped drive gets the red cross (for disconnected). After this I establish the VPN connection again and when I double click on the mapped drive on Explorer it works just fine. Trying to map another drive through net use * ... still doesn't work. I am confused with this behavior. Any help appreciated.

7 replies

by mckaytech

Hmmm... very interesting. Since you can establish a drive mapping using dial-in and maintain it with the VPN but not map a new drive, I'm wondering if your server is having a hard time finding the domain controller through the VPN. I'm thinking that your server is getting an access token through the dial-in and that explains how it can continue to find the share but when you try and map a new share through the VPN, it can't find it's way to a domain controller to get that new token.

Have you tried an LMHosts file on the W2K server pointing to the IP for a domain controller?

paul

by mike

Try using the IP instead of the unc ie net use x: \\xxx.xxx.xxx.xxx\sharename if that works fine then go ahead and use a hosts file or lmhosts, or you can just stick with teh ip instead of the unc, the users are none the wiser!
Mike

by james_randy

That was a very thoughtful and thorough first answer. Why don't you go ahead and accept that answer and close the question.

This discussion is closed to new replies.