If you look at the network interfaces on your Workspaces you will see that there are two - one which connects to your VPC and another which is used for streaming traffic (keyboard, mouse, pixels, etc. that are delivered to and from the client machine you're using to access the Workspaes instance).
When you set up a VPN connection it will (by default) send all traffic from the Workspaces instance to the VPN endpoint - this breaks the streaming traffic because that traffic must use the network interface that is designated for streaming traffic.
To resolve this you can do two things:
- Exclude the routes used for that network interface. You can find the routes in the Windows route table by running
- Set up the VPN so that you limit the access over the VPN to just the corporate NAS IP address (or another smaller set of IP addresses). Because that doesn't include the range that the streaming interfaces uses it won't interfere with that traffic.
Connect Windows 10 WorkSpace to Amazon Linux 2 EC2 Instanceasked 6 months ago
Unable to access internet from my laptop when I connect to a VPC using client VPNAccepted Answerasked a month ago
Connect remote sites using VPN to access on-prem via existing Direct Connect?Accepted Answerasked 6 months ago
Trying to port a number to connectasked 3 years ago
How to apply Patch for windows workspace instance?Accepted Answerasked 3 years ago
unable to connect to VPN in linux OS on django app on amazon lightsail
Connect to VPN using Amazon Lightsail instance
How to connect Workspace (Windows 10) to L2TP/IPSec VPN serverasked 4 months ago
Connection to external VPN from Windows Server 2016asked 7 months ago
How to connect AWS VPC from ARM CPU?asked a month ago