Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jmone]

My "MAIN" PC went to Win11 24H2 a few weeks ago.  Then at some point after this, all my other PC's (Win11 but not 24H2) could no longer access my "Media" share.  In their explorer you can see "Main" but if you click on it then you end up with an error saying "Main" did not respond. 

I've no idea what changed, but have tried:
- Deleting / Adding Shares
- Turning On / Off Windows Defender (no other AV SW is installed) ...this one is for JimH
- I've worked through all the various "fixs" in this thread - https://answers.microsoft.com/en-us/windowsclient/forum/all/windows-11-update-24h2-changes-network-access/e54c583a-7f60-4b84-a7f7-ae2dcafbc85a but nothing makes any difference.

Any other suggestions would be welcome.  No idea what MS have done.  Worked great for a decade +. 

Thanks
Nathan

[jmone]

I should say, it's the worlds simplest "share" with the "everyone" group added (and tried both "read only" and "full access").

[jmone]

...also lost the ability to scan (from a MFD) to a SMB share.

[jmone]

...ahhh, I 'think' it's "mostly" fixed?!?  Not sure why or how.  Twiddled some more settings but nothing too obvious.  Scanner now works, so does as couple of MC Clients.  One is complaining about the "reference account is locked out".  Need to check a couple of others.

How hard can it be to just "share" a folder these days?

[zybex]

This happened to me recently too. I found out the cause was a new network policy setting added by a Windows Update called "Enable insecure guest logons". I had to enable it manually using GPEdit, then it worked again (I use guest/anonymous shares at home).

gpedit.msc:
Computer > Software > Admin Templates > Network > Lanman Workstation > Enable insecure guest logons    [enable]

Also check these:
Computer > Software > Windows > Security > Local Policies > Security Options >
> Network access: Restrict anonymous access to Named Pipes and Shares      [disable]
> Network access: Let Everyone permissions apply to anonymous users          [enable]

Also, make sure your network is still set as "private/home" as Windows sometimes sets it back to Public, causing the firewall to block access to shares.

[jmone]

Thanks, got most of those set, one Q:

Restrict anonymous access to Named Pipes and Shares : Should that be "enabled" or "disabled"?

[zybex]

Disabled.

[Manfred]

Also, make sure your network is still set as "private/home" as Windows sometimes sets it back to Public, causing the firewall to block access to shares.

I had the same problem last year. zybex named root cause also fixed it on my side.

[jmone]

Thanks zybex!  Seems to be up and working again.

@Manfred, yup all were set to private (first thing I checked).  Zybex is right, it is how the latest clamp down has impacted the shares as my "MC Clients" range from dedicated HTPC's to "normal" pc/laptops.  I have a range of MS Accounts, Local Accounts, Pins, Passwords, Autologon across these devices.  Windows 11 24H2 was clearly not happy letting these sort of devices access to the share even if it was set to "everyone".

I miss the simple "Homegroup" days of sharing.

[Richard Martin]

This happened to me recently too. I found out the cause was a new network policy setting added by a Windows Update called "Enable insecure guest logons". I had to enable it manually using GPEdit, then it worked again (I use guest/anonymous shares at home).

gpedit.msc:
Computer > Software > Admin Templates > Network > Lanman Workstation > Enable insecure guest logons    [enable]

Also check these:
Computer > Software > Windows > Security > Local Policies > Security Options >
> Network access: Restrict anonymous access to Named Pipes and Shares      [disable]
> Network access: Let Everyone permissions apply to anonymous users          [enable]

Also, make sure your network is still set as "private/home" as Windows sometimes sets it back to Public, causing the firewall to block access to shares.

Lanman takes me back 30 years to the days when Microsoft bought 3Com's networking software, 3Com 3 Open Plus and renamed it Lan Manager.