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