Microsoft Remote Desktop cannot connect to some servers after macOS update to Sequoia 15.0

Piers Uso Walter 85 Reputation points
2024-09-16T19:33:03.7266667+00:00

I just updated my Mac to macOS Sequoia 15.0. I'm using Microsoft Remote Desktop 10.9.10.

I can no longer connect to some of our old servers (I was connected to one of those servers right before the update, so the macOS update may be the cause of the problem). The systems I cannot connect to are two Windows Server 2008 R2 Enterprise systems and one Windows Server 2012 system.

The error message I receive in each case is:

We couldn't connect to the remote PC because the PC can't be found. Please provide the fully-qualified name or the IP address of the remote PC and then try again.

Error code: 0x104

I have no problem to connect to other servers (both older systems running Windows 2003, or other Windows Server 2012 systems, or newer systems running Windows Server 2016, or Windows Server 2022).

The error message suggests a DNS problem, but I have verified that the server names resolve correctly, I have flushed my DNS cache, and I have tried to use the IP addresses in the Microsoft Remote Desktop configuration. Still, I get the same error.

Is this a known issue with using Microsoft Remote Desktop on macOS Sequoia?

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,603 questions
0 comments

9 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Piers Uso Walter 85 Reputation points
    2024-09-17T14:19:22.7466667+00:00

    I found the root cause of the problem and how to fix it.

    macOS 15 has a new permission that you have to grant in order to allow apps to access local IPs and domains. A window pops up: "Microsoft Remote Desktop" would like to find devices on your local networks. I didn't know why it would want to do this, so I did not allow this.

    This prevented the app from accessing servers on my local network.

    To fix, I opened System Settings > Privacy & Security > Local Network.
    There I allowed Microsoft Remote Desktop to access the local network (and while I was at it, Windows App Preview and several web browsers as well).

    Now I can once again connect to the servers as I could before the macOS update.

    8 people found this answer helpful.
  2. James McDowell 15 Reputation points
    2024-09-22T02:13:59.0366667+00:00

    Same here.

    Local network access is allowed.

    I can ping the machines.

    I can also use RDP from a Parallels Win 10 VM on the same Mac.

    The 104 error started with Sequoia.

    EDIT: There is now an update to RDP version 11 in the App Store. For whatever reason it did not show up under "updates." I had to select the RDP app in my account in the app store and then it gave me the option to update. It's now called Windows app, quite different.

    At least it seems to be connecting again.

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-09-17T02:01:26.56+00:00

    Can confirm. The same seemingly happens to me. 0x104 right after upgrading a Mac to Sequoia.

    2 people found this answer helpful.
    0 comments
  4. Eric Cabestany 15 Reputation points
    2024-09-17T07:23:56.3433333+00:00

    I have the same problem after updating to MacOS Sequoia 15.0

    Now I'm trying the beta of Windows App.

    I will let you know if works better than the Microsoft Remote Desktop App.

    2 people found this answer helpful.
  5. Keller, Mike 10 Reputation points
    2024-09-18T21:24:55.3033333+00:00

    I changed the Local Network permission and still getting 0x104 errors. Both in RDC and Windows App Preview.

    2 people found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.