Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have an issue connecting to a network share from Windows 7 Professional client to Windows Server 2008 R2.

Here are the particulars of the issue:

  1. When outside of the office, I log in to the computer as my AD domain user
  2. I then bring up my VPN connection to the office, this is OK
  3. I try and connect to a mapped network drive, which is mapped by NetBIOS hostname P:\ => \\myserver\departments, but I get the error invalid username or password, I am not prompted for any credentials
  4. I check that the VPN adapter is set on the top-most of the Adapters and Bindings of Advanced Settings of Network Connections in the Control Panel
  5. I see that the hosts file to contain the IP address of the server to remove the possibility of NetBIOS name resolution issues

The strange thing is that I am not prompted for credentials, Windows Explorer simply says invalid username or password when attempting to open the mapped drive.

Disconnecting the mapped share, and reconnecting once connected via VPN works perfectly, and I am not prompted for credentials.

Any idea why this is and what can be done so I do not face the same issue each and every time I log in?

share|improve this question
    
Do the mapped drive and the VPN connection use the same credentials? –  joeqwerty Dec 19 '12 at 4:16
    
The credentials for the vpn are different from the active directory user account. Would that have any affect? –  g18c Dec 19 '12 at 4:40
    
Yes it would. Accessing resources while connected via a VPN connection (assuming you're using Windows RRAS as the VPN server) will use the VPN credentials to access those resources. –  joeqwerty Dec 19 '12 at 4:59
    
Thanks @joeqwerty, the VPN is provided by a hardware router. Is there anyway to change this behaviour and separate the use of VPN credentials with mapped drive credentials? It is strange that once the VPN is up (and I get this error), disconnecting the mapped drive and remapping the drive does not give this error and is OK. –  g18c Dec 19 '12 at 5:51
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.