Win11 24H2 Installed, now no network sharing

lafargeotte · Oct 1, 2024

Hi Guys,

I upgraded to 24H2 Pro on my desktop and one laptop.
Two laptops still on 23H2 Pro.

The laptops on 23H2 still have network sharing seeing all PCs and able to access the shared folders.
The 24H2 PCs see the other PCs, but have no access to sharing, with error message 'Network Path Not Found'.

Network settings on all 4 PCs are the same, although SMB1 was not installed on the 24H2 machines!

I went to the Tutorial and tried the suggestions there, but no luck.

There must be something obvious, but I cannot see what it is.

Any suggestions please?

Bree · Oct 1, 2024

lafargeotte said:
The laptops on 23H2 still have network sharing seeing all PCs and able to access the shared folders.
The 24H2 PCs see the other PCs, but have no access to sharing, with error message 'Network Path Not Found'.

In 24H2 tighter security restrictions that were previously only enforced in Enterprise and above are now on by default in Pro. Insecure logins are not allowed by default, you now cannot connect to another PC if you have a local account with no password.

There are two ways to connect. The first is to create a Windows Credential for an account with a password on that other PC.

The second is to turn off the restriction on insecure logins.

Microsoft said:
Select Start, type gpedit.msc, and select Edit group policy.

In the left pane under Local Computer Policy, navigate to Computer Configuration\Administrative Templates\Network\Lanman Workstation.

Open Enable insecure guest logons, select Enabled, then select OK.

Enable insecure guest logons in SMB2 and SMB3 for Windows client and Windows Server

This article describes how to enable guest logons policy in SMB2 and SMB3 for Windows client and Windows Server devices using Group Policy and PowerShell.

learn.microsoft.com

lafargeotte · Oct 2, 2024

Bree said:
In 24H2 tighter security restrictions that were previously only enforced in Enterprise and above are now on by default in Pro. Insecure logins are not allowed by default, you now cannot connect to another PC if you have a local account with no password.

There are two ways to connect. The first is to create a Windows Credential for an account with a password on that other PC.

The second is to turn off the restriction on insecure logins.

Enable insecure guest logons in SMB2 and SMB3 for Windows client and Windows Server

This article describes how to enable guest logons policy in SMB2 and SMB3 for Windows client and Windows Server devices using Group Policy and PowerShell.

learn.microsoft.com

View attachment 110750

Thank you so much Bree.

However, I have now upgraded another laptop and despite having made the change as you suggested, that does not help. As a stop gap, I have passworded that laptop, and then networking is fine.
The desktop and first laptop upgraded now work fine.

jimbo45 · Oct 2, 2024

Bree said:
In 24H2 tighter security restrictions that were previously only enforced in Enterprise and above are now on by default in Pro. Insecure logins are not allowed by default, you now cannot connect to another PC if you have a local account with no password.

There are two ways to connect. The first is to create a Windows Credential for an account with a password on that other PC.

The second is to turn off the restriction on insecure logins.

Enable insecure guest logons in SMB2 and SMB3 for Windows client and Windows Server

This article describes how to enable guest logons policy in SMB2 and SMB3 for Windows client and Windows Server devices using Group Policy and PowerShell.

learn.microsoft.com

View attachment 110750

I HATE WINDOWS NETWORKING -- For me it's broken again - Nothing I do can make this PC see other PC's on the LAN --- updated this one from 23H2 which was working OK -- I can only get access to other machines if I enter their IP addresses -- shouldn't have to do that.

The Linux machines can see this Windows machine without any issue. C'mon Ms why is it that Networking is always so random with Windows -- after all this is meant to be the RTM release - and 99% of users on this release aren't Network gurus or even have access (unless they know about this great Forum) to decent help.

Cheers
jimbo.

Wolfzz · Oct 4, 2024

OK with 24H2 Pro 26100.1742 I had this problem.
My Windows 10 Pro could access Windows 11 24H2 through my network, however Windows 11 24H2 could not access my Windows 10 Pro or any earlier versions of Windows 11 Pro Computers this only happened since I went to 24H2.
To fix this issue I did both of these changes in Local Group Policy Editor. And Now all is happy including me. I hope this helps.

Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options
Double click on Microsoft Network Client: Digitally sign communications (always)
Double click on Microsoft Network Client: Digitally sign communications (if server agrees)
Set both of these to "Disabled"
Click on OK.

Computer Configuration, Administrative Templates, Network, Lanman Workstation
Double click on "Enable Insecure Guest Logons"
Set this to "Enabled"
Click on OK.

LarsYouPutz · Oct 5, 2024

Wolfzz said:
OK with 24H2 Pro 26100.1742 I had this problem.
My Windows 10 Pro could access Windows 11 24H2 through my network, however Windows 11 24H2 could not access my Windows 10 Pro or any earlier versions of Windows 11 Pro Computers this only happened since I went to 24H2.
To fix this issue I did both of these changes in Local Group Policy Editor. And Now all is happy including me. I hope this helps.

Computer Configuration, Windows Settings, Local Policies, Security Options
Double click on Microsoft Network Client: Digitally sign communications (always)
Double click on Microsoft Network Client: Digitally sign communications (if server agrees)
Set both of these to "Disabled"
Click on OK.

Computer Configuration, Administrative Templates, Network, Lanman Workstation
Double click on "Enable Insecure Guest Logons"
Set this to "Enabled"
Click on OK.

Hi Wolfzz,

I just wanted to let you know that I registered to this site just to say THANK YOU for this post. I was just doing a fresh install and wasn't able to connect my network drives on a PC that previously had been connected. Difference, when I downloaded a fresh copy of W11, it was 24h2 and not the previous 23h2 that had been on there. I've had no problem over the years networking all my PCs together, but this one had me banging my head against the wall for the last five hours.

I had previously done the Enabling Insecure Guest Logons part of your suggestion and that alone didn't do it. Then I found your post, and the...
"Computer Configuration, Windows Settings, Local Policies, Security Options
Double click on Microsoft Network Client: Digitally sign communications (always)
Double click on Microsoft Network Client: Digitally sign communications (if server agrees)
Set both of these to "Disabled"
Click on OK"
... part did the trick.

Again, thanks a ton!

Berton · Oct 5, 2024

Isn't Build 26100 still in the Insider Preview area? Anyhoo, I did my LAN different, have a NAS drive, 5 Desktops [Win7 Win10 Win11 Linux Mint] and my workbench plus 2 printers attached to the Wireless Router, all via Ethernet. I will have various Wireless/Wi-Fi computers connected when needed, don't even try to connect to an individual computer from another, just keep all the things to be shared on the NAS drive, a whole lot less headache. For Internet service my ISP provides a small PoE Modem that provides Wireless DSL, it connects via Ethernet to my Router. The Router has 4 input ports, 1 Uplink port for the Modem and I added an 8-port Switch, all are Gigabit.

Bree · Oct 5, 2024

Berton said:
Isn't Build 26100 still in the Insider Preview area?

The Insider Preview Channel 26100 appears to be identical to the 24H2 26100 that MS released publicly on 1st October.

Berton · Oct 5, 2024

Bree said:
The Insider Preview Channel 26100 appears to be identical to the 24H2 26100 that MS released publicly on 1st October.

Haven't seen it yet for my machines, only the version for the Copilot+ PCs.

Bree · Oct 5, 2024

Berton said:
Haven't seen it yet for my machines, only the version for the Copilot+ PCs.

It has been freely available at Download Windows 11 since 1st October.

It's bound to be a gradual rollout (as it has been for all previous new versions). None of my supported machines have been offered 24H2 yet either. But I did get one of my machines to see and install it through Windows Update by setting the Target Release version to 24H2.

How to get the Windows 11 2024 Update (24H2) - post #46

LarsYouPutz · Oct 5, 2024

Berton said:
Isn't Build 26100 still in the Insider Preview area?

I just did a fresh build install on 10/2 and I'm seeing a build 26100.1882
I'm not part of the Insider Preview Program.

JJVilzu · Oct 9, 2024

In admin PowerShell type in:
Set-SmbClientConfiguration -RequireSecuritySignature $false

It is the SMB sign in that is on by default on 24H2.
Check here:
SMB signing required by default in Windows Insider

jpopcorn · Oct 9, 2024

Wolfzz said:
OK with 24H2 Pro 26100.1742 I had this problem.
My Windows 10 Pro could access Windows 11 24H2 through my network, however Windows 11 24H2 could not access my Windows 10 Pro or any earlier versions of Windows 11 Pro Computers this only happened since I went to 24H2.
To fix this issue I did both of these changes in Local Group Policy Editor. And Now all is happy including me. I hope this helps.

Computer Configuration, Windows Settings, Local Policies, Security Options
Double click on Microsoft Network Client: Digitally sign communications (always)
Double click on Microsoft Network Client: Digitally sign communications (if server agrees)
Set both of these to "Disabled"
Click on OK.

Computer Configuration, Administrative Templates, Network, Lanman Workstation
Double click on "Enable Insecure Guest Logons"
Set this to "Enabled"
Click on OK.

Thank you! After many hours of the usual stuff, this worked for me. Great info!

JJVilzu · Oct 10, 2024

JJVilzu said:
In admin PowerShell type in:
Set-SmbClientConfiguration -RequireSecuritySignature $false

It is the SMB sign in that is on by default on 24H2.
Check here:
SMB signing required by default in Windows Insider

And by the way, this also works on Home versions which do not have the Policy Editor thus the ability to edit all policies is not available. Changing false to true turn on the SMB sign on again.

flhthemi · Oct 10, 2024

Could any of these settings you all have mentioned be the reason why ONE NAS in my network is not showing up in the workgroup but I can access it via \\NASNAME? I just added it to the Quick Menu as a temp workaround. It's an old Zyxel NAS520. It is using a password/user name.

I tried Bree's suggestion in post#2 - No joy there.

I tried Wolfzz suggestions in post#5 - No joy there either

And now I've noticed, prior to these attempts, this PC isn't showing and none of the other 24H2 are either. What the heck!
You know MS really has made a mess out of networking for the average Joe.

OAT · Oct 10, 2024

flhthemi said:
Could any of these settings you all have mentioned be the reason why ONE NAS in my network is not showing up in the workgroup but I can access it via \\NASNAME? I just added it to the Quick Menu as a temp workaround. It's an old Zyxel NAS520. It is using a password/user name.

I tried Bree's suggestion in post#2 - No joy there.
I tried Wolfzz suggestions in post#5 - No joy there either

And now I've noticed, prior to these attempts, this PC isn't showing and none of the other 24H2 are either. What the heck!
You know MS really has made a mess out of networking for the average Joe.

Disable firewall(s) temporarily in Private or Public whatever your case.
See if the machines are discovered that way.

flhthemi · Oct 10, 2024

OAT said:
Disable firewall(s) temporarily in Private or Public whatever your case.
See if the machines are discovered that way

Firewalls disabled made no difference. I'm at a total loss and highly frustrated by this MS. Just sayin'

Oh and these boxes are all Un-approved PCs. I used setup.exe /product server to update them. I haven't updated ANY of my legit win 11 PC's and won't until I figure this mess out.

Dru2 · Oct 10, 2024

I've not been offered 24H2 yet, but looking at this issue, glad I don't have it yet.

OAT · Oct 10, 2024

Dru2 said:
I've not been offered 24H2 yet, but looking at this issue, glad I don't have it yet.

I don't have such issues with 24H2; wished I had so I could help debug.
And I have a mixed bag of qualified and unqualified systems.

Dru2 · Oct 10, 2024

OAT said:
I don't have such issues with 24H2; wished I had so I could help debug.
And I have a mixed bag of qualified and unqualified systems.

Yeah, but I'm not looking to troubleshoot or debug anymore. Was fun when I was doing it but now zero patience for such things. In the past I would have grabbed the ISO and immediately installed it. Now I'm in no hurry to get them.

Anyway, good you and others aren't having issues as I'm well aware these things can also be system and user configuration dependent.

At any rate this was just a quick thought on my part. I have no solutions, so I'll move on.

Peace

Win11 24H2 Installed, now no network sharing

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Ret. ATC

My Computers

Well-known member

My Computers

Ret. ATC

My Computers

Well-known member

My Computers

Member

My Computer

Member

My Computer

New member

My Computer

Member

My Computer

Well-known member

My Computer

Pragmatic Member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Pragmatic Member

My Computers

Well-known member

My Computers