This could happen if
1. You username for the VPN connection and the username on the remote domain a
re the same and have different passwords.
2. if you use 3rd Party RADIUS implementation than Microsoft Routing and Remote Access or a Microsoft Radius Server.
Case 1: Same username
If the problem is the same username use for the VPN connection and remote domain then this is expected behaviour. When a VPN connection is established, Windows 7 will cache those credentials. It then will use the cached credentials for accessing local resources as well if the username is the same. Since the cached password is not correct for the domain, it results in access denied for the local resources.
To resolve the problem,
Simply use different username for the VPN connection and the remote domain. Or, fix it the insecure way by setting the password on the VPN connection to be the same as that of the remote domain. This is not recommended though.
Case 2: 3rd Party RADIUS implementation
To resolve the problem, simply do the following:
1. Search and locate the .pbk file that contains the entry that you dial.
2. Edit the file in Notepad and locate the following entry:
3. Modify the entry to the following:
4. Save the file and that should fix the problem.
Incoming search terms:
- Access denied to remote resource (8)
- userascredentials (5)
- dfs over vpn (5)
- userascredentials windows 7 (4)
- cache access denied vpn (3)
- windows 7 access denied dfs share (3)
- windows 7 copy filename lpt1 access denied (2)
- dfs vpn access denied (2)
- win 7 net use lpt access denied (2)
- windows 7 access denied to dfs share (1)