Remote Desktop Gateway cannot connect

  • Sections
    • Cloud Computing
      • Amazon Web Services
      • Google Cloud
      • Microsoft Azure
    • Containerization
    • Data Center
    • Mobile Technology
    • MS Exchange Server
    • Networking
    • Office 365
    • Security
      • Hacking & Cyberattacks
      • Malware
      • Compliance & Privacy
      • Ransomware
      • Social Engineering
      • Vulnerabilities
    • Virtualization
    • Windows 10
    • Windows 11
    • Windows Server
  • Tech News
  • Tutorials
  • Reviews
  • Newsletters
    • WServerNews
    • FitITproNews
  • Product Directory
  • Webinars
  • About
    • Advertising
    • About Us
    • Contact Us
    • Meet The Team
    • Legal
      • Privacy Policy
      • Terms & Conditions
Type your search query and hit enter:
FooterView Non-AMP Version
Type your search query and hit enter:
  • Homepage
  • Networking
  • Network Troubleshooting
Network Troubleshooting

How to fix remote desktop cant connect to the remote computer

Shutterstock

In todays world, connecting to a remote computer has become commonplace, given that many companies have adopted a work-from-home culture. However, this can bring up many technical issues, including common errors such as remote desktop cant connect to the remote computer.

So, how to fix this error? Well, lets get a bit into the basics first.

Remote desktop is a convenient feature that allows you to virtually connect to other computers running the Windows operating system. With this feature, you can connect to computers located in any part of the world, provided you have the right credentials [username and password] to connect. Also, a good Internet connection is absolutely essential!

If you have the right credentials and the Internet connection and still face this issue, lets address them.

Top reasons for remote desktop cant connect to the remote computer error

Before you read this section, check if your Internet connection is working fine and if youre using the right credentials to log in because these are two of the most common causes of this error. Besides these two causes, there are also other reasons for this error.

Windows update

Many times, the Remote Desktop [RDP] functionality may get corrupted after a Windows update or upgrade as one of the newly installed files can interfere with the working of the RDP. Youll have to manually identify the exact cause and fix it.

Antivirus

Sometimes, antivirus software can block RDP completely or partially, and this leads to the remote desktop cant connect to the remote computer error. The good news about this error is it is easy to identify. Disable your antivirus and see if you can connect now. If you can, youve found the root cause of the problem!

Public network profile

If you have a public network profile or a network group, your computer can block the remote desktop functionality as a protective measure. While this is not an exhaustive list of reasons, these are the most common ones. Now comes the big question how to fix the remote desktop cant connect to the remote computer error.

Fixing theremote desktop cant connect to the remote computererror

There are many ways to fix this error, so youll have to try them one after the other until the problem is fixed. This is true, especially when you dont know the root cause of the error.

Change your firewall settings

This is one of the easiest solutions to the remote desktop cant connect to the remote computer error. Turn off your firewall and see if you can connect to the remote computer, and if you can, youve identified the cause.

Here are the steps to fix this problem.

  • Open the start menu and type Allow an app through Windows firewall. Alternatively, navigate to Control Panel > System and Security > Windows Defender Firewall > Allowed apps.
  • Look for a button called Change Settings on the right-hand top corner of the page and click it.

  • Youll see the list of apps that were allowed or blocked by your firewall. Scroll through the options until you get to Remote Desktop. Check the private and public checkboxes.
  • Close the window and try connecting. If the firewall was the problem, you should be able to connect to the remote computer now.

Check your permissions

You have to be a member of the local Remote Desktop Users group to access a remote machine through RDP. By default, this group is empty and only administrators have the option to add users. So, check with your admin and see if you have the permission to connect via RDP.

Allow remote desktop connections

Remote Desktop Connection [RDC] is the technology that allows your computer to connect to a remote computer over the Internet. You wont be able to connect if this functionality is blocked.

To check if this is blocked, and to allow in case of blocked connections,

  • Go to the Start menu and type Allow Remote Desktop Connections.
  • Look for an option called Change settings to allow remote connections to this computer.
  • Click on the Show settings link right next to it.
  • Check the Allow Remote Assistance Connections to this Computer. Click Apply and OK.

These steps will enable the RDC on your computer.

Reset your credentials

When you connect to a computer frequently, youll save the credentials. However, the same credentials may be used when you connect to a new computer too, and this could cause problems. So, check if youre using the right credentials for the right computer.

To reset the credentials,

  • Open the Remote Desktop Connection. You should find it in the Start menu.
  • Type the IP address of the computer you want to connect to.
  • If the credentials are already saved, youll have the option to edit or delete it.
  • Make the necessary changes.

This will reset or change your credentials.

Verify the status of RDP services

The remote desktop cant connect to the remote computer error can be because RDP services are not enabled either on the local or on the remote computer.

Check if the following services are running on both computers.

  • Remote Desktop Services [TermService].
  • Remote Desktop Services UserMode Port Redirector. Look for UmRdpService.

You cant connect to a remote computer if the UmRdpService was disabled through a central Group Policy. Start these services if you have admin privileges or request the admin to start them for you. Also, you may have to reboot the machine after this service starts.

Add the hosts IP address

Sometimes, Windows wont allow you to connect to those hosts whose IP address is not saved in your hosts file. So, if youre connecting to a computer for the first time:

  • Open the command prompt. Go to Run and type cmd to open it.
  • Type cd C:/Windows/System32/Drivers/etc. This will list down all the hosts saved on your computer. If you dont find the IP of the computer you want to connect to, open this file in notepad and manually add the new IP.

  • To do this, type notepad hosts.
  • Once the file opens, add the IP address at the end of the file, save, and close it.

Now if you check, you should see the IP hostname in your hosts file.

Check the Group Policy

A possible cause of the remote desktop cant connect to the remote computer error can be incorrect Group Policy settings.

To verify and change [if needed]:

  • Open the Run window [Windows key + R] and type gpedit.msc.
  • Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
  • Look for the Allow users to connect remotely by using Remote Desktop Services option.
  • If this setting is disabled, change it to Enabled or Not Configured setting.

Add the RDGClientTransport Key

This is a technical fix, so watch out while doing it.

In this option, youll be tweaking the registry key to force the RDP to use RPC/HTTP connections instead of HTTP/UDP connection.

To do this,

  • Press Windows + R to open run and type Regedit. Press the Enter key.
  • Navigate to HKEY_CURRENT_USER > Software > Microsoft > Terminal Server Client.
  • Navigate to the right-hand pane, right-click, and choose New > DWORD [32-bit value].
  • Name this option as RDGClientTransport.
  • Double-click this newly-created file. Its properties will open, and here, look for an option to set the value data. Enter the value 1. Click OK and close the Windows registry.

Check the RDP listener port

Next, check the RDP listener port. By default, Remote Desktop service will use port 3389 unless you change it. If some other application is using the same port, you wont be able to connect.

To check the remote desktop port thats being used:

  • Type Windows + R and in the dialog box, type Regedit
  • Navigate to HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > Terminal Server > WinStations > RDP-Tcp.
  • Look at the right-hand pane and check the value of PortNumber.
  • If the value is 0x00000000d3d, it means the default port is configured and its value is 3389.
  • Change it to 3388 and try connecting to the remote computer in the new port.

Change the network properties

The cause of the connectivity problem could be the network settings as sometimes, Windows may block public networks as a security measure. So, change the settings to private and see if it works.

To do that:

  • Navigate to Control Panel > Network and Internet.
  • Open the Status.
  • Click the Change Connection Properties option. Look for this on the right-hand pane.
  • When this window opens, choose the Private radio button, and close.

Try connecting now to see if it works.

Overall, the remote desktop cant connect to the remote computer is a common error, but it can have many fixes as the cause may vary greatly. Though it can be a little arduous, your best bet is to run through each solution until you find the one that fixes your problem.

Thanks for reading and share with us the fix that worked for you. If you know any other solutions, please share that too with our readers.

Featured image: Shutterstock

Lavanya Rathnam

Lavanya Rathnam is a professional writer of tech and financial blogs. Creative thinker, out of the boxer, content builder and tenacious researcher who specializes in explaining complex ideas to different audiences.

Next Wait! What? Have chat apps replaced email? »
Previous « Cisco releases 41 new patches, 29 for 'high-severity' issues
Share
Published by
Lavanya Rathnam

    Related Post

  • Securing out-of-lifecycle systems

    Not every business can afford the latest and greatest, even if they want to be

  • Device management for Microsoft 365

    Do you experience problems with Microsoft 365 device licensing limitations? Microsoft has made a few

  • Exchange 2016 Use a Web Application Proxy with Outlook on the web [OWA]

    A Web Application Proxy [WAP] allows reverse proxy functionality for web applications such as Outlook

Recent Posts

  • Microsoft 365

Device management for Microsoft 365

Do you experience problems with Microsoft 365 device licensing limitations? Microsoft has made a few

1 day ago
  • Articles

Firewall as a Service: Everything you need to know

Firewall as a service [FWaaS] refers to an on-demand cloud-based service that serves organizations just

2 days ago
  • Microsoft Azure

Azure Quick Hints: Using nmap tools to identify the certificate being used by your Application Gateway

When troubleshooting, it is essential to understand which certificate is currently in use. Learn how

2 days ago
  • Windows Networking

Securing out-of-lifecycle systems

Not every business can afford the latest and greatest, even if they want to be

3 days ago
  • Windows Networking

Adding a progress bar to your PowerShell scripts

One way that you can gain more insights into your PowerShell scripts is by incorporating

3 days ago
  • Security

SSU takes down Phoenix cybercrime group

SSU investigators are celebrating the successful takedown of the Phoenix hacking group.

4 days ago
FooterView Non-AMP Version

Video liên quan

Chủ Đề