Windows 10: Unable to fully Disable NTLM authentication in Windows VM.

After disabling NTLM authentication on a Windows VM, users are unable to log in or connect via RDP. Kerberos is enabled and configured. Error: "An authentication error has occurred. The function requested is not supported. This could be due to CredSSP encryption oracle remediation."Need assistance ensuring Kerberos-only authentication works with RDP.After disabling the NTLM, I am unable to login to the VM. I can not able to DO RDP . Please note - In the same system i have enabled Kerberos. I am getting below error when trying to access the VM

:)

 

NTLM authentication (or Windows Integrated auth) on E50 not working - any possibilities?

Seems that E50 browser does not accept NTLM authentication (or Windows Integrated auth).

Is there any browser for E50 which works with NTLM auth (or Windows Integrated auth) ?

Thx,

Lauri.
Message Edited by on 14-Dec-2006

08:58 PM

 

key authentication

Quick poll! I finally got around to securing my remote VM by disabling password authentication and using key authentication only for SSH. Curious if others do the same.

 

KB3189866, KB3193494 and KB3194496 cause problem with Chrome and Firefox with authenticated proxy (SQUID)

I'm experiencing the same issue with a company proxy McAfee Web Gateway and a Windows 10 client, after the abovementioned update

I've traced the connection and discovered that the problem is related to Google Chrome not completing the 3-way handshake of NTLM authentication (in particular, step 3)

The issue is very weird considering that, from a comparison between MS Edge and Chrome, step 1 and 2 are the same. Then Edge completes the procedure with the authentication message (step 3) and Chrome stops the sequence returning to the user ERR_INVALID_AUTH_CREDENTIALS.

It looks like there is something in the KB code that breaks the NTLM authentication