Windows Forum

Ask something
Discussion Locked

Mapping drive through Cisco VPN

0 helpful
13 replies

by dagnasty 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a client that is connecting to our network via the Cisco VPN client. They connect succesfully but can not map to a network drive. When they try to they are told that it drive is not found on the network. If they ping it, they find it and it resolves. When they try to map in DOS it says they are not authorized. I assumed this to be because they were using the default user logon information from windows so we changed it to prompt but back in Windows it says there is no domain server to authenticate against.

I had him check his WINS configuration Tab under TCP/IP properties. The "Use DHCP for WINS Resolution" is not selected. It is not available as an option because under the IP Address tab he has specified IP Addresses. He cannothave it obtain an IP address automatically because locally there is no DHCP. IP's are all issued statically because it is required to run under a secureNAT client.

Any thoughts ?

13 replies

by sgt_shultz

i think this is because mapping to a network drive is full of security issues? why does he need to map a drive? database? let us know more and maybe we can help with a workaround if others confirm this cannot be done...

by dagnasty

we've given him access to this particular drive in order for them to drop files on the network as a secure method to transfer (yeah... wasn't my idea... just what I am stuck working with!)

We figure it must have something to do with the fact thathe is not running DHCP. I'm confident that there's some way this will work and we are sifting through all the VPN documentation but hoped someone might be able to provide us with an answer quicker than we might find one.

Let me know what other type of information you need and I'll gladly provide it.

Thanks for your reply.

by dagnasty

Thanks, we do have the exact same instructions we have provided to our client. Still did not work

thank you for your time... much appreciated

by ctmoore1998

Since they can ping the address ie ping 192.168.0.22 sounds like the connection is okay. His home network can't be in the same network ie 192.168.0.0 255.255.252.0 (your VPN network) his PC can't have a network of 192.168.0.xxx to 192.168.4.xxx as this is the same network. You have to guest logon enable and the use the guest password in the NET USE statement. IE NET USE G: \\server\share password -password- DO a NET USE /? |more for more help on the net use command Once you can successfully use the NET USE from the command prompt you can use a batch file to run from a shortcut on the desktop. Usually you can have the cisco vpn server assign a DHCP pool for the the VPN clients. Also make sure the guest acct has rights to the shares you want access to. I found on my cisco VPN client that was dialing in to his own network that I couldn't map drives because the NIC had a IP in the host network ie 10.0.0.xxx and my server was assing 10.0.0.xxx for the client once I disabled the NIC then the session was okay.

by binarysleeper

It sounds like the VPN Client PC cannot resolve to the Domain Controller. Try putting a line like this in you %systemroot%\system32\drivers\etc\lmhosts file
172.16.240.1 domaincontrollername#DOM:DOMAINNAME

Just replace the appropriate bits, i.e.IPaddress, domaincontrollername, and DOMAINNAME. This should let the client PC know where to authorize to when logging on with that domains credentials. Hope that makes sense and sorts it for you.

by dagnasty

Thanks for the suggestion, tried it and did not work. Still receiving exact same problem.

Appreciate the effort... many thanks

by ctmoore1998

Some more information on this. If the the client is 98 then. In Network neighborhood make sure you are using Microsoft client for networks in the primary network login. Then make the windows user name and password the same as the Domain logon thatyou are using (You Must create a user for this person and make sure that the use has remote/vpn logon rights. Next select in the vpn client to prompt for network logon, this will log you into the domain. Now you should be able to create a script to map network shares. I've found the most reliable way is to use the ip\share example: Net Use f: \\192.168.100.100\company where the IP address is the server's IP and company is a folder with the share name company to keep the shares from showing upin Network neighborhood put a $ at the end ie company$ This should get that user up and running. If they have a good user acct on client already use that user name for the new use on domain that way they won't have to re-enter all the passwords onthe client workstation otherwise if they change the user name there any previous cached passwords will have to be re-entered.

This discussion is closed to new replies.