#Mac rdp settings password
#Mac rdp settings Pc
#Mac rdp settings mac
#Mac rdp settings windows

NTLM authentication within the domain is blocked. Source: Microsoft-Windows-Security-NetlogonДomain Controller Blocked: NTLM authentication to this domain controller is blocked.

#Mac rdp settings windows

On the domain controller, I have a corresponding log event to the failed NTLM authentication request, under Applications and Services logs > Microsoft > Windows > NTLM > Operational:- Log Name: Microsoft-Windows-NTLM/Operational

Network security: Restrict NTLM: Audit Incoming NTLM Traffic: Enable auditing for all accounts.

Network Security: Restrict NTLM: NTLM authentication in this domain: Deny for Domain Accounts to Domain Servers.

Network Security: LAN Manager authentication level: Send NTLMv2 response only.

Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options.

As per various security best-practices and recommendations, I have tried to disable NTLM authentication in the domain, by applying the following group policies to Domain Controllers, using the Default Domain Controllers Policy:. So, looks like a failed Network login using NTLM authentication. GPO Settings and Event Logs, on the Domain Controller Source: Microsoft-Windows-Security-AuditingДЇailure Reason: An Error occured during Logon. If I try and login from a non-Windows client, thereby receiving the above error, the Security Log on the RDP Server shows a failed Logon Event, ID 4625:- Log Name: Security Users intended for remote access are added to the respective remote desktop PC's user group 'Remote Desktop Users', using the lusrmgr.msc MMC snap-in.

Set client connection encryption level: Enabled.

Require user authentication for remote connections by using Network Level Authentication: Enabled.

Require secure RPC communication: Enabled.

#Mac rdp settings password

Always prompt for password upon connection: Enabled.

Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security.

Allow users to connect remotely by using Remote Desktop Services: Enabled.

Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections.

Remote Host Allows delegation of non-exportable credentials: Enabled.

Windows Defender Firewall: Defined Inbound Port Exceptions: 3389:TCP::enabled:Remote Desktop Connections.

Windows Defender Firewall: Allow Local Port Exceptions: Enabled.

Network/Network Connections/Windows Defender Firewall/Domain Profile:.

Computer Settings > Policies > Administrative Templates.

What I think are all the relevant settings from gpresult follow:

#Mac rdp settings Pc

The domain-joined target PC (RDP server) has many GPO's applied. GPO Settings and Event Logs, on the RDP Server

#Mac rdp settings mac

Is there a way I can enable non-Windows clients to connect to domain-joined Windows PCs by remote desktop, without making NTLM authentication exceptions for each target PC? Kerberos doesn't seem available for the Mac RDP Client, is there another authentication mechanism that is supported? If I try and remote into the same PC from a Windows PC, using the native Windows Remote Desktop client, I don't get this error, and can connect fine. If this keeps happening, contact your network administrator When I try and start a Remote Desktop session from a Mac to a Windows domain-joined PC, using Microsoft's latest Remote Desktop Client (v10.3.9 currently), I'll often receive the error in the following screenshot. This has been bugging me for quite a while (and no amount of internet searching has amounted to a decent solution), so I'm hoping someone can offer some sage advice.