This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 54%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
Hi
I can't anymore use the remote desktop app on mac. On macOS 14.2.1 I always get the following error:
Unable to connect
We couldn’t connect to the remote PC. Make sure the PC is turned on and connected to the network and that remote access is enabled.
Error code: 0x204
But I can connect to the windows PC when using the remote desktop app on my iPhone or iPad. Only on Mac it doesn't work, so the PC side works. And it worked on my Mac before.
Greetings
Patrick
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 11%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHZ%3C/text%3E%3C/svg%3E)
The error code 0x204 indicates that the macOS Remote Desktop app cannot connect to the remote PC. To troubleshoot, ensure both devices are on the same network with stable internet connections, verify remote access settings on the Windows PC, check firewall and antivirus settings, update macOS and the Remote Desktop app, reset Remote Desktop preferences, and if necessary, reinstall the app. If the issue persists, double-check the IP address or hostname of the remote PC and consider trying alternative Remote Desktop clients for macOS.
Hi
thanks for your comment!
Reinstalling of the app didn't work.
But I found I can access the PC via its IP instead of the hostname.
So on mac I now can access the PC via IP addess.
iPhone and iPad can still acces per Remote Desktop app via the hostname.
Strange, but it works.
Greetings.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 24%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Same problem here. Entered the IP where previously the hostname was set - solved it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 22%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
I am seeing this issue with a new installation of Remote Desktop 10.9.10 on macOS 14.6.1. The problem is not with the DNS server - it is with the Remote Desktop client querying the wrong DNS servers.
Using Wireshark, I can see that DNS queries are not being sent to the two DNS servers shown in macOS as learned via DHCP - instead, Remote Desktop (and only this product) is sending DNS queries to two DNS servers that we decommissioned last year, and which have not been learned via DHCP since then.
Why is the Remote Desktop client not using the macOS DNS server settings?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 15%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
I'm seeing the same behavior today. macOS Sequoia 15.0 and Microsoft Remote Desktop 10.9.10(2327)
This worked fine all day yesterday (Tuesday). I had updated to macOS 15 on Monday so that shouldn't be the problem.
Eureka! I found a fix, at least for my scenario - hopefully this helps someone else...
The short version: look in /etc/resolvers/ for the remnants of config files from the Leopard era that have old/invalid DNS servers configured. Delete the one with bad data - this is an old method of defining resolvers that isn't used anymore but apparently has come to play here.
Something about the way MS Remote Desktop does DNS queries, it results in a more specific match against a different 'resolver' block here, which takes precedence over the current, learned DNS servers from DHCP. So, the DNS name resolves fine in terminal, other programs work, and you can use Remote Desktop with the target's IP address - but its DNS queries are falling into a black hole and it won't connect via name.
Running this command will give you a picture of all the DNS servers your system will try to use for different scenarios:
scutil --dns
Thanks for the comment and glad it solved your problem.
Turns out my problem was related to the upgrade to Sequoia. What was throwing me off is that it worked the day after the upgrade.
System Settings --> Privacy & Security --> Local Network
I had to turn that on for Remote Desktop and then mine was working properly. That doesn't explain how it worked the previous day though. I do remember seeing the popup about that at some point and I clicked no. Wish I could remember when I told it no as that would explain my issue.
Hello,
If you can access via ip address, the issue is on your dns server, you dns server cannot recognize your Hostname (if your pc has no dns record in Operator network)
You can manually find the host file, then add your hostname and ip to the end of this file.
a. Type in ip
b. A "blank"
c. Type in hostname
If the Answer is helpful, please click "Accept Answer" and upvote it.