![linux pcoip zero client linux pcoip zero client](https://m.media-amazon.com/images/I/61n5KeO7EgL._AC_SX450_.jpg)
This protocol is much more efficient and faster than Citrix (which is the basis for Microsoft Remote Desktop "RDP" protocol). This is because Amazon WorkSpaces uses Teradici PCoIP which is a totally different product with a totally different protocol. You're going to find that Remote Desktop Connection isn't as nice as the Amazon WorkSpaces client. If you want to be more elegant, register your WorkSpace's public IP in DNS (Amazon Route 53 or ).
#Linux pcoip zero client Pc
I dont want to give my users a power hungry PC that needs a windows license and a virus scanner just so they. Its not clear if this just isnt supported or it really wont work. Allowing PCoIP zero clients and thin clients to connect would be great.
![linux pcoip zero client linux pcoip zero client](https://www.leadtek.com/p_images/zoom/641_1Z.jpg)
Just use the IP address for your WorkSpace that you found in your EC2 console. A Linux client would be good, lots of people use Linux. Now you can log in using "rdesktop" on Linux or Remote Desktop Connection on Windows. In the EC2 Console, poke around to find the public interface associated with that private IP address you wrote down and write down its public IP address.Īgain, in your EC2 Console, find the Security Group associated with the public interface you found in the previous step.Įdit the Security Group associated with the public interface. Essentially, you are figuring out what private IP your WorkSpace is using. Then open a cmd prompt and type ipconfig. It won't be as fast or as nice but it works fine with some EC2 Console tweaking.įirst, open your WorkSpace and ensure that Windows Firewall has opened TCP port 3389. Here is how you can use regular "rdesktop" on Linux and Macintosh, or Microsoft Remote Desktop Connection on Windows to connect to Amazon WorkSpaces. You do not have to use the Amazon WorkSpaces client to reach your WorkSpace.