Hey everyone! I've been having this strange issue with NTLM authentication after updating to 25H2 and installing KB5065426 a few months back. After coming back from a vacation, I noticed that I started getting errors saying that NTLM is disabled. I've tried running `Set-SMbClientConfiguration -BlockNTLM $false` to unblock it, enabled guest logins with `Set-SmbClientConfiguration -EnableInsecureGuestLogons $true`, and checked the local group policy settings. They seem fine since I ensured that the Network Security: Restrict NTLM settings are configured properly. I've even created server exceptions. Thankfully, this issue is only affecting my machine at work. Has anyone found a way to resolve this? Thanks for any help!
3 Answers
Don't forget to look at the event logs! They can provide detailed information about why NTLM authentication is failing on 25H2. They might point you in the right direction.
It sounds like the update might have disabled NTLMv1. Make sure the server you’re connecting to supports at least NTLMv2. Don't forget to check that your PC is fully up to date and restart it if you haven’t yet. If this isn’t the issue, also consider checking out Microsoft’s support page about Kerberos and NTLM authentication failures, just in case your computer was set up incorrectly.
Have you checked the server's configuration? Sometimes, it’s a good idea to upgrade your SMB security settings to ensure compatibility.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures