1 Answer
- Newest
- Most votes
- Most comments
1
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
route print
- 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.
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 days ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 months ago
Thanks for the info - I was able to connect to the remote NAS over VPN by limiting the route specifically for the NAS per your suggestion.