How to Fix Microsoft Remote Desktop Error Code 0x204 (2026 Updated)

Facing RDP Error 0x204 on Mac or Windows 11/10? Learn 5 fast ways to fix it, from firewall settings to clearing Mac cache. Get your remote connection back in minutes!

Ellie

By Ellie / Updated on September 1, 2026

Share this: instagram reddit

Imagine you’re ready to start working remotely, but suddenly blocked by a frustrating message: "We couldn't connect to the remote PC. Error code 0x204." Whether you want to access a Windows 11/10 office computer from your Mac at home or a tablet on the go, this error usually indicates a communication gap between the two devices. But don't worry—you don't need to be a network engineer to fix it.

Error Code 0204

30-Second Quick Check:

Before diving into the technical solutions, ensure these basics are covered:

  • Power: Is the remote PC turned on and not in Sleep/Hibernate mode?
  • Update: Is your Microsoft Remote Desktop app running the latest version from the App Store or Microsoft Store?
  • Network: Are both devices connected to the internet?

If these are fine and you still see Error 0x204, let's look at the 5 proven solutions to get you back online.

What causes RDP Error Code 0x204?

In technical terms, Error 0x204 is a "Handshake Timeout." Your device is knocking on the door, but the remote PC isn't answering. This usually happens for one of four reasons:

  • Connectivity: The remote PC is turned off, asleep, or disconnected from the network.
  • Permissions: Remote Desktop is disabled in Windows settings, or the user lacks authorization.
  • Security Blocks: Windows Firewall or a 3rd-party antivirus is blocking Port 3389 (the RDP gateway).
  • Name Resolution: Your Mac/Client cannot "find" the PC because of a DNS mismatch (common when using PC names instead of IP addresses).
  • Corrupted Cache: (Mac Only) The app's temporary data has become glitched, preventing a clean connection.

Quick fix: Repair RDP Error 0x204 directly

Use this order before changing advanced settings. It fixes the most common host, firewall, account, and name-resolution problems without exposing your PC directly to the internet.

  1. Check the host edition: On the remote PC, open Settings > System > About. Windows 11/10 Pro, Enterprise, and Education can accept incoming RDP connections; Home can only act as a client.
  2. Enable Remote Desktop: Go to Settings > System > Remote Desktop, turn it on, and keep Network Level Authentication enabled.
  3. Allow the user: Under Remote Desktop users, add the account you will use. The account must have a password.
  4. Repair the firewall rules: Open Windows Terminal or PowerShell as administrator and run Enable-NetFirewallRule -DisplayGroup "Remote Desktop".
  5. Restart the RDP service: Press Win + R, enter services.msc, open Remote Desktop Services, and select Restart.
  6. Test by local IPv4 address: Run ipconfig on the host, then enter its IPv4 address in Windows App or Remote Desktop Connection. If the IP works but the PC name does not, the issue is DNS/name resolution.
  7. For access from another network: Connect through a VPN, RD Gateway, or a secure remote access solution. Avoid exposing TCP 3389 directly to the public internet.

RDP 0x204 differences by system version

System or edition Can host an RDP session? What to check for 0x204
Windows 11/10 Home No It can connect to another PC, but cannot accept built-in RDP connections. Upgrade the host edition or use an alternative remote desktop solution.
Windows 11/10 Pro, Enterprise, Education Yes Use Settings > System > Remote Desktop; confirm the account, firewall rules, network profile, and NLA compatibility.
Windows Server 2016-2025 Yes Confirm Remote Desktop is enabled, the user has sign-in rights, firewall rules are active, and RD Gateway/RDS policies are correct.
macOS 12 or later Client only Microsoft Remote Desktop has been replaced by Windows App. Update the app first; only clear legacy cache if the problem started before or during migration.
iOS/iPadOS 16 or later Client only Use the current Windows App, verify local-network permission, and recreate the saved PC entry if its hostname or gateway changed.

5 ways to fix Microsoft RDP Error Code 0x204

To fix this error, we will first configure the Target Windows PC (the one you want to access) and then adjust the Client Device (the Mac or iPad you are using).

Solution 1. Enable Remote Desktop on Windows

Step 1. On Windows 11 or Windows 10, open Settings > System > Remote Desktop and turn on Remote Desktop. Alternatively, press Win + R, type “sysdm.cpl”, and press Enter to open the legacy System Properties dialog.

Run Command Sysdm.cpl

Step 2. Go to the Remote tab, and check Allow remote connection to this computer.

Remote Desktop Tab

Solution 2. Allow Remote Desktop through Windows Firewall on Windows

Step 1. On Windows 10, open the Run box, type in “control panel” to open Control Panel.

Run Control Panel

Step 2. Navigate here: Control Panel > System and Security > Windows Defender Firewall.

Defender Firewall

Step 3. Click Allow an App or Feature Through Windows Defender Firewall.

Allow APP or Feature

Step 4. Select Remote Desktop and Remote Desktop (WebSocket), then hit OK.

Tick Remote Desktop

⚠️Notes:

If you use 3rd-party antivirus (like McAfee or Norton), you must manually allow Port 3389 in their specific firewall settings.

Solution 3. Connect via IP address (Bypass DNS)

DNS mismatches are a top cause of 0x204. Connecting via IP is much more stable.

Step 1. On Windows 10, open the Run box, type in “cmd” and press Enter to open Command Prompt.

Run Box CMD

Step 2. Type in “ipconfig” and press Enter, the IPv4 address is the one you need.

Find the Computer Name in the Console

Step 3. On the Mac, enter the IP Address of Windows 10 instead of the PC Name in the box to achieve a remote connection.

Enter IP Address

Solution 4. Clear Remote Desktop Temp Files (Mac only)

On current macOS versions, Microsoft Remote Desktop has been replaced by Windows App. Update Windows App and recreate the saved PC entry first. If you migrated from the legacy client and 0x204 persists, its cached container may still be damaged.

Step 1. Click the Finder icon, type “group containers” in the search bar, and press Enter. Be sure the search area is “This Mac”.

Group Container

Step 2. Open the Group Containers folder (Path: `~/Library/Group Containers`).

Open Group Container

Step 3. Right-click the folder named UBF8T346G9.com.microsoft.rdc and then choose Move to Trash.

Move To Trash

Solution 5. Test port 3389 and secure off-network access

RDP listens on TCP port 3389 by default. First test the connection on the same private network. For access from another network, prefer a VPN or RD Gateway; directly forwarding 3389 to the public internet is not recommended.

Step 1. On a Windows client, open PowerShell and run Test-NetConnection HOST-IP -Port 3389. On macOS, open Terminal and run nc -vz HOST-IP 3389. Replace HOST-IP with the remote PC's private IPv4 address.

Port Scan

Step 2. If the test fails on the same private network, search for Windows Firewall on the Windows 11/10 host and choose “Windows Defender Firewall with Advanced Security”.

Windows Defender Firewall Advanced Security

Step 3. Click on Inbound Rules and then New Rule.

Inbound Rules Firewall

Step 4. Select the Port and click Next.

Port

Step 5. Click Specific local ports and enter port number 3389.

Specific Local Ports 3389

Step 6. Click Allow the connection.

Allow the Connection

Step 7. Select the network types you want to use, name the rule, and hit Finish.

Confirm Check

⚠️Notes:

Error 0x204 can also appear on iPhone or iPad. Microsoft Remote Desktop has been replaced by Windows App on iOS/iPadOS. Update Windows App, allow Local Network access in iOS/iPadOS settings, and recreate the saved PC entry. For remote work across different networks, consider a managed remote work solution that does not require public port forwarding.

Still failing? Skip the RDP headache with AnyViewer

If you’ve tried the steps above and are still seeing Error Code 0x204, or if you find port forwarding and firewall rules too risky and complicated, it’s time for a more modern solution.

AnyViewer is a free, professional-grade remote desktop alternative designed to bypass the technical barriers that plague Microsoft RDP. It supports both unattended remote access and attended remote support without asking users to expose RDP ports.

Download Freeware Win PCs & Servers
Secure Download

Why AnyViewer is the best alternative for Mac & Windows

Unlike Microsoft Remote Desktop, which requires a perfect network "alignment," AnyViewer is built for ease of use:

  • No Port Forwarding Required: AnyViewer uses advanced technology to automatically penetrate firewalls and routers. You don't need to touch your router settings or open Port 3389.
  • Work on Windows Home Edition: While Microsoft RDP is restricted to Pro and Enterprise editions, AnyViewer works flawlessly on Windows 11/10 Home, saving you the cost of an OS upgrade.
  • One-Click Connection: Once logged in, you can access your remote PC with a single click—no IP addresses or PC names required.
  • Security You Can Trust: It uses 256-bit ECC (Elliptic Curve Cryptography) encryption, providing a secure "tunnel" to protect your data from interception.
  • Feature-Rich Free Version: Unlike RDP, AnyViewer supports high-quality image sync, file transfer, and even remote gaming for free.

How to access your Windows PC from Mac in 3 simple steps

Step 1. Download and install AnyViewer for Windows on your target PC and AnyViewer for Mac on your client device.

Step 2. Create a free account and sign in on both devices.

Free Editions

Step 3. Go to the "Device" tab on your Mac, select your Windows PC, and click "One-click control." That's it! No 0x204 errors, no complex configurations.

control-windows-from-mac

Conclusion

Microsoft Remote Desktop Error Code 0x204 is a sign that something in your network chain is broken—be it a firewall, a port, or a DNS mismatch. While the 5 solutions above can fix the issue, they require manual upkeep every time your network changes.

For a more stable, "set-and-forget" experience, we highly recommend switching to AnyViewer. It’s the fastest way to get your work done without letting error codes get in your way.

FAQs

Why does Error 0x204 keep appearing even when Remote Desktop is enabled?
 
Enabling Remote Desktop is only one requirement. Confirm the account is allowed, the firewall rules are enabled, the host is awake, and the client can reach TCP 3389. Update Windows App and verify that the client and host clocks are correct before changing Network Level Authentication.
Can I fix Error 0x204 on Windows Home Edition?
 
Unfortunately, the "Host" feature of Microsoft Remote Desktop is not available on Windows 11/10 Home Edition. You can use a Home PC to control others, but you cannot control a Home PC. To fix this without paying for a Pro upgrade, we recommend using a third-party tool like AnyViewer, which supports all Windows editions.
Is Port 3389 safe to open for RDP?
 
Opening Port 3389 (Port Forwarding) makes your PC visible to the entire internet, which can be a security risk for brute-force attacks. If you must use RDP, ensure you use a strong, unique password and a VPN. Alternatively, AnyViewer provides a more secure path as it doesn't require open ports to establish a connection.
Does the "PC Name" work for remote connections over different Wi-Fi networks?
 
Rarely. PC Names (like "Office-Laptop") are resolved using local network protocols (NetBIOS/LLMNR). Once you leave your local Wi-Fi, your Mac won't be able to "find" that name. For remote access over the internet, you must use the Public IP address of your router or a dedicated remote access software.
Will reinstalling the Microsoft Remote Desktop app on Mac fix 0x204?
 
Microsoft Remote Desktop for macOS has been replaced by Windows App. Update Windows App and recreate the saved PC first. If you migrated from the legacy client, removing its UBF8T346G9.com.microsoft.rdc cache can help, but back up any saved settings before deleting it.
Why does RDP work on the same Wi-Fi but show 0x204 from another network?
 
The local test proves that the host and Windows firewall are working. Off-network access still needs a secure route into the private network, such as a VPN or RD Gateway. Do not expose TCP 3389 directly unless you understand and mitigate the security risks.
How can I tell whether error 0x204 is a DNS problem?
 
Connect using the host's private IPv4 address while both devices are on the same network. If the IP address works but the PC name fails, check DNS, VPN name resolution, or the saved PC entry rather than changing the RDP service.