Hi,
I’m running Microsoft Remote Desktop
10.2.1 (1143) Beta on Mac High Sierra 10.13.6 attempting to connect to a local (LAN) Windows 10 system.
I can connect initially, but if I suspend the Mac and reopen it and try to connect via MRD I get the error «Your session ended because of an error. If this keeps happening, contact you network administrator for assistance. Error ode: 0x4»
If I reboot the Windows 10 box, or connect to it via another remote tool (eg TeamViewer) and then disconnect, I can reuse MRD to connect again.
It’s as if its maintaining the original connection, and can’t reconnect.
I’ve only recently started using V10, and V8 had been working fine. I re-downloaded V8 and tried to connect whilst I was getting the V10 0x4 error and in V8 the msg is «Connection reset by peer».
Anything I can check on the network/router, Mac or Windows settings?
I also see a few other entries on here of similar issues from Mac High Sierra with no responses — has something recently changed on the Mac side that is causing issues?
Thanks.
You have a Mac Computer and are running Microsoft Desktop (RDP) throws an Error code: 0x4 just randomly when you try to connect to a computer you have configured for connection.
For us, this problem just randomly started this year after Microsoft updated their RDP software. “Go Microsoft”
We have searched the web, and noticed that the suggestions to Reboot the computer, or restart the RDP software, or both. Do not appear to reliably work. Although we did have some luck with this.
Another suggestion was to copy or recreate the connection in RDP. Again, only limited success with this solution.
The Fix for 0x4 Errors on Mac RDP Remote Desktop Connection
For us the solution came when we went into the system preferences of the Remote Desktop Connection
And you will notice the default preferences look something like this.
We simply unticked the “Use hardware acceleration when possible” check box.
That’s it. After doing this you should notice that it can fixe in some cases the Mac RDP not connecting with 0x4 Errors.
Update
We have found that the errors can reoccur, which is super frustrating. So there are a few other tips that we have found can assist.
Reboot
It’s odd, but sometime rebooting the computer that is making the connection, and help in eliminating the 0x4 error.
Duplicate the Connection
If you right click / or Two finger click on the connection, and select Duplicate – Then use the duplicated connection, sometimes that can allow you to connect.
Try Again
When all else has failed, trying to connect from the connection multiple times can also sometimes work after multiple attempts.
Alternating the Attempts
Lastly, trying the original connection, or alternating between the original, then the newly duplicated connection (in the point above) can also help.
Basically we know these are not solutions, but we have found that they definitely can assist in helping to get the connecting going and avoiding the 0x4 error. Hope it helps, and if you find anything else that eliminates or reduces the error, please chime in.
Skip to content
Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft which provides a user with a graphical interface to connect to another computer over a network connection. You will receive the following error “Your session has ended because of an error: Error Code 0x4″ whenever your Mac goes to sleep”. Below are some troubleshooting guides relating to RDP “We could not connect to the remote PC with error code 0x204 and make sure the PC is turned on and connected to the network–Part 1” and We could not connect to the remote PC with error code 0x204 and make sure the PC is turned on and connected to the network–Part 2.
Since this is actually not a problem, please use the following steps below to mitigate this issue. 
Solutions: Kindly refer to the steps below to resolve these issues.
1: Launch a new RDP connection or
2: Simply increase the maximum outstanding connections limit on the windows client machine. The following DWORD registry key controls this value.
See the following hyperlinks for what is Registry Editor and how to access the registry hives and how to search through Windows Registry.
-Launch the Windows registry, navigate through hives to troubleshoot the 0x4 Session Disconnection Error, as described below.
Computer\HKEY_LOCAL_MACHINE
- SYSTEM
- CurrentControlSet
- Control
- Terminal Server
- MaxOutstandingConnections
Now create the DWORD key if your machine doesn't have it.
- Set it to 10,000 (hex value)I hope you found this blog post about the 0x4 Session Disconnection Error helpful. Please let me know in the comment session if you have any questions.
- Remove From My Forums
-
Question
-
I am using both Microsoft Remote Desktop Beta Version 10.2.1 (1143) and Microsoft Remote Desktop
Version 8.0.43 (Build 27325) but I can’t seem to remote into any machines. In this case I am trying to connect to a machine using an .rdp file. My computer is a Macbook Pro (Retina 15-inch Mid 2015) using MacOS High Sierra 10.13.6
On the Beta version I get this error:
Your session ended because of an error. If this keeps happening, contact your network administrator for assistance.
Error code: 0x4
On the non-Beta version I get a Connection Reset By Peer error so neither work.
Can somebody help?
Thank you!
-
Edited by
Tuesday, August 7, 2018 2:27 PM
-
Edited by
With the Android client I get the error message Error code: 0x4 and the following tcpdump:
tcpdump -vv -nn -i ens192 host 172.20.254.123
tcpdump: listening on ens192, link-type EN10MB (Ethernet), capture size 262144 bytes
17:16:36.336602 IP (tos 0x0, ttl 64, id 62316, offset 0, flags [DF], proto UDP (17), length 78)
172.20.254.123.49935 > 255.255.255.255.137: [udp sum ok] UDP, length 50
17:16:36.336733 IP (tos 0x0, ttl 64, id 58314, offset 0, flags [DF], proto TCP (6), length 60)
172.20.254.123.45876 > 172.20.254.130.3389: Flags [S], cksum 0xc7ac (correct), seq 133865233, win 65535, options [mss 1460,sackOK,TS val 2654479732 ecr 0,nop,wscale 9], length 0
17:16:36.336806 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto TCP (6), length 60)
172.20.254.130.3389 > 172.20.254.123.45876: Flags [S.], cksum 0xb2d0 (correct), seq 3338194830, ack 133865234, win 65160, options [mss 1460,sackOK,TS val 2291726115 ecr 2654479732,nop,wscale 7], length 0
17:16:36.338037 IP (tos 0x0, ttl 64, id 58315, offset 0, flags [DF], proto TCP (6), length 52)
172.20.254.123.45876 > 172.20.254.130.3389: Flags [.], cksum 0xdf6e (correct), seq 1, ack 1, win 172, options [nop,nop,TS val 2654479743 ecr 2291726115], length 0
17:16:36.338759 IP (tos 0x0, ttl 64, id 58316, offset 0, flags [DF], proto TCP (6), length 71)
172.20.254.123.45876 > 172.20.254.130.3389: Flags [P.], cksum 0xcd4b (correct), seq 1:20, ack 1, win 172, options [nop,nop,TS val 2654479744 ecr 2291726115], length 19
17:16:36.338793 IP (tos 0x0, ttl 63, id 45125, offset 0, flags [DF], proto TCP (6), length 52)
172.20.254.130.3389 > 172.20.254.123.45876: Flags [.], cksum 0xde07 (correct), seq 1, ack 20, win 509, options [nop,nop,TS val 2291726117 ecr 2654479744], length 0
17:16:36.339830 IP (tos 0x0, ttl 63, id 45126, offset 0, flags [DF], proto TCP (6), length 52)
172.20.254.130.3389 > 172.20.254.123.45876: Flags [F.], cksum 0xde05 (correct), seq 1, ack 20, win 509, options [nop,nop,TS val 2291726118 ecr 2654479744], length 0
17:16:36.340697 IP (tos 0x0, ttl 64, id 58317, offset 0, flags [DF], proto TCP (6), length 52)
172.20.254.123.45876 > 172.20.254.130.3389: Flags [F.], cksum 0xdf53 (correct), seq 20, ack 2, win 172, options [nop,nop,TS val 2654479746 ecr 2291726118], length 0
17:16:36.340738 IP (tos 0x0, ttl 63, id 45127, offset 0, flags [DF], proto TCP (6), length 52)
172.20.254.130.3389 > 172.20.254.123.45876: Flags [.], cksum 0xde01 (correct), seq 2, ack 21, win 509, options [nop,nop,TS val 2291726119 ecr 2654479746], length 0