Microsoft Remote Desktop Mac Error Code 0x4
Rafa Ostermann
This article helps you understand the most common settings that are used to establish a Remote Desktop session in an enterprise environment, and provides troubleshooting information for Remote desktop disconnected errors.
A Remote Desktop Session Host server is the server that hosts Windows-based programs or the full Windows desktop for Remote Desktop Services clients. Users can connect to an RD Session Host server to run programs, to save files, and to use network resources on that server. Users can access an RD Session Host server from within a corporate network or from the Internet.
Remote Desktop Session Host (RD Session Host) was formerly known as the Remote Desktop server role service, and Remote Desktop Session Host (RD Session Host) server was formerly known as Remote Desktop server.
When you try to make a Remote Desktop Connection (RDC) to a remote computer or to a Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2, you receive one of the following error messages:
Remote Desktop Disconnected.
This computer can't connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
Also, you are limited in the number of users who can connect simultaneously to a Remote Desktop session or Remote Desktop Services session. A limited number of RDP connections can be caused by misconfigured Group Policy or RDP-TCP properties in Remote Desktop Services Configuration. By default, the connection is configured to allow an unlimited number of sessions to connect to the server.
You experience a port assignment conflict. This problem might indicate that another application on the Remote Desktop server is using the same TCP port as the Remote Desktop Protocol (RDP). The default port assigned to RDP is 3389.
Remote Desktop Services clients are repeatedly denied access to the Remote Desktop server. If you are using a Remote Desktop Services client to log on to the Remote Desktop server, you may receive one of the following error messages.
Because of a security error, the client could not connect to the Terminal server. After making sure that you are logged on to the network, try connecting to the server again.
Remote desktop disconnected. Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again.
If you select Don't allow connections to this computer on the Remote tab, no users will be able to connect remotely to this computer, even if they are members of the Remote Desktop Users group.
On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services.
If the Maximum connections option is selected and dimmed, the Limit number of connections Group Policy setting has been enabled and has been applied to the RD Session Host server.
The Remote Desktop Users group on an RD Session Host server grants users and groups permission to remotely connect to an RD Session Host server. You can add users and groups to the Remote Desktop Users group by using the following tools:
On the Remote tab in the System Properties dialog box, click Select Users. Add the users or groups that have to connect to the RD Session Host server by using Remote Desktop.
If you select the Don't allow connections to this computer option on the Remote tab, no users will be able to connect remotely to this computer, even if they are members of the Remote Desktop Users group.
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, seeHow to back up and restore the registry in Windows.
To resolve this problem, determine which application is using the same port as RDP. If the port assignment for that application cannot be changed, change the port assigned to RDP by changing the registry. After you change the registry, you must restart the Remote Desktop Services service. After you restart the Remote Desktop Services service, you should verify that the RDP port has been changed correctly.
The listener component runs on the Remote Desktop server and is responsible for listening for and accepting new Remote Desktop Protocol (RDP) client connections, thereby allowing users to establish new remote sessions on the Remote Desktop server. There is a listener for each Remote Desktop Services connection that exists on the Remote Desktop server. Connections can be created and configured by using the Remote Desktop Services Configuration tool.
If you have to change the port assigned to RDP, you must change the registry. To do this, you must be a member of the local Administrators group, or you must have been granted the appropriate permissions.
For the RDP port assignment change to take effect, stop and start the Remote Desktop Services service. To do this, you must be a member of the local Administrators group, or you must have been granted the appropriate permissions.
Remote Desktop Connection and the Terminal server Web Client use port 3389, by default, to connect to a Remote Desktop server. If you change the RDP port on the Remote Desktop server, you will have to modify the port used by Remote Desktop Connection and the Remote Desktop server Web Client. For more information, see Change the listening port for Remote Desktop on your computer.
On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see 322756 How to back up and restore the registry in Windows.
To resolve this problem, back up and then remove the X509 Certificate registry keys, restart the computer, and then reactivate the Remote Desktop Services Licensing server. To do this, follow these steps.
If this article does not help you resolve the problem, or if you experience symptoms that differ from those that are described in this article, visit the Microsoft Support for more information. To search your issue, in the Search support for help box, type the text of the error message that you received, or type a description of the problem.
I updated it last night and have the same issue. Was connected minutes before executing the update. After the update I cannot connect in any way. I'm getting Error code: 0x300005b when executing a workspace connection. Also, I'm getting Error code: 0x3000064 when executing a downloaded RDP file. None of my connections are working.
I had the same problem before updating on Mac,iPad,iPhone. When I disabled mobile data it throws an error. Active mobile data, RD client works. Mobile data has no effect on Android devices. It's terribly annoying that it doesn't work well on Apple products.
Apologies for any inconvenience caused by this issue. Can you please confirm which type of host you are remotely connecting to? Whether that is: Azure Virtual Desktop, Windows 365, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, a personal PC running Windows 11, Windows 10, Windows 8.1.
In the meantime, if your issue is specific to version 10.8.0 please download the most recent stable beta build at aka.ms/rdmacbeta (10.7.9) to continue your productivity while our team tracks down this issue. Thanks
Hello @js351. I want to connect from a device (Mac, iPhone, iPad) using the RD Client to a PC with Windows 10.
When mobile data is enabled on iPhone, remote desktop works, then I disable the data, remote desktop doesn't work, It throws an error. On an Android phone, remote desktop works even when mobile data is not active. We cannot connect via Mac and iPad at all. Thank you for the correction. Rome
For workspace cases, does refreshing or deleting/readding the workspace resolve the issue? The error codes 0x3000064 and 0x300006c could be the product of various issues so further investigation will be helpful, to help us triage can you please collect some traces. Set the core log level to "Information", then start logging and repro the issue. Please send the logs to rd...@microsoft.com please. Thanks
We are continuing to have problems with 10.8.0 on our University campus. The solution proposed today is not working for us. While away from the campus network and connected to the campus network using an always-on GlobalProtect configuration, attempts to connect to any host using its dns name are failing with a 0x204 error, but will connect when using the assigned IP address. They are essentially acting as if the host is turned off. However, attempting to connect to the same host, but with Cisco AnyConnect instead of GlobalProtect, allows us to connect, using DNS or IP address. We've set the defaults spring, with no luck.
I'm trying to remote onto a Windows 2012 Server using Remote Desktop Connection for Mac. Using the same credentials, it works from my Windows PC (using Remote Desktop for Windows), but trying to do it from my Mac I get the error: