Mac os ошибка 0x4

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.

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.

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.

Apple Footer

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.
– Next, you will have to launch the Windows registry and navigate through the following hives as described below

ComputerHKEY_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 helpful. If you have any questions, please let me know in the comment session.

Hi

I’ve built this hackintosh which was working perfectly with Yosemite and El Capitan and now with Sierra I’m facing these weird issues. I have spent the last two weeks trying to work it out but getting nowhere!

Build Info:
Motherboard: Gigabyte GA-H61M-S2P-R3 (Native NVRAM and Unlocked MSR 0xE2)
CPU: Intel® Pentium® Processor G2030 (3M Cache, 3.00 GHz)
GPU: Asus NVIDIA GeForce GT 710 2GB (Using VGA port since it’s the only port my Display is supporting)
RAM: Patriot 4GB 1333Mhz DDR3

BIOS Settings:
EIST Disabled
C1E Enhanced, C3/C6, Thermal Monitor Enabled
Turbo Boost Disabled (since my CPU does not support this feature)
OS Type Windows 8 with CSM set to Never (To get UEFI Video Output and clover native resolution)
EHCI/XHCI hand-off Enabled
xHCI Mode Auto

Installed by Vanilla method with Clover 3811 with the latest FakeSMC (RehabMan version)
DSDT dumped and patched by the latest MaciASL (RehabMan version)
SSDT Generated by ssdtPRGen beta 20.5 (tried with and without -xcpm flag)

Problem #1 (Fixed in a way):
So here’s the issue, certain Apps like Messages, Preview crash reporting «Namespace SIGNAL, Code 0x4» as the reason, also the same error pops up when changing Color Profiles on Display Preferences and Mail App goes white screen when viewing certain messages! I’ve realized this error relates to CPUs lacking SSE4.1 support but my CPU supports both SSE4.1 and SSE4.2!
I found a fix (here) by vandroiy2012 on InsanelyMac requiring clover hot patching the kernel but there’s no description regarding what it does and why it fixes the issue, I’ve been wondering if someone could shed some light on this and see if there’s a DSDT patch or Kext that I can implement to fix this? I can’t seem to understand why Sierra would KP on this build while it clearly supports genuine Macs with Ivy Bridge CPU architechtures! Guessing it maybe power management related I tried to switch to XCPM with clover patches but no matter what I can’t seem to get XCPM working on Sierra!

Problem #2:
Sierra reboots automatically almost 5 minutes after waking up from sleep! Then it pops up a message saying Computer was shutdown due to a problem. And whenever I shutdown the machine, everything powers off except the CPU which goes on for like 5 seconds more and then going off, I never had these issues with 10.10 or 10.1.

Solutions I’ve tried so far:
1. Trying the clover patches with and without -xcpm
2. Generating SSDT with and without -xcpm
3. Tinkering with ACPI settings on Clover
4. Trying different kernel patches on Clover (KernelPm, KernelCPU, AICPUPM…)
5. Generating new DSDTs
6. Using different darkwake values to fix the reboot and shutdown issue
6. Clearing NVRAM
7. Having multiple Clean Installs ( Even with vandroiy2012’s patch the first boot Kernel Panics on AppleIntelCPUPowerManagement.kext, Clover does 15 kernel replaces when booting on fresh install I have to disable the patch and setup Sierra and generate caches then re-enable the patch, then it does 1 kernel replaces thereafter. )

If it helps I’ve attached my IOReg 2.1 export, config.plist, DSDT and SSDT and crash reports.

Thanks in advance

Over the summer we build a Remote Desktop Gateway Cluster to provide remote access to workstations for some of our clients.

Initial testing worked great for Mac OS, Windows and Linux users. For Mac OS we had clients download the official Microsoft RDP App from the App Store.

Right before go-live day we updated our RDP template we provide to clients and that’s when things started going wrong for only Mac users…. and only some Mac users.

Clients using Mac OS 10.15.x and Microsoft RDP 1.14.x were greeted with this error message:

Unable to connect

We couldn’t connect to the Remote PC. This might be due to an expired password. If this keeps happening, contact your network administrator for assistance.

Error code: 0x207

I originally came cross this Technet thread when researching the issue: https://social.technet.microsoft.com/Forums/en-US/e0f8f58f-58c9-49fc-9d48-f6bfde830f17/rdweb-authentication-error-0x607?forum=winserverTS

Turns out that didn’t apply to us. The registry entries it mentioned did not exist on our servers.

We found that rolling back the Microsoft RDP Client to 1.13.8 (the latest 1.13.x build) would solve the problem.

We also found that the latest Microsoft RDP Client, 1.14.0, worked fine on Mac OS 10.14.1 but the same was not true for Mac OS 10.15.6.

On a whim one of our Techs still had a copy of our original RDP template we used for initial testing where everything worked and found that it still worked on Mac OS 10.15.6 with Microsoft RDP 1.14.0.

We cracked open the RDP file (it’s just text) to find what the difference was:

We had added the following line:

username:s:OURDOMAIN

In an attempt to make it easier for clients to connect by auto-populating our domain name into the shortcut.

When we removed this line from our template the problem went away.