Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a standalone (non-domain) Windows Server 2008 R2 that I need to securely access using RDP from the public internet. I want to access it using the standard 443 SSL port, since other ports are most likely blocked within corporations and schools etc.
So I read about the Remote Desktop Gateway (former known as the Terminal Services Gateway). All the examples I have stumbled upon relies on a dedicated server for this role, gatewaying the traffic to the request server within the intranet.

So, can I install the Remote Desktop Gateway role to this standalone server without any issues? Essentially, it will then acting a a gateway for itself. I am planning on registering a dedicated host name, such as (this would also be used to purchase a SSL certificate) that the gateway will use. On the RD client, this would be the gateway name, and the actual remote server name would be the computer name of the server

Will this work?

share|improve this question
up vote 3 down vote accepted

Despite the overwhelming number of answers, I bit the bullet and tried it...
So far it seems to work.
So, yes, it seems that one can run the RD gateway role on a single server instance, RD'ing to itself.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.