I have been having issues with the latest version of workspaces running on MS Windows 10. In some cases the Teradici PCOIP driver attempts to bind a UDP port to an interface which fails due to a permission denied error. The machine I was having issues with has several physical and virtual interfaces including OpenVPN TAP adapters and HyperV interfaces as well as VMWare virtual NICs, Ethernet and Wifi. The permission denied error occurred when attempting to bind to Wifi. The Teradici driver didn't attempt to use a different interface - instead the connection fails.
The target Workspace is running Amazon Linux 2 in the us-east-1 region. Disabling UDP transport didn't make any difference.
I was able to workaround the issue by disabling NICs when using Workspaces so that a usable NIC was always selected. I am not entirely sure how Teradici selects the NIC to bind to.
Is this a known issue and is there any chance of getting the problem resolved?
AWS 官方已更新 2 年前
This does precisely answer the question thank you!
I really don't understand why - being able to use consumer grade software on a machine with any form of virtualization - would be considered not a valid use case / not worth fixing. I don't think that most user's experiencing this issue would know what/where/how to diagnose the issue or implement the workaround. It took me a while to just figure out what the right question would be to ask!