I've set up some instances on Amazon AWS that have RDP enabled. I can log in to these instances just fine from my home network. There is no domain behind the instances, there are only local accounts.
However, I want to be able to access them from corporate networks that block RDP. In order to get around firewall restrictions, I've added an RDP GateWay server with a signed certificate. Using my OS X RDP client ("Microsoft Remote Desktop.app"), I can connect to the instances just fine through the RDP GW.
However, when I'm using Windows (7, 8, 10), it doesn't allow me to connect. The login prompt below jus keeps respawning, without any feedback whatsoever. I'm sure the credentials are correct. The title refers to the GW, but the target is the actual EC2 instance. I've tried credentials for both the GW and the EC2 instance.
What I've tried
- In the GPO, set
LAN Manager Authentication Levelto
Send NTLMv2 response only. I did this both on the gateway and my local computers.
- Use different computers (Windows 7 without domain, Windows 8 with domain, Windows 10 without domain). (Only OS X works)
- Using the same credentials on the GW and the EC2 instance.
- Exporting the RDP configuration from OS X and opening it with windows.
Logs on Gateway
When connecting from OS X:
The user "WIN-XXXXXX\USERNAME", on client computer "xx.xx.xx.xx", met connection authorization policy requirements and was therefore authorized to access the RD Gateway server. The authentication method used was: "NTLM" and connection protocol used: "HTTP".
When connecting from windows, nothing is shown
When I monitor everything through WireShark, no traffic occurs when using the gateway (on windows), while I do see everything on OS X+GW and windows w/o gateway. It doesn't try to resolve my gateway dns, it doesn't try to connect to it; nothing! It just gives me the login prompt, I enter credentials and press enter, and the prompt resets.