24H2 Networking broken again on 21600.2454

Hi folks
Can access Internet etc on this release but no machines on my LAN can now see this machine,. as well as mobile phone and 3 X remote TV's with amazon firesticks so can't get to multimedia content from this machine.

Done all the right things --same LAN subnet, etc. Tested also with all firewalls off, minimum security etc etc -- still no joy.

Never mind about Black Friday -- Windows Networking still seems to operate on Black Magic.

The 100% Bonkers thing is that if I run a HYPER-V Linux VM on this system - the VM can be seen and accessed everywhere including those firesticks on remote TV's but still no sight of the Windows Host. Even on HYPER-V GUEST/HOST communication only works one way !!!

Something is really hosed up -- previous release was working perfectly --- and this release is meant to be the nearest thing to a definitive RTM.

Cheers
jimbo

Sorry to hear that Jimbo
I have updated lately a Asus Intel Notebook and did a fresh ISO install on a Intel Nuc 11 and they are both running 21600.2454.
The only thing I did was to make sure they both had SMB 1.0/CIFS File Sharing Support and SMB Direct both fully ticked in Turn Windows features on of off. And of course made sure all the sharing options were on except turn off password protected sharing.
Which I always have done in the past for all Win 10 and earlier Win 11 Computers but now since 24H2 I've had to do this

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.

And all is working fine networking both ways on a Private Network including access to my NAS's

Good Luck

Wolfzz said:

Sorry to hear that Jimbo
I have updated lately a Asus Intel Notebook and did a fresh ISO install on a Intel Nuc 11 and they are both running 21600.2454.
The only thing I did was to make sure they both had SMB 1.0/CIFS File Sharing Support and SMB Direct both fully ticked in Turn Windows features on of off. And of course made sure all the sharing options were on except turn off password protected sharing.
Which I always have done in the past for all Win 10 and earlier Win 11 Computers but now since 24H2 I've had to do this

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.

And all is working fine networking both ways on a Private Network including access to my NAS's

Good Luck

Click to expand...

Hi there
I really don't want SMB1 any more -- and the NAS's I have (running Linux Fedora 41 and Arch Linux) have more or less deprecated SMB1 on SAMBA. On the firesticks I have which I plug into remote TV's (I've sideloaded Kodi on them) I also have minimum protocol to SMBV2.

Global part for SAMBA on my NAS's
#GNU nano 8.1

[global]
workgroup = VIKINGURS
security = user
# server min protocol = NT1
passdb backend = tdbsam
printing = cups
printcap name = cups
load printers = yes
cups options = raw


I suspect there's some new obscure setting in the firewall rules or whatever that have changed and need to be set properly.

(For SMB1 in SAMBA on current Linux versions -- kernel 6.11.XX you need to set min protocol to NT1 but that's being deprecated soon - plus getting name via NETBIOS (parameter is NETBIOSNAME = computer name - but it's not supported either now).

I agree if you need to share with older gear, Win 7, XP or whatever then you still need SMB1 but not really on modern gear any more.

On previous Windows release - worked perfectly e.g :



On current release -- "destination is unreachable").


(BTW on the latest Amazon firesticks to enable "Developer mode" so you can sideload non amazon sourced apps you need to get into "about my firestick, scroll to the name and press ENTER 6 times on the remote -- then the option is enabled).

Cheers
jimbo

Hi Jimbo
The only reason I enable SMB1 is that I deal with old clients computers with windows 7 and 8.1 as I need to access those computers to transfer drivers and data.
It wouldn't really matter if it is turned on or off with your issue.
I was just explaining what I do to get my network to work and so far no issues.
I've also tried it with firewall enabled and disabled which again didn't effect anything.
The only thing I've have to do now with 24H2 is with the gpedit settings to get my network to work.

Maybe check to see if the Master browser has changed. I had a power outage the other day and it changed my Master browser and hosed up the workgroup. Got it back to the usual master and now everyone shows up.

Jimbo, I didn't see you had noted this:-
Computer Configuration, Administrative Templates, Network, Lanman Workstation
Double click on "Enable Insecure Guest Logons"
Set this to "Enabled"
Click on OK.