sodcalculator

10 Tech How-To

Fix Remote Desktop Can’t Find Computer on Windows 10

Guide 10-54767 · Updated · Step by step

If Remote Desktop on Windows 10 says it can’t find the computer you’re trying to reach, the problem is almost always a network discovery, firewall, or name resolution issue — not a broken Remote Desktop feature. This guide walks you through the most effective fixes, from enabling network discovery to checking the target PC’s IP address and firewall rules.

Why Remote Desktop Can’t Find the Computer

Remote Desktop Connection (RDC) needs to locate the target computer on your local network or over the internet. When it fails, the cause usually falls into one of these categories:

  • Network discovery is off — Windows can’t see other devices on the network, so the computer name won’t resolve.
  • Firewall blocks the connection — Windows Defender Firewall or third-party security software may block port 3389 (the default RDP port).
  • Wrong computer name or IP — A typo, an outdated IP address, or a computer name that isn’t registered in DNS can cause a “can’t find” error.
  • RDP is disabled on the target — The remote PC must have Remote Desktop enabled in its settings.
  • Network profile is Public — Windows treats Public networks more restrictively, blocking file and printer sharing and often RDP.

Understanding which of these applies to your situation is the first step, because the fix differs for each.

Prerequisites: Check Remote Desktop Is Enabled

Before you troubleshoot connectivity, make sure the computer you want to connect to actually has Remote Desktop turned on. On the target PC (the one you’re connecting to):

  1. Open Settings > System > Remote Desktop.
  2. Toggle Enable Remote Desktop to On.
  3. Note the PC name shown in the same window — you’ll need it later.

Also, the user account you’re using must have a password. Windows Remote Desktop won’t allow connections from accounts without passwords by default. If you’re using a Microsoft account, that’s fine; if you’re using a local account, set a password first.

Fix 1: Turn On Network Discovery

Network discovery is the Windows feature that lets your PC find other devices on the same network. If it’s off, Remote Desktop can’t resolve computer names, even if the IP is reachable.

  1. Open Control Panel > Network and Sharing Center.
  2. Click Change advanced sharing settings on the left.
  3. Under Private (or Guest or Public if you’re on a public network), select Turn on network discovery.
  4. Also select Turn on file and printer sharing — this is often required for RDP to work on the same network.
  5. Click Save changes.

If you’re on a domain network, these settings may be controlled by Group Policy, and you might need to contact your network administrator. On a home network, this usually resolves the “can’t find the computer” error immediately.

Fix 2: Use the IP Address Instead of the Computer Name

Computer names rely on DNS or NetBIOS resolution, which can fail if the network is slow, the name is wrong, or the target PC isn’t registered. Using the IP address bypasses name resolution entirely.

  1. On the target PC, open Command Prompt and type ipconfig. Look for the IPv4 Address under your active network adapter (e.g., 192.168.1.10).
  2. On the client PC, open Remote Desktop Connection, type that IP address in the Computer field, and click Connect.

If the IP address works but the computer name doesn’t, the issue is name resolution. You can also try the computer’s full name (e.g., DESKTOP-ABC123) or append a period (DESKTOP-ABC123.) to force a DNS lookup.

Note: If the target PC’s IP changes frequently (due to DHCP), consider setting a static IP address or using the computer name once you’ve fixed name resolution.

Fix 3: Check Windows Defender Firewall Rules

Windows Firewall can block RDP even if it’s enabled. The default rule is usually on, but it can be disabled by third-party security software or a previous configuration.

  1. On the target PC, open Control Panel > Windows Defender Firewall.
  2. Click Allow an app or feature through Windows Defender Firewall.
  3. Scroll down to Remote Desktop. Ensure both Private and Public checkboxes are ticked (if you’re on a private network, at least Private must be checked).
  4. If it’s not listed, click Allow another app, browse to C:\Windows\System32\mstsc.exe, and add it.

If you’re using a third-party firewall, add an inbound rule for TCP port 3389. If you’ve changed the RDP port (not recommended for most users), you’ll need to allow that port instead.

Fix 4: Switch Network Profile to Private

Windows applies stricter firewall rules to Public networks. If your network is misidentified as Public, RDP may be blocked even when the firewall rule is enabled.

  1. Open Settings > Network & Internet > Status.
  2. Click Properties under your active connection.
  3. Under Network profile, select Private.

This change immediately relaxes the firewall for that network, allowing RDP and other discovery features. If you’re on a public Wi-Fi network, be aware that switching to Private makes your PC more visible to others on the same network.

Fix 5: Restart the Remote Desktop Services

Occasionally, the Remote Desktop Services on the target PC may hang. Restarting them can clear temporary glitches.

  1. On the target PC, press Win + R, type services.msc, and press Enter.
  2. Find Remote Desktop Services (TermService), right-click it, and select Restart.
  3. Also restart Remote Desktop Configuration (SessionEnv) and Remote Desktop Services UserMode Port Redirector (UmRdpService) if they exist.

This is a quick fix that often helps when RDP was working before but suddenly stopped.

Frequently Asked Questions

Why does Remote Desktop say “Windows cannot find the computer” even though it’s on the same network?

This usually means network discovery is off or the computer name isn’t resolving. Try using the IP address directly. If that works, enable network discovery and check that the target PC is set to Private network profile.

Can I use Remote Desktop over the internet without a VPN?

Yes, but you’d need to forward port 3389 on your router to the target PC’s IP. This is risky because it exposes RDP to the internet, and brute-force attacks are common. A VPN or a remote desktop gateway is safer.

Does Remote Desktop work on Windows 10 Home?

No, Windows 10 Home cannot act as the host (the computer you connect to). It can only be the client (the computer you connect from). You need Windows 10 Pro or Enterprise for hosting RDP.

Why is the Remote Desktop checkbox greyed out in Settings?

This happens on Windows 10 Home, or if your PC is managed by an organization (via Group Policy). If it’s a home PC, you’ll need to upgrade to Pro. If it’s a work PC, contact your IT admin.

What if I get an error about credentials or authentication?

That’s a separate issue from “can’t find the computer.” It usually means the remote PC requires Network Level Authentication (NLA), and your client doesn’t support it, or the user account doesn’t have permission. Ensure the account is in the Remote Desktop Users group on the target PC.

Can I use a hostname like “MYPC.local” instead of an IP?

Yes, if your network uses mDNS or DNS, you can use MYPC.local (on Macs and some Windows networks). However, on a typical Windows network, the plain computer name works better.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →