This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 81%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAC%3C/text%3E%3C/svg%3E)
Last week I connected to a remote PC. Today I get an error and can't connect. I have changed nothing on any of the involved machines, what can have happened?
Details:
Since everything works as it should when connecting via VMware, my guess is that either firewall (on my side or the PC side, or the ISP), is the culprit. How can I verify that? Is it possible to ping the RDP port to see if it's open somehow?
Edit: I just realized that I have a virtual Windows 10 on the same machine, so it's most likely not the firewalls, unless RDP in Windows 10 don't use the same port as 2003…
It seems so effin random. No restarts, no changes, no updates. Please help! 🤪
Thanks for the input! 👍
Strange. I tried from a Mac with an older version of RDP, and it didn't work either.
Edit: It turns out that it hade auto-updated. They are both on 10.8.2. Is there any way to downgrade?
Any news from MS?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 67%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBL%3C/text%3E%3C/svg%3E)
Same issue here, happened around the same time. Can no longer connect to one of my Azure VMs. I have to connect via an unaffected one that's in the same vnet. No real help from Microsoft, and I can't even create a ticket for it without signing up for advanced support.
Any news on this?
I have turned off autoupdate because I don't want to get locked out again.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 53%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
My PC on Windows11. Using Microsoft remote desktop version 10.2.3012.0.
Try to connect my work PC(on server of terminals) via hot spot of my iphone.
In connection settings i put ip with port(for example 61.134.124.33:18).
But i have an "Error code: 0x4
Extended error code: 0x0 "
Earlier i didn`t have problem with RDP, but near september 2023 something happened.
To solve problem, i have to reload my iphone. But after sleep mode, i have the same error.
I don`t know how to fix it. Can somebody help?
I solved the problem!
The mobile network operator used to distribute Internet only using the IPv4 protocol, and a year ago it started distributing Internet using the IPv6 protocol. My iPhone itself decided that the ipv6 protocol is better for me and through the hotspot distributes the Internet using this protocol (ipv6). Accordingly, my laptop cannot receive correct routes on this network.
I wrote an official request to the mobile operator and received from him the settings of the cellular data network for my iphone, which allow to limit the protocol version - only ipv4.
Hope this helps someone.
Я вирішив проблему!
Оператор мобільної мережі раніше роздавав інтернет тільки за протоколом ipv4, а рік тому почав роздавати інтернет за протоколом ipv6. Мій iphone сам вирішив, що протокол ipv6 для мене краще і через хот-спот роздає інтернет саме за цим протоколом(ipv6). Відповідно, мій ноутбук в цій мережі не може отримати коректні маршрути.
Я написав офіційний запит мобільному оператору і отримав від нього налаштування мережі стільникових даних для мого iphone, які дозволяють обмежити версію протоколу - тільки ipv4.
Сподіваюсь, що це комусь допоможе.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 28.999999999999996%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFD%3C/text%3E%3C/svg%3E)
Well, I have a virtual Win Server 2019 with TS receiving connections with RDP. I used to have a Win Server 2003 working as a DHCP on my local network, then I decided to remove it and give that task to my Mikrotik router, so this is now the one assigning DHCP addresses in my network. After that change, NO computer that receives an IP through DHCP can connect to my Terminal Services Server using Remote Desktop app (all computers and servers are windows and are correctly licensed), and every time the error is: "Error code: 0x4 - Extended error code: 0x0 ". When I change the IP of every computer (Win 10 Pro or Win11 Pro) to a fixed IP, the connection is stablished. Going back to DHCP and I receive the error. every device is on network A (including the router that now gives DHCP) and TS Server is on network B.
The change was on DHCP server installed in a windows server 2003 before and now is a Mikrotik router who gives DHCP.
Any advice?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 8%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
We are having the same problem. Looks to be since the RDP app update released last week. Only seems to prevent connections to Windows Server 2003.
Thankyou Keir!
I found v10.5.2 on MacUpdate.com, and now I can connect again!
For those who are having the same problem this version can be found here: https://www.macupdate.com/app/mac/8431/microsoft-remote-desktop/old-versions
That's a couple of hours of my life I will never see again… 😝
Weird to say. But y'all are Wildin'
Please move to something like Windows Server 2019 when the Opportunity comes around😵💫
I have Win Server 2019 running a TS with an ERP app, so users connect from their workstations Win10 Pro or Win 11 Pro using RDP. As soon I changed the DHCP Server from Windows to my router, now users can't connect with RDP using DHCP assigned IP addresses, but when I change the IP of workstations for a fixed IP (even the same IP i just receive over DHCP) the RDP works. Change back to DHCP, and receive the same IP, and RDP don't work. Seems like Windows is pushing me to use DHCP on windows and of course that I have to buy CAL licenses. Just for the reference, my router assigning DHCP is a Mikrotik. Have anyone had any solution on this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 22%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
It happens on W11 as a client, W2022 as server.