Your computer can t connect to the Remote Desktop Gateway server

Symptoms

When this issue occurs, you receive the following error message that prevents you from accessing the Remote Desktop Services (RDS) server:

Nội dung chính Show

Hotfix information
your computer can't connect to the Remote Desktop Gateway server (Windows 2019)
What causes the ‘Your Computer Can’t Connect to the Remote Desktop Server’ Error on Windows 10?
Create a New Registry Key ‘RDGClientTransport’
RDP error: This computer can’t connect to the remote computer
Check the RDP Network Connectivity
Cách khắc phục một số lỗi sử dụng Remote Desktop trên Windows 10

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.

Additionally, you have to restart the RD Gateway service to regain the access.

You may also notice that the Terminal Services Gateway (TSGateway) svchost.exe process is taking excessive CPU time.

Hotfix information

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

your computer can't connect to the Remote Desktop Gateway server (Windows 2019)

We are having issues all of a sudden with our Windows 2019 RD Gateway not forwarding external user traffic to the rd session hosts.

We see the error "your computer can't connect to the Remote Desktop Gateway server" when clients attempt to connect.

We've applied windows updates KB5003541 and KB5003711 this past weekend. Not sure if that could have caused any issues.

Any feedback would be appreciated.

I'm also seeing this warning in the event viewer. Not sure if this is a problem:
The server's security layer setting allows it to use native RDP encryption, which is no longer recommended. Consider changing the server security layer to require SSL. You can change this setting in Group Policy.

windows-server

Comment

Comment Show 0

Comment

5 |1600 characters needed characters left characters exceeded

▼

Visible to all users
Visible to the original poster & Microsoft
Viewable by moderators
Viewable by moderators and the original poster
Advanced visibility

Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JiaYou-MSFT answered • Jul 30, '21 | JiaYou-MSFT edited • Jul 30, '21

HI HenryNiekoop-2622,

There is a thread, could you please check if it can help you?

RD gateway Server-side fix

Set the EnforceChannelBinding registry value to 0 (zero) to ignore missing channel bindings on the Gateway server. To do this, locate the following registry subkey, and use the given specifications:

HKLM\Software\Microsoft\Windows NT\CurrentVersion\TerminalServerGateway\Config\Core

Type: REG_DWORD
Name: EnforceChannelBinding
Value: 0 (Decimal)
Note: By default, the EnforceChannelBinding value does not exist on the Gateway server. You must create this value.

Working from home challenges–Remote Desktop Gateway Server does not work
https://blog.wisefaq.com/2020/06/10/working-from-home-challenges-remote-desktop-gateway-server-does-not-work/
Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice.
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Comment

Comment Show 0

Comment

5 |1600 characters needed characters left characters exceeded

▼

Visible to all users
Visible to the original poster & Microsoft
Viewable by moderators
Viewable by moderators and the original poster
Advanced visibility

Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HenryNiekoop-2622 answered • Jul 29, '21 | HenryNiekoop-2622 commented • Jan 3, '22

If I add the following registry on a windows 10 client it works. Can I make any changes on the server to make it work without having to do it on each client?

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

HKCU > SOFTWARE >Microsoft > Terminal Services Client

Set its value to ‘1’ (one).

Comment

Comment · Show 2

Comment

5 |1600 characters needed characters left characters exceeded

▼

Visible to all users
Visible to the original poster & Microsoft
Viewable by moderators
Viewable by moderators and the original poster
Advanced visibility

Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GregM-7676 · Jan 03 at 07:34 PM

Were you able to get around this issue without having a create a registry value? Having the same issue on Windows 10.

0 Votes 0 ·

HenryNiekoop-2622 GregM-7676 · Jan 03 at 08:08 PM

I had to add the registry key on the server to make it work. Still not sure what changed all of a sudden that required me to make this change.

0 Votes 0 ·

HenryNiekoop-2622 answered • Jul 30, '21

Tried it and get this now for some users.

image.png (9.8 KiB)

Comment

Comment Show 0

Comment

5 |1600 characters needed characters left characters exceeded

▼

Visible to all users
Visible to the original poster & Microsoft
Viewable by moderators
Viewable by moderators and the original poster
Advanced visibility

Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HenryNiekoop-2622 answered • Jul 30, '21

Disregard the last error. It was a permissions issue. The accounts were added to the wrong group. It works.

Comment

Comment Show 0

Comment

5 |1600 characters needed characters left characters exceeded

▼

Visible to all users
Visible to the original poster & Microsoft
Viewable by moderators
Viewable by moderators and the original poster
Advanced visibility

Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

What causes the ‘Your Computer Can’t Connect to the Remote Desktop Server’ Error on Windows 10?

Well, after a little bit of research, we came across the real reason behind the error message which is unknown to many. The error is caused due to the following reason —

HTTP/UDP Connection: The issue seems to be caused by the use of HTTP/UDP connection by the RDP client. To fix this, you will have to force it to use RPC-HTTP connections over HTTP/UDP. This can be easily done by adding a new key to your Windows Registry.

Now, to fix your issue, you will have to follow the solution provided down below. An administrator account will be needed as you are going to add a new key in the Windows Registry.

Create a New Registry Key ‘RDGClientTransport’

The solution to the said issue is pretty easy and straightforward. You will just have to add a new DWORD key in the Windows Registry by the name ‘RDGClientTransport’. What this does is make the RDP client use RPC-HTTP connection over HTTP/UDP connection. This is how to add the key:

Go to the Start Menu, type in Run and then hit Enter to open up the Run dialog box.
Once it loads up, type in ‘regedit’ and then press Enter.
This will open up the Windows Registry. Now you will have to navigate to the following directory:HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client
You can either navigate to it by expanding the specified folders or just pasting the above path in the address bar.
Once you are there, right-click on the right-hand side pane, move your cursor to New and then select DWORD (32-bit).
Name the newly created key as RDGClientTransport and then double-click it to change its value.
RDGClientTransport Key
Set the value to 1 and then click OK.
Changing the Value
Close the Windows Registry.
Try to connect again.

This will probably fix your issue and you should be able to connect to the remote system again.

9 Replies

· · ·

Mace

My knee jerk reaction is check your firewall rules/port forwarding/authentication groups pointing to any internal authentication servers using something like RADIUS.

Are you using RADIUS for authentication? If so, check your NPS authentication group(s).

· · ·

Mace

Can you manually use the RDG from the outside?
If you sign into RDWeb with chome and download one of the .rdp files, open it up with notepad and make sure it has the correct RDG settings

· · ·

Pure Capsaicin

My recommendation is pretty much close to the other ones. Check that the RD gateway is accessible through the public IP as well. Trace the configuration same as your working environment and make sure it matches your configuration obviously with different IP addresses but same logic.

· · ·

Jalapeno

BBigford wrote:

My knee jerk reaction is check your firewall rules/port forwarding/authentication groups pointing to any internal authentication servers using something like RADIUS.

Are you using RADIUS for authentication? If so, check your NPS authentication group(s).

Sorry don't know how to answer this yet. I never had to configure this part manually even on the existing working RDS. I'll get back to you on this. I only setup the RD CAP and RAP and they seem to be correct.

· · ·

Jalapeno

dbeato wrote:

My recommendation is pretty much close to the other ones. Check that the RD gateway is accessible through the public IP as well. Trace the configuration same as your working environment and make sure it matches your configuration obviously with different IP addresses but same logic.

I can access the FQDN and IP of the Gateway from external and internal (had to add DNS forwarders internally). Right now the setup is single server (public IP > single server). Public IP works and I have tried two different Public IPs just to isolate the forwarding rules as well.

· · ·

Jalapeno

I'm clueless, even with running BPA doesn't show any errors. Tried different remote locations and computers and they all seem to give the same result.

· · ·

Jalapeno

Best Answer

Thanks for the input guys. I figured out my issue. Based from the information I provided above and the BPA result, it kinda suggested that there wasn't an issue with my RDS config. I reviewed my network settings and updated it it to a simpler structure. Works well now.

· · ·

Mace

fernanespiritu wrote:

Thanks for the input guys. I figured out my issue. Based from the information I provided above and the BPA result, it kinda suggested that there wasn't an issue with my RDS config. I reviewed my network settings and updated it it to a simpler structure. Works well now.

Can you provide more input about what you changed? Something with your firewall/etc? You mentioned a "simpler network", please elaborate on that.Definitely helpful to people in the community, as well as anyone online that stumbles upon this thread, to give some clarity about what specifically resolved your issue, if no suggestions in here were helpful.

· · ·

Jalapeno

BBigford wrote:

fernanespiritu wrote:

Thanks for the input guys. I figured out my issue. Based from the information I provided above and the BPA result, it kinda suggested that there wasn't an issue with my RDS config. I reviewed my network settings and updated it it to a simpler structure. Works well now.

Can you provide more input about what you changed? Something with your firewall/etc? You mentioned a "simpler network", please elaborate on that.Definitely helpful to people in the community, as well as anyone online that stumbles upon this thread, to give some clarity about what specifically resolved your issue, if no suggestions in here were helpful.

Well basically my main network is on 10.0.0.xx with 255.255.0.0 and I was trying to build the new RDS environment on 10.0.12.xx. I can ping everything from anywhere internally so I never thought it would be an issue. I would say, I haven't found the real cause of issue or mis-configuration I made. But placing the new RDS environment on the same octet with the prod network made it easier. My network is simple, no vlans or complex routing, but would need to revisit placing the RDS network to a different octet next time.

does that make sense?

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

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.

RDP error: This computer can’t connect to the remote computer

Let’s try to figure out how to fix an RDP connection error This computer can’t connect to the remote computer. It occurs when you try to connect to a remote computer or Remote Desktop Server (RDS) using the built-in Windows RDP client (mstsc.exe).

The problem looks like this: when you try to connect to a remote Windows server/desktop via RDP, the mstsc.exe client freezes for a minute, and a window with the following RDP error appears:

Remote Desktop Connection
This computer can’t connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.

Check the RDP Network Connectivity

First of all, check if the remote computer is accessible from your device over the network, and the default Remote Desktop port (TCP 3389) is responding (and not blocked by firewalls).

Make sure the DNS address of the remote RDP host is correctly resolved from your computer. Use the following commands:

nslookup rdp_server_name1 ping rdp_server_name1

If the DNS name is not resolved properly, check your DNS settings or try connecting to a remote host using an IP address.

You can check the RDP port availability on a remote server from a client workstation using:

The Telnet client:

telnet rdp_server_name1 3389

PowerShell 4.0 and higher:

Test-NetConnection rdp_server_name1 -Port 3389 -InformationLevel Quiet

Note. If this command returned True, then the RDP port responds on the server and it’s not blocked.

PowerShell all versions:

New-Object System.Net.Sockets.TcpClient).Connect(‘rdp_server_name1’, 3389)

If port 3389 is unavailable, you should check if the Remote Connection is enabled on the remote server (right-click on Start button > Settings > System > Remote Desktop > Enable Remote Desktop).

You can remotely enable Remote Desktop on a Windows computer by changing the fDenyTSConnectionsregistry.