Hot answers tagged remote-desktop-gateway
Gateway wins for me every time. If your clients are running a modern OS (read: XP SP3 or above) with NLA, you can expose dozens or hundreds of terminal servers behind a single interface with a single point of entry. This makes applying NAP much easier, along with controlling who can go where and connect to what. A VPN is more universally accepted (I.e. ...
I think you're on the right track with everything you've said. There really isn't any easier way to get the kind of authentication scenario you're looking for. Assuming that the physical security in the datacenter is reasonable I think both choices you've outlined have roughly the same exposure. The read-only domain controller (RoDC) being at the datacenter ...
Apparently MS botched the instruction somewhat. I believe you need to create the cert request in iis manager on the rdg gateway computer. The request needs to specify the fqdn used by the clients to connect over the internet. For processing the request signing you use a CA trusted by your client computers. If you have full control over the client computers ...
Since the TS gateway is effectively a proxy, why don't you query the proxy's logs? Filtering for the last event 303 from Remote Desktop Gateway by the user in question should supply you with the IP. I am not aware of any "X-Forwarded-For"-style header in RDP.
This is not supported on Windows 2008 R2, but will be supported in Windows 8. http://microsoftplatform.blogspot.com/2011/10/running-rd-gateway-on-different-port.html However, to connect to an address on a different port, you would use the following syntax. In my example, i'm connecting to port 444 http://rdg.domain.com:444/
Only top voted, non community-wiki answers of a minimum length are eligible