Hi, ever since upgrading to Windows 11 Pro 24H2 I get error code 0x80070035 when i navigate to //[SERVERNAME] via shortcut or through windows explorer. If i attempt to go directly into one of the shares I get the attached login rejection stating "Authentication Failed Because NTLM authentication has been disabled"

 

I've worked through the "Security Is Not a Dirty Word" document applying all suggestions. does anyone know how to get around this issue?

See if this helps:

https://forums.unraid.net/topic/177975-formatted-my-pc-and-installed-fresh-windows-11-now-cant-access-smb-shares/?do=findComment&comment=1478526

 

Sadly, These steps did not help I get the same error After disabling the SMB client signing requirement and verifying insecure guest logins are enabled

I am experiencing the same issue after updating to 24H2, only I'm trying to connect to an openSuse TW smb share. My M1 Mac can connect to it, and my Win 10 box can connect to it, and the Win 11 box can connect to the mac via smb, but not to the linux one. I think that 24H2 update is buggy. It is the only thing that changed on my network and other people have been reporting various sharing and network connectivity issues with this update. 

I gave up and reverted back to 23H2. Blocked the update in group policy. Hope this gets fixed soon. The whole reason i got unraid was for a NAS for my windows PC's.

There's nothing to fix, SMB shares work with a stock Windows 11 24H2 install, if you do the steps linked above, so possibly, there are already some changes in your Windows config.

It's certainly possible. My installs are windows pro and the affected PC's were previously managed via group policy from a windows server, but after hours of trying everything in the linked steps, googling multiple solutions i chose the fresh install route. Perhaps when I have another weekend to burn I'll re-install 24H2 and see if it's totally gone

Edited February 4, 20251 yr by cjyoda78

I was having the same issue and this fixed it for me.

 

Disable the SMB client signing requirement:

a. On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor). If you are using Home edition, skip to step 8.

b. In the console tree, select Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options.

c. Double-click Microsoft network client: Digitally sign communications (always).

d. Select Disabled > OK.

 

Source: https://techcommunity.microsoft.com/blog/filecab/accessing-a-third-party-nas-with-smb-in-windows-11-24h2-may-fail/4154300

I had this problem on a windows 11 Pro PC I added to my work peer to peer network.

Block NTLM (LM, NTLM, NTLMv2)

This policy controls if the SMB client will block NTLM for remote connection authentication.

If you enable this policy setting, the SMB client won't use NTLM for remote connection authentication.

If you disable or do not configure this policy setting, the SMB client can still use NTLM.

=========

(1) To open it, press Win + R, type gpedit.msc, and press Enter (this was on my 11 Pro box, but isn't on my 10 Home box)

Computer Configuration > Administrative Templates > Network > Lanman Workstation.

setting: Block NTLM (LM, NTLM, NTLMv2)

set to: Disabled

Apply the changes and restart the computer or run gpupdate /force.

Note: Another way to do with is in Powershell: Set-SmbClientConfiguration -BlockNTLM $false

(2) you might have to do this first.

Enable SMB 1.0/CIFS Client: Go to Control Panel > Programs > Turn Windows features on or off. Check the box for "SMB 1.0/CIFS File Sharing Support" and restart.

Note: I added gpedit.msc to windows 10 home via this method. The Block NTLM policy was not present in Windows 10 Home in this location .. Computer Configuration > Administrative Templates > Network > Lanman Workstation.

Edited January 6Jan 6 by digitaldoctor