Mapped drives for VPN clients from computers not joined to the domain
Mapped drives for VPN clients from computers not joined to the domain.
I am wondering how others handle this situation. When connecting to VPN on a computer that is domain joined we can map our network drives for our users and this works fine.
However for non domain joined computers connecting the drives prompts for password since it tries local windows credentials.
Is it even possible to map drives from a VPN Client and use the VPN client credentials for example which are domain credentials?
Or are there other ways to handle this?
I am wondering how others handle this situation. When connecting to VPN on a computer that is domain joined we can map our network drives for our users and this works fine.
However for non domain joined computers connecting the drives prompts for password since it tries local windows credentials.
Is it even possible to map drives from a VPN Client and use the VPN client credentials for example which are domain credentials?
Or are there other ways to handle this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What about using RDP over VPN? This is the simplest solution.
...or RD over RD Gateway. No special VPN client needed, and more secure (you have to really screw up to make RD Gateway insecure. VPN is insecure by default once someone connects.)
ASKER
we already using RD over RD gateway... however for security reasons we do not allow files to be transferred and some apps we do not run on remote desktop.
with VPN we can check the local system is secure before connecting then allow files to be transferred and other apps locally
with VPN we can check the local system is secure before connecting then allow files to be transferred and other apps locally
Then when mapping for the username use the format domain\user not just the user name