Win11 24H2 Installed, now no network sharing

sorry if I missed this, but do you have assigned static IP's to local, or are they dhcp? I have found that trouble can be had if you assign IP's as static, even though they are suppose to work, .. just networks still get complicated..

Scannerman said:

Feel free to post your user specific thread.

Click to expand...

Thanks! I'm posting now.

retiredat44 said:

sorry if I missed this, but do you have assigned static IP's to local, or are they dhcp? I have found that trouble can be had if you assign IP's as static, even though they are suppose to work, .. just networks still get complicated..

Click to expand...

I set static IP's based on mac numbers in my router.

Tracian said:

Hi guys! As they say... you are my last hope!

Briefly put:
- I updated to 24H2. All network functionality broke
- I tried every fix known, including every single one listed in this thread. No joy....

Click to expand...

The tighter security in 24H2 is what catches most people out, particularly if you like to use local accounts with no password. See post #2

Tracian said:

.... I harbor a faint hope that 25H2 might fix this - but would it be possible to skip 24H2 at all when updating?

Click to expand...

antspants said:

25H2 will be an enablement package which I believe 24H2 needs to be installed to use. @Bree or another member may have the answer to that.

Click to expand...

Correct. 25H2 ans 24H2 share a common set of system files. The dormant 25H2 features in 24H2 will be turned on by a small enablement package.

Bree said:

The tighter security in 24H2 is what catches most people out, particularly if you like to use local accounts with no password.

Click to expand...

I might be mistaken, but as I understand it, this means that you are supposed to log in to the device you want to access. In my case, that would be the NAS (which, when working, cannot be accessed without providing its set of username/password).

Or does your statement refer to the desktop PC I am using to access the NAS? Being a home computer, I access it as admin without having to provide a full login every time I boot it up. Please don't tell me that this entire ballyhoo is about forcing every single user on the planet to type a password whenever they use a device...!

Tracian said:

...as I understand it, this means that you are supposed to log in to the device you want to access. In my case, that would be the NAS (which, when working, cannot be accessed without providing its set of username/password).

Or does your statement refer to the desktop PC I am using to access the NAS? Being a home computer, I access it as admin without having to provide a full login every time I boot it up.

Click to expand...

Sound like you use a local account on the desktop PC that has no password. When Windows tries to connect to a network device it will initially try with the name and password that you are signed in with. If that is rejected by the device you are connecting to you'll be challenged to provide name/password credentials that the device will accept.

Starting with Windows 11 24H2 by default it will not let you use a insecure connection, incoming or outgoing. An account with a blank password will not be allowed to connect to a network device like your NAS. This means you'll never get as far as being challenged for the NAS name/password.

You could just give your account on the PC a password. But if you want to keep using your PC's account without a password, then the alternative is to use the Credential Manager to add a Windows Credential with name and password to use when connecting to the NAS. Windows will now use this to connect to the NAS, rather than trying (and failing) to use your signed in account that has no password.

Bree said:

the alternative is to use the Credential Manager to add a Windows Credential with name and password to use when connecting to the NAS. Windows will now use this to connect to the NAS, rather than trying (and failing) to use your signed in account that has no password.

Click to expand...

This sounds sensible! Just one snag, though... How do I even do that? Can you please point me to a tutorial?

Bree said:

You could just give your account on the PC a password. But if you want to keep using your PC's account without a password, then the alternative is to use the Credential Manager to add a Windows Credential with name and password to use when connecting to the NAS. Windows will now use this to connect to the NAS, rather than trying (and failing) to use your signed in account that has no password.

Click to expand...

All my systems have password protected account, i get the password challenge, enter the details and then rinse and repeat.

Tracian said:

This sounds sensible! Just one snag, though... How do I even do that? Can you please point me to a tutorial?

Click to expand...

Credential Manager is in the Control Panel. You could just click Start and type credential manager to find and open it.

In Credential Manger click on 'Windows Credentials', then click 'Add a Windows credential'.



Fill in the details, server, username, and password, then click OK.

Bree said:

Credential Manager is in the Control Panel. You could just click Start and type credential manager to find and open it.

In Credential Manger click on 'Windows Credentials', then click 'Add a Windows credential'.

View attachment 144397

Fill in the details, server, username, and password, then click OK.

View attachment 144398

Click to expand...

Thanks! Please allow me just one more stupid question: what am I supposed to enter in the first field, given that I have nothing like that set up?


[Edit] - I did set up a password, restarted the PC, entered the password, logged in correctly. ...but while the NAS is seen among the connected items (as it was before), clicking on it just sends Explorer in a long search ending with a "device not found" error. Clicking on diagnostics provides a "Predefined gateway not available" message. (I'm translating the error messages from Italian, so they might not be completely accurate).

Tracian said:

Thanks! Please allow me just one more stupid question: what am I supposed to enter in the first field....

Click to expand...

That should be the network name of the NAS as you see it in File Explorer, preceded by \\

like this: \\My-NAS-name

one more victim of the 24H2 abrupt changes... except, my local accounts do have passwords - yet they are being rejected.
I have 3 machines: 2 x win11 24H2 home, one win10 home. all of the machines have the same local user with the same password locally.

The win10 user can access both win11 drives with no issues.
The win11 machines refuse to map each other's drives. (i've tried everything in this thread - and more!) when I type the \\nameofpc i get asked for a username/password and althought i enter the correct name - it says password is not correct. (i even tried ./username and machine\username)

I created new users with password on each computer, and same behaviour.

I did not make any registry editor changes (but all the private/public netowrk, allow no password, SMB on, credentials reset has been tried)

being a home edition, i don't have access to the groups.

thoughts?

priior said:

one more victim of the 24H2 abrupt changes...

Click to expand...

Welcome to Eleven Forum.

Turn off Password Protected Sharing on each machine.

Thank you for the welcome :)

I wish it was that simple!

This issue is all over the internet. I appreciate Bree's suggestions and help but none of these actually work. So I went on a long hunt through the net to glean information. (I'm trying to get 26100.5074 to behave itself. 26100.4946 is ok for the update I received).

The best analysis I've found doing that is the fault appears to lie in 24H2's miscoded inability to "pass on" the IP addresses dynamically assigned by the DHCP function in the home network router. So irrespective of whether "insecure guest logon" is enabled, or whether the nitpicky "credentials" have been assigned, logging onto a machine on one's network is hit and miss. That information came from a particularly annoyed network administrator about 5 weeks ago - her final comment was she had retreated to 23H2 untill MS fixed this.

Now I'm experimenting with static versus dynamic network assignments. The issue with static addresses is that if one of the machines on the network is turned off, that IP address becomes vacant and the Master Browser may reallocate what it sees as a vacancy. Avoiding this then requires static allocation by MAC address. Well, we'll see, I suppose.

Still, there is one fact I've encountered in this mess that absolutely flummoxes all these ifs and buts. Using 26100.5074 on 2 machines in a 3 machine network, without "insecure logons" enabled, or network "credentials" assigned, sure results in both machines seeing each other but refusing to talk; both machines, however, have no trouble at all in talking with a 3rd networked machine on Win11 Lite. Nor does the Lite machine have any trouble in talking to both the 24H2 machines. That's with standard DHCP allocation from the router. I'm yet to try static IP address allocations with this.

Perhaps all this helps someone.

After more days (and nights) of attempting everything and their dog, I came to the conclusion that my specific issue isn't even rooted in authentication, but in network discoverability issues: no matter what, the Network Discoverability toggle reverts to off as soon as I close the relevant Options panel

Of course I tried following every tutorial I could find about that specific matter, but once again... no joy at all. If you have any fix that you think might work (short of changing OS, factory reinstalling, and similarly humorous suggestions), I'm all ears.

Tracian said:

After more days (and nights) of attempting everything and their dog, I came to the conclusion that my specific issue isn't even rooted in authentication, but in network discoverability issues: no matter what, the Network Discoverability toggle reverts to off as soon as I close the relevant Options panel

Of course I tried following every tutorial I could find about that specific matter, but once again... no joy at all. If you have any fix that you think might work (short of changing OS, factory reinstalling, and similarly humorous suggestions), I'm all ears.

Click to expand...

I suppose you could always test it with a fresh install on a fresh drive. I could be entirely mistaken but I keep thinking it might be a third party thing such as your router settings or switch settings or something of that nature. This is not to say that I haven't encountered this issue before with Windows. I still have PCs that refuse to see other PCs for no discernible reason but I have so many PCs that I use the ones that "see" each other for networking. Sometimes certain security suites also interfere with networking.

Scannerman said:

I suppose you could always test it with a fresh install on a fresh drive. I could be entirely mistaken but I keep thinking it might be a third party thing such as your router settings or switch settings or something of that nature. This is not to say that I haven't encountered this issue before with Windows. I still have PCs that refuse to see other PCs for no discernible reason but I have so many PCs that I use the ones that "see" each other for networking. Sometimes certain security suites also interfere with networking.

Click to expand...

I see your point, but:
- The system worked fine with all of its software before 24H2
- Any security suite, VPN, router, etc. is there for a reason. I'm pretty sure Windows would work wonders by itself, but the fact of the matter is that it must work along with all its nice little helpers

Tracian said:

I see your point, but:
- The system worked fine with all of its software before 24H2
- Any security suite, VPN, router, etc. is there for a reason. I'm pretty sure Windows would work wonders by itself, but the fact of the matter is that it must work along with all its nice little helpers

Click to expand...

I hear you but for as long as I've used Windows (admittedly this only goes as far back as Windows 95) every time a new OS comes onto the scene issues with networking make an appearance. It can be any number of variables. So yes, one might say we're shooting in the dark but this is part and parcel where trouble shooting is involved. Sometimes we find what went sideways, other times Microsoft fixes it with an update, and sadly, sometimes we are left in the dark. Myself, I'd try a fresh install because it doesn't take long to install an operating system these days. Of course I wouldn't destroy what I have already installed but to test the problem I'd install on a fresh drive.

What I find especially frustrating is that my wife has her OS installed with a MS account as opposed to a local account and she can network practically all the PCs in the house. I can't do this with a local account. Not sure why this should be the case but fortunately the PCs I need to network with I can access (so far).

Scannerman said:

I hear you but for as long as I've used Windows (admittedly this only goes as far back as Windows 95) every time a new OS comes onto the scene issues with networking make an appearance. It can be any number of variables. So yes, one might say we're shooting in the dark but this is part and parcel where trouble shooting is involved. Sometimes we find what went sideways, other times Microsoft fixes it with an update, and sadly, sometimes we are left in the dark. Myself, I'd try a fresh install because it doesn't take long to install an operating system these days. Of course I wouldn't destroy what I have already installed but to test the problem I'd install on a fresh drive.

What I find especially frustrating is that my wife has her OS installed with a MS account as opposed to a local account and she can network practically all the PCs in the house. I can't do this with a local account. Not sure why this should be the case but fortunately the PCs I need to network with I can access (so far).

Click to expand...

But I don't need a test to know that on a clean system it is going to work! Of course millions of people have perfectly working setups... it's my particular hardware and software configuration that borks it all (and / or the downgrade from 24 to 23 leaving stuff behind) - so even if I lost one week to reinstall and reconfigure it all, I'd only come back to this unworking combination. My point is to find a fix for this specific configuration.