Microsoft Remote Desktop Unable To Connect To Remote Pc

Posted on by admin



  1. Microsoft Remote Desktop Unable To Connect To Remote Pc
  2. Microsoft Remote Desktop Unable To Connect To Remote Pc Download

In this article, we will take a look at the basic techniques for diagnosing a problem with Remote Desktop Connection. For example, when you try to establish a connection to the remote server using the standard client mstsc.exe (Remote Desktop Connection), the message “Initiating Remote Connection …” appears, and then the user receives an error: Remote Desktop can’t find the computer %RDPHostName%. This might mean that %RDPHostName% does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.

Make sure that all Windows updates and service packs have been successfully applied to the server. Log into the server as an Administrator. Open the Remote Desktop Licensing Manager: Go to 'Start' 'Administrative Tools' 'Remote Desktop Services' 'Remote Desktop Licensing Manager'. Hi, Please try to run our PC Setup tool on your PC: to ensure your PC is configured properly to work remotely. If you have another device you can use it to see if you can establish a successful a connection to rule out there is an issue with the app.

How to Fix the Error: Remote Desktop Can’t Find the Computer on Windows?

In most cases, this error means that there are problems with your DNS servers (or DNS records on them), because of which your computer can’t resolve the specified host name.

First of all, make sure that you have specified the correct hostname of the remote RDP host in the Computer field.

Try to connect to the RDP server by IP address instead of the DNS name. If the RDP connection by an IP address is established correctly, this means that the issue is related to DNS.

Possible reasons for the DNS problem are:

  1. Incorrect IP addresses of DNS servers are specified in the settings of your Windows computer;
  2. On your computer, the host file contains incorrect entries for the RDP host names;
  3. Your DNS servers are not available (the access is blocked by a firewall or server is down);
  4. There is no DNS record in the DNS zone for your RDP host or the record points to the wrong IP address.

Try to find out if your DNS server knows the FQDN of the RDP server you are connecting to (%RDPHostName%). Open an elevated Command prompt and run the command:

Make sure that the command returned the IP address of the remote server, for example:

If the command returned an incorrect entry, try to flush DNS cache (ipconfig/flushdns) on the client and try to resolve RDP hostname again.

READ ALSOHow to Fix Language Bar Problem in Windows Server 2016/2012R2/2008R2?

If the nslookup command returns a “DNS request timed out” error, it means that your DNS server is not available (offline, blocked by a firewall) or the wrong DNS server is specified in your network card settings.

Check the preferred and alternate DNS server IP addresses specified in the network connection settings. You can get local DNS server addresses using the following PowerShell command:

If you have assigned the DNS server addresses manually, check with your network administrator that they are correct. If the DNS server settings are assigned automatically by the DHCP server (Windows Server DHCP or Cisco DHCP server), make sure they match your infrastructure. In the last case, you can refresh your IP settings using the ipconfig command:

If the above advice didn’t help, please make sure that the outbound DNS client traffic is allowed in your firewall. If you are using Windows Defender Firewall with Advanced Security, you can add the firewall rules to accept any inbound traffic on port 53 (both UDP and TCP).

Unable

Hint. Or just reset your Windows Firewall settings to default state.

If the Nslookup command still returns an invalid entry, open the local hosts file with the command:

If there are no entries for your RDP server in the file, you can try to add them manually (this way you can bypass the wrong records your DNS server returns). You need to add a string to a hosts file in the following format:

You can use the following batch script to add new entries to your host file. Just replace the values in the script with the IP addresses and FQDN names of your RDP hosts or RDS servers:

If the problem is resolved, it means that your DNS server is misconfigured. You need to check the entries on it or report the problem to the DNS administrator.

READ ALSOFix: Windows 10 Keyboard not Working

If you a member of the DNS adminsdomain security group, you can check the DNS records using the DNS manager mmc snap-in (dnsmgmt.msc).

Connect to a DNS server (usually it is a closes domain controller), expand the DNS zone, and find the A or CNAME record of your RDP host. Make sure it has the correct IP address.

If there are lot of records in the DNS zone, you can use the View > Filter menu to quickly find the DNS records you need.

Microsoft Remote Desktop Unable To Connect To Remote Pc

Next, check the availability of the RDP server with the ping command:

Then you should check that the RDP port 3389 (TCP) is accessible on the server from the client (this is the port for RDP connection by default). The easiest way to check the port availability is using the PowerShell command:

If the command returned TcpTestSucceeded: False, this means that the RDP service on the remote computer is disabled (you can try to enable Remote Desktop remotely), or the connection is blocked by the firewall on the client, server, or network routers.

A few tips to check if you can’t connect to an RDP server:

  1. Try to update the version of your RPD client (especially if you are using Windows XP, Windows 7 or 8.1);
  2. Try to use an alternative RDP client (RDCMan);
  3. Temporarily disable the antivirus and firewall on the client and server side and check the RDP connection;
  4. If you are connecting from a Windows XP client and the NLA (Network Level Authentication) is enabled on the server, then on the client side XP you can enable NLA support only through the registry;
  5. Remote connection is not possible if the user account under which you are connecting does not have a password.
READ ALSOHow to Fix an Error ERR_NAME_NOT_RESOLVED on Android Devices?

Microsoft Remote Desktop Unable To Connect To Remote Pc Download

Remote Desktop Can’t find the Computer through the RDWeb Gateway

In some cases you can get an error the “Remote Desktop can’t find the computer” when you trying to create a remote RDP connection or to run a RemoteApp hosted on the Remote Desktop Gateway. You can see the following error after successful authentication on RDWEB Gateway.

RemoteApp Disconnected – Remote desktop can’t find the computer FQDN.

First, try to specify the correct RD Gateway address in the RDP connection settings manually (the connection through RDWebAccess is performed not via standard port 3389, but through HTTPS – 443 port) and try to connect. If the connection is successfully established, then you have a misconfigured RDWebAccess server.

To fix the problem, open the IIS Management console on the RD Web Access server. Go to Sites > Default Web Site > RDWeb > Pages. Open the Application Settings section and in the DefaultTSGateway parameter specify the external DNS name of your RD Gateway server.

Now refresh the RDWeb page and try to establish an RDP connection again.

AuthorRecent PostsCyril KardashevskyI enjoy technology and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion.Latest posts by Cyril Kardashevsky (see all)
-->

This article describes common issues with the Remote Desktop client and how to fix them.

Remote Desktop client for Windows 7 or Windows 10 stops responding or cannot be opened

Starting with version 1.2.790, you can reset the user data from the About page or using a command.

Use the following command to remove your user data, restore default settings and unsubscribe from all Workspaces.

If you're using an earlier version of the Remote Desktop client, we recommend you uninstall and reinstall the client.

Web client won't open

First, test your internet connection by opening another website in your browser; for example, www.bing.com.

Use nslookup to confirm DNS can resolve the FQDN:

Try connecting with another client, like Remote Desktop client for Windows 7 or Windows 10, and check to see if you can open the web client.

Can't open other websites while connected to the web client

If you can't open other websites while you're connected to the web client, there might be network connection problems or a network outage. We recommend you contact network support.

Nslookup can't resolve the name

If nslookup can't resolve the name, then there might be network connection problems or a network outage. We recommend you contact network support.

Your client can't connect but other clients on your network can connect

If your browser starts acting up or stops working while you're using the web client, follow these instructions to troubleshoot it:

  1. Restart the browser.
  2. Clear browser cookies. See How to delete cookie files in Internet Explorer.
  3. Clear browser cache. See clear browser cache for your browser.
  4. Open browser in Private mode.

Client doesn't show my resources

First, check the Azure Active Directory account you're using. If you've already signed in with a different Azure Active Directory account than the one you want to use for Windows Virtual Desktop, you should either sign out or use a private browser window.

If you're using Windows Virtual Desktop (classic), use the web client link in this article to connect to your resources.

If that doesn't work, make sure your app group is associated with a workspace.

Web client stops responding or disconnects

Try connecting using another browser or client.

Other browsers and clients also malfunction or fail to open

If issues continue even after you've switched browsers, the problem may not be with your browser, but with your network. We recommend you contact network support.

Web client keeps prompting for credentials

If the Web client keeps prompting for credentials, follow these instructions:

  1. Confirm the web client URL is correct.
  2. Confirm that the credentials you're using are for the Windows Virtual Desktop environment tied to the URL.
  3. Clear browser cookies. For more information, see How to delete cookie files in Internet Explorer.
  4. Clear browser cache. For more information, see Clear browser cache for your browser.
  5. Open your browser in Private mode.

Windows client blocks Windows Virtual Desktop (classic) feed

If the Windows client feed won't show Windows Virtual Desktop (classic) apps, follow these instructions:

  1. Check if the Conditional Access policy includes the app IDs associated with Windows Virtual Desktop (classic).
  2. Check if the Conditional Access policy blocks all access except Windows Virtual Desktop (classic) app IDs. If so, you'll need to add the app ID 9cdead84-a844-4324-93f2-b2e6bb768d07 to the policy to allow the client to discover the feeds.

If you can't find the app ID 9cdead84-a844-4324-93f2-b2e6bb768d07 in the list, you'll need to register the Windows Virtual Desktop resource provider. To register the resource provider:

  1. Sign in to the Azure portal.
  2. Go to Subscription, then select your subscription.
  3. In the menu on the left side of the page, select Resource provider.
  4. Find and select Microsoft.DesktopVirtualization, then select Re-register.

Next steps

  • For an overview on troubleshooting Windows Virtual Desktop and the escalation tracks, see Troubleshooting overview, feedback, and support.
  • To troubleshoot issues while creating a Windows Virtual Desktop environment and host pool in a Windows Virtual Desktop environment, see Environment and host pool creation.
  • To troubleshoot issues while configuring a virtual machine (VM) in Windows Virtual Desktop, see Session host virtual machine configuration.
  • To troubleshoot issues related to the Windows Virtual Desktop agent or session connectivity, see Troubleshoot common Windows Virtual Desktop Agent issues.
  • To troubleshoot issues when using PowerShell with Windows Virtual Desktop, see Windows Virtual Desktop PowerShell.
  • To go through a troubleshoot tutorial, see Tutorial: Troubleshoot Resource Manager template deployments.