Remote Desktop Services – Connection Errors

KB ID 0001132 Dtd 16/01/16

Below is not an exhaustive list of connection errors, it's just a some things that have tripped me up. If you have a nasty error that you have fixed, feel free to drop me a line, send me some screenshots and the fix, and I'll add them as well.

General Errors server you are connecting to error

Your computer can't connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance.

Solution for Windows 10: I struggled with this for a while, all forum posts refer to windows 7/8 and the problem was caused by a windows update (KB2592687), that needed to be removed. But I was connecting with Windows 10? This  was the resolution;

Windows 10 RDP Error

Create/Edit a 32 bit DWORD value called RDGClientTransport in your registry at;

HKCU > SOFTWARE  >Microsoft > Terminal Services Client

Also See¬†Remote Desktop Web Access ‚Äď Connection Error

Remote Network Access Protection Error

Your computer can't connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator.Contact your network administrator for assistance.

You normally see this error if one (or more), of your Remote Desktop Role servers does not have the correct certificate installed on it, (or the certificate it does has has expired).

Server Manager > Remote Desktop Services > Collection > Task > Select your collection > Task > Edit Deployment Settings > Certificates > Check and reinstall each one as required.

RDS Certs

Remote Desktop Gateway Errors

RemoteApp Error RDSG

Your computer can't connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address.

RemoteApp Error Gateway

Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.

IIS Settings remote desktop gateway name

The machine trying to connect needs to be able to resolve the 'public name' of the Remote Desktop Gateway server. And this may not be the hostname of the server! As you can see in the image above the Gateway server name is set to The important thing is when I ping this name, it resolves to the correct IP address, (mine responds to pings, yours probably wont if you're connecting though a firewall.)

IIS Settings remote desktop gateway

In some cases you need to set the public name of the the Remote Desktop Gateway server, in the servers IIS Settings. On the Gateway server > Start > Administrative Tools > Internet Information Services (IIS) Manager > {Server-name} > Sites > Default Website > RDWeb > Pages  > Application Settings > Set 'DefaultTSGateway' to the public name of the gateway server. Then from command line run 'iisreset' to restart the web services.

Gateway Server Certificate Expired

Your computer can't connect to the remote computer because the Remote Desktop Gateway server's certificate has expired or has been revoked. Contact your network administrator for assistance.

In most cases this should be easy to fix, if you use self signed certificates make sure your CRL settings and/or OCSP settings are correct. If you use a publicly signed cert make sure your client can contact the publishers CRL (look on the properties of the certificate).

Check the Obvious: It saying the RDG cert has expired, make sure it's in date! In the Gateway Server Launch Server Manager > Remote Desktop Services > Collections > {Collection-name} > Tasks > Edit Deployment Properties.

Remote Desktop Services Certificate Settings

Certificates > RD Gateway > View Details > Is it in date?

Remote Desktop Services Change Certificates

Everything is OK? But I'm Still Getting This Error? Are you publishing the Gateway with something else like Web Application Gateway? Threat Management Gateway? Load Balancer? Look in that direction.

Also See¬†Remote Desktop Web Access ‚Äď Connection Error

Related Articles, References, Credits, or External Links


Author: PeteLong

Share This Post On


  1. Hello Pete,

    Thanks for this article.
    This registery entry fixed my error.
    I was wondering tho what this entry actually does in the background for troubleshooting reasons and because this kinda is a work arround and not fixing the cause of the issue.
    I am looking forward to your reply.

    Kind regards,


    Post a Reply
    • If I had to guess, I would say it allows RDP session to be sent via a gateway server (by default). In some cases you only have one RDP server, with all the roles on so, that would appear not to make sense.

      Post a Reply
  2. Thank you so much for this article!! I’ve been trying to fix this issue for weeks since I upgraded to Windows 10.

    Post a Reply
  3. This registry entry fixed my error as well. Thanks so much for this post!

    Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *