Unable to access Windows Server (2016) using Windows App from MacBook Prod

Question

I am trying to access Windows server (Windows 2016 Standard) from my MacBook Prod(M1 and Sonoma 14.6.1).
I received error: Unable to connect, We couldn't connect to the remote PC because of a security error. If this keeps happening, contact your network administrator for assistance. Error Code: 0x1807

How can I address this error?

Answer 1

Hello,

Thank you for reaching out.

To address the "Error Code: 0x1807" you're encountering when trying to access a Windows Server 2016 machine from your MacBook (M1, running macOS Sonoma 14.6.1), you can follow these steps:

1. Check Remote Desktop Settings on Windows Server

On your Windows Server 2016, make sure that Remote Desktop is enabled.

• Go to Control Panel > System and Security > System.
• Click on Remote settings on the left.
• Under Remote Desktop, ensure that Allow remote connections to this computer is selected.
• Also, uncheck Allow connections only from computers running Remote Desktop with Network Level Authentication (NLA) for troubleshooting. Afterward, you can re-enable NLA once the connection is working.

2. Verify the Firewall Settings

Ensure that the Windows Firewall allows Remote Desktop connections:

• Open Control Panel > Windows Defender Firewall.
• Click on Allow an app or feature through Windows Defender Firewall.
• Ensure that Remote Desktop is allowed on both private and public networks.

3. Check Remote Desktop Version Compatibility

Make sure that your macOS Remote Desktop App is up-to-date and compatible with the version of Windows Server you are using.

Sometimes older versions of the app can cause compatibility issues with newer versions of Windows Server or macOS.

4. Use Correct IP and Credentials

Double-check that you're using the correct IP address or hostname for the server.

Ensure that you're entering the correct username and password, and try using the full domain name (if applicable) for the username (e.g., DOMAIN\username).

5. Check Encryption Level

Windows Remote Desktop can use different encryption levels. If there's a mismatch between what your MacBook Remote Desktop app supports and what the server is configured for, you might encounter errors.

To change the encryption level:

• Open Group Policy Editor on the Windows Server (type gpedit.msc).
• Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.
• Look for Set client connection encryption level and ensure it's set to High Level or Client Compatible.

6. Check for Security Software Conflicts

If you have any third-party security software (like VPNs or antivirus software) on either the server or your MacBook, they could potentially block the Remote Desktop connection. Temporarily disable these and try connecting again.

7. Network Level Authentication (NLA) Issues

If you disabled NLA on the server and the error is resolved, it could point to a problem with NLA. If needed, try enabling NLA again after you've successfully connected by re-checking the Allow connections only from computers running Remote Desktop with Network Level Authentication option on the server.

8. Clear Credentials

If there’s a cached credential conflict on your MacBook, try clearing the stored credentials:

• Go to Keychain Access on your MacBook.
• Search for Remote Desktop credentials and delete any saved credentials for the server.
• Try connecting again and enter the correct credentials when prompted.

9. Check for RDP Licensing Issues

Sometimes RDP licensing on the Windows Server may have expired or is not set up correctly. You can check the Event Viewer for any licensing-related messages that could be causing the issue.

After going through these steps, if the error persists, please let me know, and we can dive into more advanced troubleshooting!