sodcalculator

10 Tech How-To

Fix Remote Desktop Error 0x204 on Windows 10

Guide 10-50852 · Updated · Step by step

Remote Desktop error 0x204 on Windows 10 means your client can’t connect to the host, usually because of a network, authentication, or configuration issue. The fix typically involves checking the Remote Desktop service, adjusting firewall rules, or verifying credentials. Below are the exact steps to resolve it, plus background on why it happens.

What Causes Error 0x204?

Error 0x204 (which sometimes appears as “This computer can’t connect to the remote computer”) is a generic connection failure. It’s not a single fault; it can stem from:

  • The Remote Desktop service (TermService) is not running on the host.
  • Network Level Authentication (NLA) is enabled but the client doesn’t support it.
  • Windows Firewall or a third-party firewall is blocking port 3389.
  • The host is asleep, off, or unreachable on the network.
  • Credentials are wrong or the user lacks Remote Desktop permissions.
  • Group Policy or registry settings are restricting connections.

Because the error is generic, you’ll need to methodically check each layer: service, network, port, and permissions.

Step-by-Step Fixes

1. Ensure Remote Desktop Is Enabled on the Host

  1. On the Windows 10 host, go to Settings > System > Remote Desktop.
  2. Toggle Enable Remote Desktop to On.
  3. Confirm the dialog that appears.

If it’s already on, toggle it off and on again to reset the listener.

2. Check the Remote Desktop Service

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll to Remote Desktop Services (TermService).
  3. Its status should be Running. If not, right-click and select Start.
  4. Double-click it, set Startup type to Automatic, and click OK.

Also check Remote Desktop Configuration and Remote Desktop Services UserMode Port Redirector – they should be running as well.

3. Verify Firewall Rules

Windows Firewall usually creates rules automatically when you enable Remote Desktop. To verify:

  1. Open Control Panel > Windows Defender Firewall > Advanced Settings.
  2. Click Inbound Rules and look for “Remote Desktop” rules.
  3. Ensure the rules are Enabled and Allow the connection.
  4. If you use a third-party firewall, add an exception for TCP port 3389.

4. Test Port 3389 Reachability

From the client machine, open Command Prompt and run:

telnet host_ip 3389

If telnet is not installed, use PowerShell:

Test-NetConnection host_ip -Port 3389

If the port is not open, the problem is network-level – check the host’s IP address, ensure it’s on the same network, or configure port forwarding if connecting over the internet.

5. Adjust Network Level Authentication (NLA)

NLA is a security feature that requires authentication before a full session is established. If your client is older or the host’s NLA is misconfigured, you can temporarily disable it:

  1. On the host, go to System Properties (Win + R, type sysdm.cpl).
  2. Click the Remote tab.
  3. Uncheck Allow connections only from computers running Remote Desktop with Network Level Authentication.
  4. Click OK and try connecting again.

If this fixes it, you can re-enable NLA later after updating the client.

6. Check User Permissions

The user account you’re using must be in the Remote Desktop Users group. To add a user:

  1. Open System Properties > Remote tab.
  2. Click Select Users.
  3. Add the user or group, then click OK.

Administrators are included by default, but standard users need explicit permission.

7. Disable Sleep and Wake Timers on the Host

If the host goes to sleep, it won’t accept connections. Go to Settings > System > Power & sleep and set both “Sleep” options to Never (or at least while plugged in).

8. Reset the Remote Desktop Session

Sometimes a stuck session causes 0x204. On the host, open Task Manager, go to the Users tab, and log off any disconnected sessions. Then try again.

Advanced Troubleshooting

If the basic steps fail, try these:

  • Check RDP port in registry: The default port is 3389, but it can be changed. Open regedit on the host and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Look at the PortNumber value. If it’s not 3389, you must specify the port in the client (e.g., host:3390).
  • Update network drivers: Outdated or incompatible drivers can cause RDP failures. Update them via Device Manager.
  • Use the IP address instead of hostname: DNS issues can prevent resolution. Try the IP directly.
  • Check for VPN or proxy interference: If you’re on a VPN, disconnect and try again. Proxies can also block RDP.

Common Mistakes and Misconceptions

One common mistake is assuming error 0x204 means the password is wrong. While bad credentials can cause it, the error is more often due to the host not being reachable or the service being down. Another misconception is that you need to enable Remote Desktop on the client – actually, the client only needs the Remote Desktop Connection app (mstsc.exe), which is built-in.

Also, note that Windows 10 Home edition does not support Remote Desktop as a host. If the host runs Home, you’ll need to use a third-party tool or upgrade to Pro/Enterprise. This is a frequent cause of 0x204 that isn’t obvious.

When to Use Alternative Remote Tools

If you’ve tried everything and still get 0x204, consider using a third-party remote desktop tool like TeamViewer, AnyDesk, or Chrome Remote Desktop. These are often easier to set up and work across different networks without port forwarding. They are not a substitute for fixing the underlying issue, but they can get you connected quickly.

Preventing Future Errors

  • Keep Windows updated on both host and client.
  • Set a static IP on the host to avoid IP changes.
  • Configure your router to forward port 3389 if you need outside access (but be aware of security risks).
  • Use a strong password and consider enabling account lockout policies.

Frequently Asked Questions

Why do I get 0x204 even though Remote Desktop is enabled?

Often because the service isn’t running or the firewall is blocking the port. Check services.msc and the firewall rules first.

Can I fix 0x204 by changing the port?

Changing the port doesn’t fix the underlying issue, but if the port was changed and you’re using the default, you’ll get this error. Make sure the client uses the correct port.

Does Windows 10 Home support Remote Desktop?

No, Windows 10 Home can only be a client, not a host. You need Pro, Enterprise, or Education edition to host RDP sessions.

Is error 0x204 the same as 0x104?

No, 0x104 usually indicates a different issue, often related to the session being disconnected or the client not being able to connect due to a time or security error. 0x204 is more generic.

How do I check if port 3389 is open?

Use the telnet command or PowerShell’s Test-NetConnection as shown above. If it fails, the port is likely blocked.

Will disabling NLA make my connection less secure?

Yes, NLA adds a layer of security by authenticating before the session is fully established. Disabling it should be temporary for troubleshooting. Re-enable it once the issue is resolved.

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 →