>>>>>>>>Does anybody know what event or whatever could indicate to me what goes on when I try to Map a network drive? I am connecting to a custom network (via VPN). This part works. But then when I try to map a network drive, it does not work. That is, after a message "attempting to connect..." goes on for about 30 seconds, the log in screen pops up again.
>>>>>>>>I can ping the drive IP though. So I am trying to figure out what is wrong with the way I am mapping the drive.
>>>>>>>>Thank you for any suggestions.
>>>>>>>
>>>>>>>Do you have permissions to access that drive? Not the same as permission to connect to the VPN..
>>>>>>
>>>>>>Yes. The customer checked it. They say I have full permissions to the drive (this is what they say).
>>>>>
>>>>>Yeah - they always say that at first...
>>>>>
>>>>>Can you access ANY resources on their network?
>>>>
>>>>I can map another drive on their network. This is very big organization with probably hundreds of servers. I am suppose to have access to 2 of them. One I can map. Another, no. It used to be that it was not a problem when it was just one server. Then they added another. And it seems (if my memory services me right) that since then I started having a problem mapping the initial server.
>>>
>>>Sometimes DNS can't resolve server names to IP addresses. With VPNs you sometimes get your DNS server settings changed while your session is active. IAC the most reliable way I know to map a drive letter is to use the server's IP address and the share name:
>>>

>>>net use x: \\192.168.123.123\ShareName /persistent:y
>>>
>>>REM If you have to supply a user account and password:
>>>net use x: \\192.168.123.123\ShareName password /user:domain\account /persistent:y
>>>

>>
>>If I have to supply user name and password, do you enter the password in quotes? like "mypassword" ? and the same with user name? What is the /persistent:y for?
>
>No, you don't need quotes around the password (hopefully your password doesn't include any spaces). In a Windows domain, the "domain" will be the domain name, if no domain it's the machine name (I've never tried an IP address with that parameter).
>
>The "persistent" flag tells Windows to remember the mapping across shutdowns of your computer. You may or may not want that, if you include it and the drive isn't available you get the Windows messsage "Not all your network drives could be connected". I usually DON'T use it, instead I create a little .CMD file with the command, so I can easily run it each time I connect to resources via VPN or on LANs other than my own.

Thank you very much. I tried it all as you suggested and still cannot map. Must be something with either my PC or permissions.