Hello, since today I have problems logging into the app from my Mac. I have tried different ways but I have not been able to solve anything. The problem is that I don't have/can't access my Windows computer, as I am connected via internet. Does anyone know a way to solve the problem from the Mac (I have already tried to delete the "Group Containers" but it didn't work).
This is the message that appears every time:
"We couldn't connect to the remote PC. Make sure the PC is turned on and connected to the network, and that remote access is enabled.
Error code: 0x204"
I have been having the same problem and it's really vital that I'm able to use the remote connection; I also can't access the Windows computer, and have tried the Group Containers thing with no success. Did you manage to solve the problem?
Similar problems here. RDS fails to connect. Only solution is to restart the Windows 11 machine. Nothing else fixes this. In my case, the problem starts when I make an smb connection for sharing drives on my Mac from the windows machine. If it's a fresh start (or I'm lucky) the connection will work immediately. It lasts for a few hours, and at some random time later, it fails without explanation or error - just the connection is gone. Attempts to RDS into the windows machine to diagnose/fix the problem also fail with our famous 0x0204 error. Restart the windows machine, and all is well for a while until it shuts down again, and round and round. I have been working on this problem for several months without success. I have no replies from any Microsoft source.
Note: It's worthy to mention that error code 0x204 may also appear on the iPad. Please check if you are using the latest version of the Microsoft Remote Desktop app. You can uninstall the app and reinstall the latest version and see if that helps in resolving the issue
There are five solutions to fix Microsoft Remote Desktop error code 0x204. You need to enable a remote connection or edit firewall settings on your Windows 10. Besides, you need to enter the IP address of Windows 10 instead of entering its PC name. Additionally, you can delete the Remote Desktop temporary files from Mac. If the issue persists, open port 3389 on both devices.
Actually, you have multiple options to remotely control another computer. For example, you can use Chrome Remote Desktop from Mac to Windows. Or if you are looking forward to finding free yet professional remote desktop software for Windows, you can use AnyViewer, which can provide you with stable and fast unattended remote access.
I too am having this issue. Everything is on the same network and it was working until a month or so ago. I can RDP from my Mac to a Windows 11 Machine but when I try to connect via RDP from a Windows 11 machine to the same Windows 11 machine, I can not connect.
One of the most common problems with error code 0x204 is an instance of Remote Desktop Protocol not enabled on your Windows computer. In this case, you can manually enable it through the System Properties screen and allow network-level connections to resolve the issue.
However, this could also be caused by your firewall (since the process used by Remote Desktop is exploited by many malware). In order to fix this, in this case, you need to establish exclusion rules, disable real-time protection, or completely uninstall third-party security suites.
This issue happens only when I am connected via VPN using T-Mobile network. When using VPN on a WiFi network it works perfectly, it also works fine when used via WiFi within the same network where my computer is connected here in my office.
There shouldn't be anything specific to the RD client running on your old iPad's software vs your new iPad's software that would affect error code 0x204. Is this error reproducible? Or has it just happened a couple times?
Good morning, thanks for your prompt reply and yes, it is happening all the time, I mean, RD Client on T-Mobile is not working at all on any of the 5 new Ipads we just purchase for some executives. I have to insist: RD works perfectly when I am connected to WiFi within our network and also when using VPN on an external WiFi network but it doesn't work when there is no Wifi just the T-Mobile data network, which is when is most needed. The VPN connects fine but when RD is open the error shows.
The app engineering team does not have any guidance to provide related to your Remote Desktop issue at the time as it seems mostly related to accessing session hosts via VPN using T-Mobile network which is not an issue they have seen/delt with before.
VPN issues can have several causes. The first step is to verify that the VPN works on the same network as your PC or Mac computer. If you can't test with a PC or Mac, you can try to access a company intranet web page with your device's browser.
Good morning, thanks for your follow up and research, we found out that there is an issue with the latest version between IOS and VPN connectivity, with previous versions everything works perfectly, but with the most recent it doesn't work, we were able to make it work using domain name server instead of IP addresses which is weird because it should be able to work with both, we still are also researching on our side. Happy Holidays.
P.P.S. I tried another experiment, this time using the iPhone 12 mini with only the (T-Mobile) cellular enabled as a hotspot connection for my WiFi Samsung tablet. The Remote Desktop client on my Samsung Tablet was able to connect via OpenVPN to my Windows 10 PC (through T-Mobile using the iPhone 12 mini's hotspot).
I am experiencing this issue with the latest iPad, OpenVPN connects effortlessly, Remote Desktop clocks and then gives the error 0x204. As with the others, when using WiFi in the office it works as well.
Just as a "FYI": I'm not sure how the "DNS server workaround" mentioned above was implemented. As another test, for "PC Name" in the RD Client, I replaced the private IP address of the Windows PC I am trying to connect to with my dynamic DNS server address but as I expected, I still could not connect via OpenVPN. The reason I doubted it would work is that my dynamic DNS server address points to the internet address of my router (the same router that serves as my OpenVPN server) and not to the target PC with the private IP address. As before, as soon as I switch from cellular to WiFi the connection works fine.
I'm wondering if this workaround is successful because for your situation, use of the pc's hostname causes circumvention of the VPN connection altogether. If I'm right, you are instead connecting via another mechanism (such as SMB). In any event, hostname doesn't work for me when I connect via cell phone using OpenVPN from either Android or iPhone. For the Android Remote Desktop app the host's private IP address does work. For the iPhone Remote Desktop app, it doesn't.
not exactly, I have to go back to where the problem started: on my new Ipad the RDC app didn't work when connected VPN using T-Mobile network to access my PC , after some research I noticed that the fix was to add my PC to the RDC App using the PC host name (instead of IP), the pc name found in Windows - Control Panel - System - and with this modification the connection started to work when VPN using T-Mobile from anywhere.
I am having a similar issue. I have tested iPad connected to my verizon hotspot, iphone as a hotspot, and two other backup cellular connections. If I connect to verizon, or either of the two backups (all 3 of these have IP addresses that start with 192.168.1.....) and then connect to my company's VPN the RDClient app gives me the Error code: 0x204. However, when I connect my iPad to my iPhone hotspot (ip 172.20.1......) and the VPN, it connects. I mention the IPs because the desktops i'm attempting to connect to are also on a subnet that starts with 192.168.1..... My Network Admin thought that may be playing a part of the issue. In addition I tested these same 4 wifi connections with my windows laptop using the native RDP and all combinations worked.
Its the iPad with RDClient & wifi in 192.168.1 subnet that cause the error. I tried my host name instead of ip, but that did not work.
Thank you
TLDR: I added a 2nd VPN server to my private network and when using that server there is no problem. In my view this tends to shift the blame away from the Microsoft Remote Desktop APP and towards the VPN server itself (but that is debatable).
This second VPN server works perfectly well although I'm required to this Windows 10 computer (and the virtual Ubuntu machine) powered on to insure availability of my private network via Remote Desktop. At some point I'll check with the folks at ASUS and see if they are willing to work on this issue (assuming they can reproduce it).
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