Windows 10: "Authentication failed because NTLM authentication has been disabled" Cannot connect to...

Problem:I updated my PC from 23H2 to Windows Pro 24H2 and can no longer see my Synology NAS or access the pre-mapped network drives. Attempts to remap the drives fail, “Authentication failed because NTLM authentication has been disabled.” This is my third time trying to fix this problem after rolling back to 23H2 on the previous attempts before the 10-day limit expired. Platformsell OptiPlex 7060 MT refurb, i7-8700, 32GB of DDR4-2666, Samsung EVO 970 Plus M.2 500 GB.Windows 11 Pro 24H2, Build 26100.3037, Windows Feature Experience Pack 1000.26100.48.0, with all current updates as of 0

:)

 

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

 

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