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

When an RDP connection fails you can get the error: Remote Desktop can’t find the computer. In this article, we will look at how to troubleshoot and fix this common Remote Desktop Connection issue.

The problem occurs after you specify the remote RDP (RDS) host name in the built-in Remote Desktop Connection (RDC) client (mstsc.exe) and try to connect:

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.

Quick Fixes for Remote Desktop can’t find the computer

1. First, make sure that the hostname is correct. Try to connect using the IP address.
2. Verify DNS resolution:
   nslookup hostname
   If the nslookup command returns a DNS request timed out error, it means your DNS server is unreachable (offline, or blocked by firewall) or the wrong DNS server is specified in your network connection settings.
3. Test RDP port:
   Test-NetConnection hostname -Port 3389
   If you get TcpTestSucceeded: False, it means that the port is blocked or RDP disabled.
4. Check that Remote Desktop is enabled on the target host.

How to Identify Where the Connection Fails

Before troubleshooting, you need to determine at which stage the failure occurs:

• Name resolution failure (DNS/hosts/suffix issue)
• Port unreachable (firewall/network/RDP service)
• Handshake failure (NLA/credentials/TLS issues)

You can test each layer with the following commands:

Resolve-DnsName hostname
Test-NetConnection hostname -Port 3389

Common Reasons for Remote Desktop Can’t Find the Computer

First, check that you have entered the correct remote host name/IP address in the Remote Desktop dialog. This is the most common reason why users fail to connect using RDP.

In other cases, further diagnosis and troubleshooting is required.

The most common causes for the Remote Desktop cannot find the computer error are:

• The client computer cannot resolve the DNS name of the RDP host;
• Network connectivity issues (including firewall restrictions);
• Incorrect Remote Desktop host configuration;
• Misconfigured Remote Desktop Gateway host (if used).

IPv6 Connection Preference Behavior

Windows uses dual-stack resolution and may prefer IPv6 (AAAA) over IPv4 (A records). In some environments this can cause connection delays/failures if IPv6 routing is incomplete.

This behavior is part of modern Happy Eyeballs implementation, where Windows may attempt IPv6 first before falling back to IPv4.

Remote Desktop Can’t Find Computer due to DNS Issues

This error can mean that there are problems with the DNS that are preventing your computer from resolving the host name that you have specified.

Possible causes for the DNS problem are:

• Incorrect DNS settings in network connection properties;
• There are incorrect entries in the hosts file on your computer;
• Your DNS servers are unreachable (the access is blocked by a firewall or the server is down);
• There is no DNS record in the DNS zone for your RDP host or the record points to the wrong IP address.

Steps to troubleshoot DNS issues

First, you need to try the following simple things:

Check and Correct DNS Settings

1. Try to type the Remote Desktop Computer name in the full (FQDN) and the short NetBIOS format. And check the RDP connectivity. For example:
   

   ny-rds01 and ny-rds01.theitbros.com

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

Verify DNS Client Resolution Behavior

In some cases, DNS resolution issues are caused not by DNS server misconfig, but by client-side resolution behavior. You can inspect the DNS cache with the command:

Get-DnsClientCache

Or using ipconfig:

ipconfig /displaydns

In order to check DNS suffix search behavior, use the following command:

Get-DnsClientGlobalSetting | Select-Object SuffixSearchList

Note that this is important when short names (e.g. rdphost01) resolve to unexpected domains in multi-domain environments.

Checking Network Interface DNS Config

You can inspect per-interface DNS config with the following command:

Get-DnsClient | Select-Object InterfaceAlias, ConnectionSpecificSuffix

In order to check whether DNS registration is enabled, run the command:

Get-DnsClient | Select-Object RegisterThisConnectionsAddress

This helps identify cases where DNS records are not properly registered in AD environments.

IPv6 and AAAA Record Resolution Issues

In modern networks, DNS resolution may return IPv6 (AAAA) records before IPv4 (A records). In case IPv6 connectivity is broken/partially configured, you may face Remote Desktop fail even when IPv4 is working.

In some cases, users may experience connection delays rather than outright failures due to IPv6 timeout before IPv4 fallback occurs.

You can verify DNS responses using the following commands:

Resolve-DnsName rdphostname.contoso.com -Type AAAA
Resolve-DnsName rdphostname.contoso.com -Type A

If an AAAA record exists but IPv6 routing is not functional, RDP clients may attempt IPv6 first and fail to connect.

Here are the common causes of IPv6-related RDP issues:

• Broken/partially configured IPv6 on client/server
• DNS returns AAAA record, but no valid IPv6 route exists
• Firewall blocks IPv6 traffic while IPv4 is allowed
• VPN tunnels without IPv6 support

To determine whether DNS resolution/IPv6 preference is causing the issue, try connecting directly to the remote host by its IPv4 address:

mstsc /v:192.168.1.15

This bypasses DNS name resolution and helps determine whether the issue is related to DNS/IPv6 address selection.

Flush DNS Cache

Clear the DNS cache entries on your computer using the command:

ipconfig /flushdns

Check the preferred and alternate DNS server IPs

Check the preferred and alternate DNS server IP addresses specified in the network connection settings. You can list your DNS server settings with PowerShell:

Get-DnsClientServerAddress | Select-Object -ExpandProperty ServerAddresses

Contact your network administrator to check that the DNS server addresses are correct if you have assigned them manually. If the DNS server settings are assigned automatically by the DHCP server, make sure they match your infrastructure. In the last case, you can refresh your IP settings using the commands:

ipconfig /release

ipconfig /renew

Edit the Windows Hosts File

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

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

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

10.1.2.70 rdphostname.contoso.com

Contact Your DNS Administrator

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

Security Considerations

Legacy name resolution mechanisms (such as LLMNR and NetBIOS) can expose environments to spoofing attacks. In secure enterprise networks, these protocols are often disabled with Group Policy. Note that when you disable unnecessary fallback mechanisms, you improve both security and predictability of RDP connections.

In order to reduce name resolution attacks in enterprise environments:

• Disable LLMNR via Group Policy. Navigate to Computer Configuration → Administrative Templates → Network → DNS Client
• Disable NetBIOS over TCP/IP where possible
• Enforce DNS-only resolution in domain environments

This improves both security posture and predictability of RDP connectivity.

Fix Network Problems That Prevent Connection to Remote Desktop Computer

If DNS is working but the issue persists, try check network connectivity.

Test RDP Port 3389 Connectivity

As mentioned earlier, you can test RDP port connectivity using:

Test-NetConnection rdphostname.contoso.com -Port 3389

Enable RDP in Windows Firewall

If the command returned TcpTestSucceeded: False, it means the RDP service on the remote computer is disabled, or the connection is blocked by the firewall:

• Enable the Remote Desktop on the host;
• Check that the Windows Defender firewall on the remote host allows an incoming RDP connection. You can enable this rule the command:
  

  Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

Or you can allow Remote Desktop connection only for a specific IP address:

New-NetFirewallRule -DisplayName "AllowRDPFromSpecificHost" -RemoteAddress 192.168.10.210 -Direction Inbound -Protocol TCP -RemotePort 3389 -Action Allow

Hint. Or you can just reset Firewall settings to the default state.

Disable Third-Party Firewalls or VPNs Temporarily

If you are using a third-party firewall and/or antivirus, try to temporarily disable them on the RDP host and see if they are preventing RD connections.

Check whether a VPN connection is active on your computer, preventing you from connecting to the Remote Desktop host. Try to disabling (or enabling) VPN.

Check the Remote Desktop Host Settings

If nothing helps, check the settings on the remote RDP host you are trying to connect to.

Confirm Correct IP and Hostname

In order to check DNS resolution for the local/remote host, use the modern DNS resolution cmdlet:

Resolve-DnsName $env:computerName

This cmdlet is preferred over legacy .NET methods because it provides more accurate DNS results, including record type information (A, AAAA, CNAME) and better compatibility with modern Windows and hybrid DNS environments.

You can also use nslookup for quick validation when troubleshooting DNS behavior across different systems/when PowerShell cmdlets are unavailable:

nslookup $env:computerName

Check that the Private or Domain network profile is enabled on the computer:

Get-NetConnectionProfile

Enable Remote Desktop Access

Check that RDP access is enabled on the remote host:

Check Required RDP Services

Check if the following services are running on the computer:

• Remote Desktop Services (TermService).
• Remote Desktop Services UserMode Port Redirector(UmRdpService).

Get-Service TermService,UmRdpService

Verify RDP Port Number and Availability

Make sure the RDP service accepts connections on the default TCP port 3389:

Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-TCP\' -name "PortNumber"

If this command returns that RDP is running on a non-standard port (for example, TCP:3333), you can specify the port in the Remote Desktop Connection window in the following format

rdphost.theitbros.com:3331

Now check if the RDP service is listening on port 3389:

cmd /c 'netstat -ano | find "3389"'

How to Fix Remote Desktop Can’t Find the Computer Through the RDWeb

Another error may occur in scenarios where you connect to internal RD hosts on your network through Windows Server with Remote Desktop Gateway (RDGW) or Remote Desktop Web Access (RDWeb) deployed:

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

Manually Specify RD Gateway Settings

First, try to manually specify the correct RD Gateway address in the RDP connection settings:

1. Open mstsc.exe on the client and navigate to the Advanced tab;
2. Click the Settings tab in the Remote Desktop Gateway section;
3. Select the Use these RD gateway server settings option and enter your externally available RDGW hostname;
4. If you are trying to connect RDP host via RDGW within the local network, uncheck the option Bypass RD Gateway server for local addresses;
5. Try to connect to the Remote Desktop.

Correct RDWeb DefaultTSGateway Parameter in IIS

If the connection is successfully established, then you have a misconfigured RDWebAccess server.

To fix the problem,

1. Open the IIS Remote management (inetmgr) console on the RD Web Access server;
2. Go to Sites > Default Web Site > RDWeb > Pages;
3. Open the Application Settings section and enter the external DNS name of your RD Gateway server in the DefaultTSGateway parameter;

   

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

Alternative RD Gateway Config Methods

In modern deployments, RD Gateway settings are often managed through:

• Group Policy (GPO)
• PowerShell (Set-RDSessionCollectionConfiguration)
• Intune/MDM in hybrid environments

Note that IIS config is typically used only for legacy RDWeb deployments.

Test-NetConnection rdphostname.contoso.com -Port 3389

Remote Desktop Services (TermService)Remote Desktop Services UserMode Port Redirector (UmRdpService)

Get-Service TermService, UmRdpService