Microsoft Remote Desktop

In all likelihood, there’s no network connection and no path available between the sites, or there’s a firewall or three that’s blocking that access. There’ll need to be either public static IP addresses for the target systems at the office and a path opened through the firewall, or private IP addresses and port-forwarding configured through the firewall, or a VPN configured and established between the remote client and the target network. Or IPv6 and a path through the firewall. There’ll probably want to be a public DNS name established for the target host, too.

Check with the local networking folks for assistance.

That’s a guess.

Alternatively... Please check the Microsoft support forums for assistance with that app, or contact Microsoft support.

swhitling wrote:

Did you have any luck fixing this? I am having the same problem. When I upgraded to the new version of Remote Desktop, this error started appearing and I haven't been able to remote in.

Check the release notes and related docs for changes and any new port-forwarding requirements that might exist in the updated version, and run the network scans to check for network access to the Microsoft-cited open ports through the various network links. (Network Utility.app is still latent in macOS—use Spotlight to find it, as it's moved around over the years—and that tool can be useful here, if you're not comfortable with the command-line tools.) Then? Ask Microsoft? There's not a lot of MRD traffic here in the ARD forum.

Did you have any luck fixing this? I am having the same problem. When I upgraded to the new version of Remote Desktop, this error started appearing and I haven't been able to remote in.

Thanks!

Sarah