An Error Occurred During Logon 0xc000035b Remote Desktop Apple

An Error Occurred During Logon 0xc000035b Remote Desktop Apple

/ Knowledgebase, Remote Desktop Protocol (RDP)

Troubleshooting the “An Error Occurred During Logon 0xC000035B” on Remote Desktop for Apple Devices. Remote Desktop Protocol (RDP) is a popular way for users to remotely access Windows systems from different devices, including Apple macOS. However, like all software, it can occasionally throw errors that disrupt the user experience. One such issue is the error “An error occurred during logon 0xC000035BRemote Desktop Apple”, which often appears when Apple users try to connect to a Windows machine using the Microsoft Remote Desktop app.

In this blog, we’ll dive into what this error means, its causes, and detailed troubleshooting steps to help you resolve it effectively.

What Is the “An Error Occurs By Logon 0xC000035B” on Remote Desktop Errors?

The 0xC000035B error indicates that the authentication process between the client (your Apple device) and the server (the Windows machine) has failed. This error typically occurs when there’s a mismatch in the security protocols or settings used by the client and server.

In simpler terms, the Apple device running the Remote Desktop client is unable to log in to the Windows machine due to a compatibility or configuration issue.

Common Causes of the 0xC000035B Error

This error can be triggered by several multipliers, including:

  1. Security Protocol Mismatch:
    The Remote Desktop client and server use different authentication methods or encryption protocols, causing a logon failure.
  2. Network Configuration Issues:
    Problems like firewalls, NAT configurations, or network restrictions can block the authentication request.
  3. Incorrect Group Policy Settings:
    Certain Remote Desktop policies on the Windows machine might prevent logon attempts from the client.
  4. Outdated Remote Desktop Client:
    Using an older version of the Microsoft Remote Desktop client app on macOS can lead to compatibility issues.
  5. Credential Issues:
    Incorrect username or password, or misconfigured account permissions, can also result in authentication errors.

How to Resolve An Error Occurred During Logon 0xc000035b Remote Desktop Apple

Here’s a step-by-step full guide to troubleshoot & resolve the error:

1. Update the Microsoft Remote Desktop App

Ensure that the Remote Desktop app on your Apple device is up to date. Microsoft frequently releases updates to address bugs and improve compatibility with Windows systems.

Steps:

  • Open the App Store on your macOS or iPhone Operating System (iOS) machine.
  • Search for Microsoft Remote Desktop.
  • Check for updates and install the latest version.

2. Verify Credentials

Double-check the username & password you’re using to merger. If the account is part of a domain, include the domain name (e.g., DOMAIN\username).

Note: If your account requires multi-factor authentication (MFA), ensure you’ve set it up correctly on both the client and server sides.

3. Check Network Configuration

Network restrictions or misconfigurations can block the authentication process.

Steps:

  • Ensure the Windows machine is reachable over the network. Test this by pinging the server’s Internet Protocol address.
  • Verify that the necessary RDP ports (default is 3389) are open on firewalls or routers.
  • If you’re connecting over a VPN, ensure it’s active and properly configured.

4. Enable Network Level Authentication (NLA)

The 0xC000035B error often arises from mismatched NLA settings. Network Level Authentication is a safety feature that requires users to authenticate before creating a RDP session.

On the Windows Server:

    1. Log in to the Windows machine.
    2. Open the System Properties window:
      • Press Win + R, & write sysdm.cpl, & hit Enter.
    3. Navigate to the Remote tab.
    4. Check the box for Allow merger only from PC running Remote Desktop with Network Level Authentication (NLA).
    5. Click Apply and OK.

5. Adjust Group Policy Settings

If NLA is enabled but the issue persists, certain Group Policy settings might be causing the problem.

On the Windows Server:

    1. Open the Group Policy Editor:
      • Press Win + R, write gpedit.msc, & hit Enter.
    2. Navigate to:
      Personal Desktop Setting > Administrative Templates > Windows Components > RDP Services > RDP Session Host > Security.
    3. Locate & edit the seeing policies:
      • User authentication is required for remote connections by using Network Level Authentication: Set it to Enabled.
      • Always prompt for password upon merger: Set to Disabled (Off).
    4. Apply the changes and restart the Windows machine.

6. Update the Windows Server

Outdated versions of Windows may have compatibility issues with modern RDP clients.

Steps:

  • Ensure the Windows machine has the latest updates installed.
  • Settings > Updates & Safety > Windows Update & Press button Check for updates.

7. Change Encryption Levels

The encryption level set on the Windows machine might not be compatible with the Remote Desktop app.

On the Windows Server:

  1. Open the Group Policy Editor.
  2. Navigate to:
    Personal Desktop Settings > Administrative Templates > Windows Components > RDP Services > RDP Session Host > Security.
  3. Locate the policy Set client connection encryption level.
  4. Change the setting to Low or Client Compatible.
  5. Apply the changes and restart the machine.

8. Reinstall Remote Desktop Client

If the above steps don’t resolve the issue, reinstalling the Remote Desktop app can clear corrupted files or configurations.

Steps for macOS:

9. Check for Licensing Issues

If you’re using a Windows Server environment, ensure that you have sufficient RDP CALs (Client Access Licenses) and that the licensing server is properly configured.

10. Reset the RDP Session Host Configuration

If none of the above steps work, resetting the RDP session host configuration might resolve the issue.

On the Windows Server:

  1. Open Server Manager.
  2. Navigate to Remote Desktop Services > Session Host Configuration.
  3. Reset the settings to default & reconfigure the session host.

When to Contact Support

If you’ve tried all the above steps and still encounter the 0xC000035B error, consider reaching out to:

  • Microsoft Support for assistance with RDP configuration.
  • Your IT administrator for network or account-related issues.

Preventing Future Errors

  1. Keep Software Updated: Regularly update both the client and server software to avoid compatibility issues.
  2. Document Configuration Changes: Track any changes to RDP settings to simplify troubleshooting.
  3. Use Diagnostic Tools: Employ tools like Event Viewer on Windows and Console on macOS to identify potential problems early.

Conclusion

The “An error occurred during logon 0xC000035B Remote Desktop Apple” issue can be frustrating, but it is often caused by configuration mismatches that are straightforward to fix. By systematically addressing the possible causes outlined above, you can quickly resolve the error and restore seamless connectivity between your Apple device and Windows machine.

If you’re managing multiple remote desktop connections, consider documenting your configurations to minimize future disruptions. With proper setup and maintenance, RDP can remain a reliable tool for cross-platform remote access.

Related Posts

Scroll to Top