How to fix error 0x1807 Remote Desktop on Mac?

Question

I used to be able to connect to my remote desktop with my universities VPN but now I get a security problem (error 0x1807) which my uni administrator hasn't heard of. He's able to connect from other computers to my account but not from my mac... I've tried uninstalling it and re-installing it, but maybe I'm not doing this correctly... 

Answer 1

I tried turning off IPv6 and didn't work.

I am at the last versions of the OSs. Last build of Windows 11, last build of macOS Sonoma, last build of Microsoft Remote Desktop. (Understand it that I already checked if there is any update in Windows Update, System Preferences and Mac App Store).

I also tried with domain name in min or even all CAPS, didn't work.

It notable that is a problem in Windows, not macOS. When Windows is starting for a few second is possible to see another message but no success. Settings on Firewall also is allowed to RDP (and port 3389).

For a few second I was able to connect but seconds after login (screenshot below) the connection was lost.

It seems some service started and interrupted my access.

Answer 2

FUP: I was thinking that could be some blocking from the firewall (BitDefender) of my company on the Windows 11 PC but it's not. I tested blocking any connection from Bitdefender on AdGuard DNS and the problem still happens. Starting Windows seems good, after few seconds the connection is interrupted like screenshots above.

Answer 3

I had the same issue. Tried disabling IPv6 in the Control Panel on the server and rebooted. After the reboot I successfully logged in to the server.

Answer 4

I just had the same issue; error 0x1807. I had connected to it without issue yesterday, so was surprised to see it today. When I rebooted the server I am connecting to, I found it had a number of pending MS updates. Once rebooted, I was able to connect. Is there a possible correlation between pending MS updates and being able to connect remotely?

Answer 5

We're having the same issue, and it... is ridiculous, introduces a completely idiotic problem into what was an otherwise perfectly functional workflow. We have to have the user sign in before it lets them work, which isn't a problem from our Windows RDP clients.

Great work, Microsoft. Also super good to hear that you're aware of this problem and are working towards fixing it, the communication with your users using your software to connect to other computers using your software is top notch. Unrivaled. /s 😡