I can't connect to remote desktop

Install the current Windows App for macOS, recreate the connection using the remote PC’s IP address, and test it before changing credentials or advanced settings.

Microsoft Remote Desktop has been replaced by Windows App for supported macOS connections, and Microsoft’s published known-issues list does not identify a connection failure specifically associated with version 27.2.1.^1^^2^

Recreate the connection in Windows App

1. Install the latest Windows App from the Mac App Store.
2. Open it and select Devices.
3. Select + → Add PC.
4. In PC Name, enter the remote computer’s IP address, not its saved hostname.
5. Select Add, then double-click the new connection.^3^

Using the IP address distinguishes a name-resolution problem from a broader RDP failure. If the IP address works but the computer name does not, the problem is DNS/name resolution.^4^

If this is an office computer reached through a VPN or Remote Desktop Gateway, connect to the required corporate VPN first or obtain the correct gateway configuration from the administrator. Direct RDP from outside the office network works only when the organization provides an external-access method such as VPN or RD Gateway.^4^

If both the name and IP address fail

Someone with local or administrative access to the Windows computer should check:

1. Power state: The PC must be on and awake, not sleeping or hibernating.
2. Remote Desktop: Open Settings → System → Remote Desktop and confirm Remote Desktop is enabled.
3. Windows edition: A directly accessed Windows PC must run a supported Pro edition rather than Home.
4. Firewall: In Windows Firewall, select Allow an app or feature through Windows Firewall, choose Change settings, and allow Remote Desktop.
5. User access: Confirm your account is in Remote Desktop Users or the local Administrators group.^4^

From another Windows computer on the same network, an administrator can test whether the RDP port is reachable:

Test-NetConnection `
  -ComputerName <remote-PC-IP> `
  -Port 3389 `
  -InformationLevel Detailed

• TcpTestSucceeded: True means the network path and RDP port are reachable; investigate the Windows host configuration or client.
• TcpTestSucceeded: False indicates a network, VPN, firewall, or listener problem.^5^

On the remote Windows computer, an administrator can verify that RDP is listening:

cmd /c 'netstat -ano | find "3389"'
Get-Service TermService

Port 3389 should show LISTENING, and TermService should be running. If another process owns port 3389, resolve that conflict rather than changing the RDP port.^6^

If Windows App itself still appears broken

If the same PC connects from another device but fails only on this Mac:

1. Remove Windows App from macOS and reinstall the latest release.
2. Re-add the PC instead of importing the old saved connection.
3. If upgrading from Microsoft Remote Desktop caused saved credentials to disappear, update the relevant com.microsoft.rdc.macos entries in Keychain Access → login → Access Control so Windows App can access them.^2^
4. In Windows App, select Help → Submit Feedback and include:
   • macOS version and Mac model
   • Windows App version
   • Whether hostname and IP both fail
   • Whether VPN is involved
   • Exact error text and time of failure^7^

The available Microsoft documentation does not provide an official macOS command or log-file path for this exact failure. The IP-address test and port test above are the supported ways to separate DNS/client issues from VPN, firewall, and Windows-host failures.

References

1. Connect to Remote Desktop Services in Windows Server
2. Known issues and limitations of Windows App - Windows App
3. Get started with Windows App to connect to devices and apps (remote-pc)
4. Frequently asked questions about the Remote Desktop clients
5. Remote Desktop can't connect to the remote computer
6. General Remote Desktop connection troubleshooting
7. Basic troubleshooting for Windows App - Windows App | Microsoft Learn