Fix: Remote Desktop can’t Connect to the Remote Computer for one of these Reasons

The “Remote Desktop can’t connect to the remote computer for one of these reasons” error typically appears when a Remote Desktop connection is unexpectedly interrupted, preventing users from accessing a remote system. This error indicates a configuration or network issue blocking the connection.

Fix: Remote Desktop Can’t Connect to the Remote Computer for one of these Reasons

The most common causes are Remote Desktop being disabled on the target machine or incorrect firewall settings. Other factors, like network misconfigurations, DNS problems, or insufficient permissions, can also lead to this error.

In this article, we will discuss different ways to solve this error.

1. Change/Tweak your Firewall Settings

To address Remote Desktop connection issues, adjust firewall settings to allow RDP through security layers. If the firewall blocks port 3389 (RDP’s default port), connections won’t work. Make sure to allow traffic on this port or list Remote Desktop as an allowed app to prevent the firewall from blocking access. This step tackles a common cause of connection failures.

  1. Type ‘Allow Remote Desktop Connections‘ in the Start Menu.
  2. Select the first result.
  3. In the window that appears, scroll to the Remote Desktop section and click ‘Show settings‘ next to ‘Change settings to allow remote connections to this computer‘.
    Allowing RDP Connections
  4. Ensure ‘Allow Remote Assistance Connections to this Computer‘ is checked. Click Apply, then OK to close the window.

2. Allow Remote Desktop Connections if not allowed

This issue usually happens when Remote Desktop connections aren’t allowed on the remote system. Enabling this setting lets the machine accept RDP requests, which is crucial for a connection. Without it, connection attempts are blocked, causing errors. Allowing Remote Desktop ensures the system can accept remote access, solving a common connectivity issue.

  1. Type ‘Allow Remote Desktop Connections‘ in the Start Menu.
  2. Select the first result.
  3. In the window that appears, scroll to the Remote Desktop section and click ‘Show settings‘ next to ‘Change settings to allow remote connections to this computer‘.
    Allowing RDP Connections
  4. Ensure ‘Allow Remote Assistance Connections to this Computer‘ is checked. Click Apply, then OK to close the window.

3. Reset your Remote Desktop Credentials

When you save credentials for a specific remote computer and then try to connect to a different one, an error can occur because the saved credentials don’t match. This is because the new computer requires different login details than the ones you saved.

  1. Search for Remote Desktop Connection in the Start Menu.
  2. Click on Remote Desktop from the results.
  3. Enter the computer’s IP address. If credentials are saved, you’ll see an option to edit or delete them.
  4. Click delete to remove the saved credentials.
    Deleting Saved Credentials

4. Add the Remote Computer’s IP address to your hosts file

Updating the hosts file with the remote computer’s IP address can fix connection issues by making sure your computer links the remote’s name to its IP. When DNS doesn’t work, adding the IP gives a direct path. This ensures Remote Desktop connects to the right machine, especially when network settings fail.

  1. Press Windows Key + X and select Command Prompt (Admin) from the list to open an elevated command prompt.
  2. Once in cmd, type this command:
    cd C:/Windows/System32/Drivers/etc
  3. After that, type this command:
    notepad hosts
    Editing the hosts File
  4. Once the hosts file opens in notepad, add the IP address of the remote computer to the end of the file. Finally, click the close button and when asked to save changes, click Save.

5. Add the RDGClientTransport Key

Changing how Remote Desktop manages connections can often fix persistent issues. Adding the RDGClientTransport key tells the system to use RPC over HTTP, which can bypass network problems or security blocks affecting the default method. This is especially helpful when corporate firewalls, proxy settings, or other security measures block the connection.

  1. Press Windows + R to open Run.
  2. Type regedit and press Enter.
  3. Paste the following path in the registry editor’s address bar:
    HKEY_CURRENT_USER/Software/Microsoft/Terminal Server Client
  4. Right-click in the right pane, select New → DWORD (32-bit) Value, and name it RDGClientTransport.
    Adding RDGClientTransport Key
  5. Double-click the key to open its properties, set the value data to 1, and click OK. Then, close the Windows Registry.

6. Change Network Properties

Sometimes the problem is how your network is set up. Change your network from “Public” to “Private” so Windows trusts other devices. Public networks block services like Remote Desktop, but setting it to private allows connections. This update adjusts firewall settings to permit Remote Desktop.

  1. Click the network icon in the system tray.
  2. Select your connected network to open its settings.
    Accessing Network Settings
  3. Under the network name, click Properties.
    Selecting Network Properties
  4. Select Private as your network profile.
    Choosing “Private”
  5. Check if the issue is resolved.
ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Comments

12
    JB
    Jörgen Blixt Oct 16, 2019

    Here is my one penny solution…
    During Windows update my network connection on each PC was converted from Private to Public. There RDP protocol simply wouldn’t connect. But when I changed the network back to Private all file sharing and printer sharing and remote desktop started working again. Took me days to figure that one out :-).

    Reply
      SW
      Shane Warren Author Oct 17, 2019

      Thank you for sharing your solution, it will be added to the article shortly.

    MO
    Mojo Nov 23, 2019

    none of the above worked for me

      SW
      Shane Warren Author Nov 24, 2019

      Is the network selected as private?

        MO
        Mojo Nov 25, 2019

        Yes

    AA
    Aarya Apr 16, 2020

    None of the above solutions were not worked to me, I have tried all the options give above, but no luck

      SW
      Shane Warren Author Apr 17, 2020

      Press Windows + I to open settings and then go into the system. In here, go to display and then on Advanced Scaling Settings. Try to disable Custom scaling completely and check if that works.

      Reply
    SD
    sdsds Nov 10, 2020

    Sometime, because your VPN, try to turn off it and try again

    Reply
    IC
    Iconoclast24601 Nov 11, 2020

    So Chrome Remote Desktop (free) works straight away with minimal setup, whereas Windows Remote Desktop (expensive) requires us to jump through many convoluted hoops and even then, still may not work for unknown reasons. It feels like Chrome versus Internet Explorer all over again… typical Microsoft?

    SC
    SHIVAM CHANDLA Aug 21, 2021

    none of the above worked for me

      MZ
      Muhammad Zubyan Author Aug 28, 2021

      Try and follow these steps and check to see if the issue is resolved:-

      1. Search for Command Prompt and click “Run as administrator”.
      2. Once the Command Prompt window opens type the following command:-

      netcfg -d

      3. Wait for the command to run then restart your computer.

      Check to see if the issue is resolved.

      Reply
    AL
    Alexander Oct 4, 2021

    It kinda surprised me that it is the network being private blocks me from remote connection. Thanks for the 6th solution.