remote desktop cant find the computer cover

RDP Error: Remote Desktop Can’t Find the Computer

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 string as “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.

remote desktop cant find the computer

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

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

Try to connect to the RDP server by IP address instead of the DNS name.

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

Nslookup RDPHostName

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


remote desktop cant find the computer powershell

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

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

Notepad C:\Windows\System32\drivers\etc\hosts

remote desktop cant find the computer hosts

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

If the problem is solved, your DNS server is misconfigured, you need to check the entries on it or report the problem to the DNS administrator.

Check the availability of the RDP server with the ping command:


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

Test-NetConnection -port 3389

remote desktop cant find the computer error

If the command returned TcpTestSucceeded: False, this means that the RDP service on the remote computer is disabled, 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.

If the Remote Desktop can’t find the computer error occurs when you try to create a remote RDP connection from the RD Web Access page, try to manually specify the correct RD Gateway address in the RDP connection settings (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.

remote desktop cant find the computer fix

To fix the problem, open the IIS Manager 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.

remote desktop cant find the computer iis

Add Your Comment