Windows 11 cannot access other computers, but can be accessed by the other computers

eband · Sep 14, 2024

The "Windows cannot access \\NETWORKSHARE" problem has returned. I don't know how, but somehow the problem has returned in the last few days.Basically, all other computers can access this computer, but not the other around. The other computers' OSes were: Linux Mint, Windows 10 Pro, and Windows 7 Ultimate.

Here's what I tried:

Entering any and all variations of NETWORK SHARE names possible, including
- share names
- IP address
- including file folders with share names
- including file folders with IP addresses
Enabling and disabling SMB/CIFS 1.0 protocols.
Pinging the other computers; that worked, so I know the connections are right.
While isolating the Windows 11 problem, the other computers can communicate with each other. I've added this point to ensure that all other computers are still working.
Checking for allowing the insecure logins option; I initially allowed this because that's how my W11 computer can communicate with the others. That options has not changed.
Installing new drivers to ensure that things are going right. That didn't help and was a waste of time.
Adding the SMB protocols (SMB/CIF 1.0, SMB Direct)
Adding Network Discovery.
Manually specifying IP address and DNS address.
Enabling File and Print Sharing.
Setting the Network Profile to Private.
Not setting Password Protection.
What have I missed?

Since the last few days, I recall installing new Windows updates and updating my Gigabyte DS3H motherboard firmware. Also, the other computers can communicate with this computer, just not the other way around.

The last thing I'll try is to rewipe everything, but i don't want to do that just yet. That would take too much time for now, I hope to leave that for last. The error is 0x80004005. I don't know that error, but when I read online, it had something to do with Windows Updates. That has nothing to do with my problem though.

OK, that's all I can reveal for the moment. Back to bending more rules in the book.

Thank you in advance.

eband · Sep 15, 2024

UPDATE: I've tried wiping everything and starting over. That didn't work.

By the way, here's the image of the message:

eband · Sep 16, 2024

UPDATE: I tested an earlier copy of a Windows 11 copy that I customised that being made by me, containing all the updates before the one just released in a virtual machine, and that can peek inside the directories of the other computers, confirming that the Windows updates are the culprit of this mess.

I guess I'll wait for a later update.

Question: Is there a way to move back a Cumulative Update and not use the one offered this month?

eband · Sep 16, 2024

EDIT: I am using the 24H2 builds, so I guess things can be a little buggy.

glasskuter · Sep 16, 2024

Welcome to the forum. Not that my answer will help with your problem, but for me this issue has come, gone and come again for years, especially in mixed OSes. Networking and sharing is one thing that MS has never been consistent with managing.

For giggles and grins go to services. Check the following 2 services. If the services are stopped, start them. If they are started, restart them to see if it makes a difference.

eband · Sep 16, 2024

Thank you for answering. I just tried it. Didn't work.

For now, I made a virtual machine to facilitate transfers between this computer (Windows 11) and the others. It's going nicely. Hopefully after the next update, I won't need it for that.

garlin · Sep 16, 2024

eband said:
UPDATE: I tested an earlier copy of a Windows 11 copy that I customised that being made by me, containing all the updates before the one just released in a virtual machine, and that can peek inside the directories of the other computers, confirming that the Windows updates are the culprit of this mess.

I guess I'll wait for a later update.

Question: Is there a way to move back a Cumulative Update and not use the one offered this month?

CU's can only be rolled back if your install image was built by applying a newer CU, on top of an older integrated CU.

ISO's created by UUP dump, MCT or those released by MS will only have one CU applied. There's no point for them keeping different CU versions, because it will be a clean install.

In these cases, if you can't re-install then you simply wait for a later CU to fix all your problems.

eband · Sep 16, 2024

@garlin That's a good idea.

Bree · Sep 16, 2024

eband said:
Here's what I tried:

Entering any and all variations of NETWORK SHARE names possible, including

share names

IP address

including file folders with share names

including file folders with IP addresses

Enabling and disabling SMB/CIFS 1.0 protocols.

Pinging the other computers; that worked, so I know the connections are right.

While isolating the Windows 11 problem, the other computers can communicate with each other. I've added this point to ensure that all other computers are still working.

Checking for allowing the insecure logins option; I initially allowed this because that's how my W11 computer can communicate with the others. That options has not changed.

Installing new drivers to ensure that things are going right. That didn't help and was a waste of time.

Adding the SMB protocols (SMB/CIF 1.0, SMB Direct)

Adding Network Discovery.

Manually specifying IP address and DNS address.

Enabling File and Print Sharing.

Setting the Network Profile to Private.

Not setting Password Protection.

What have I missed?

eband said:
EDIT: I am using the 24H2 builds, so I guess things can be a little buggy.

I have a mixed network of Windows 10, Windows 11, and occasionally Windows 7, they can all see each other's shares. (I also have WfWG 3.11, Win'95 and XP as VMs that can go on the network too :wink:

).

I have to have the 'SMB 1.0/CIFS Client' enabled if I want to see the usb drive being shared out by my router (you don't need the CIFS Server and should not enable it, that's only necessary if you want XP to see a Win10/11 share).

For easy transfers all my PCs have a C:\Temp folder with share permissions of everyone/full control. I have also set its NTFS security to everyone/full control.

I have turned off Password Protected Sharing on all my machines.

It all seemed to work seamlessly until 24H2 came along. That introduced a further restriction (in Pro only). Windows 11 Pro 24H2 by default will not let you use an insecure login to connect to a remote share. As I generally have no password for my local accounts that caused me some grief at first.

By default, SMB signing is required on all connections. This increases your security by preventing tampering on the network and stops relay attacks that send your credentials to malicious servers.

Guest fallback is disabled on Windows 11 Pro edition. This increases your security when connecting to untrustworthy devices. Guest allows you to connect to an SMB server with no username or password. While convenient for the maker of your NAS, it means that your device can be tricked into connecting to a malicious server without prompting for credentials, then given ransomware or having your data stolen.

SMB signing has been available in Windows for 30 years but, for the first time, is now required by default on all connections. Guest has been disabled in Windows for 25 years and SMB guest fallback disabled since Windows 10 in Enterprise, Education, and Pro for Workstation editions. Both changes will make billions of devices more secure. They've been in Windows Insider Dev and Canary builds for a year.

Accessing third-party NAS with SMB in Windows 11 24H2 may fail

Storage at Microsoft Blog: Heya folks, Ned here again. With the publication of Windows 11 24H2 Release Preview, customers are trying out the new OS prior to general availability. If you were in the Windows Insider Canary or Dev release program for the past few years, nothing I'm about to share...

www.elevenforum.com

My solution was to create a new local account on each of the PCs with the shares and give it a password. On the 24H2 Pro PC that needed to connect to those shares, I set up a Windows Credential to use that account and password for connecting to each of them.

eband · Sep 16, 2024

I am sorry you have the problem too.

I can tell you that the problem didn't exist with 24H2, at least not with the 24H2 of IoT Enterprise LTSC 2024. Since the beginning of this release, which was June of this year, I was still using LAN sharing. In fact, I was still transferring files right before the update which was this past Tuesday.

Still I'll try your solution.

eband · Sep 16, 2024

@Bree What do I put for "Internet or Network Address?"

EDIT: Just tried that. That too didn't work. Here's how I did it:

Created a separate account for all intended computers.
Went to Credential Manager to enter the accounts names and passwords, along with the network names.
Restarted.
Went to a file explorer window and entered all possible combinations of reference to the the network shares.

And the message shown previously still came up.

Thank you for your suggestion anyways, @Bree.

EDIT: Here's the input:

THiBOR69 · Sep 16, 2024

Bree said:
My solution was to create a new local account on each of the PCs with the shares and give it a password. On the 24H2 Pro PC that needed to connect to those shares, I set up a Windows Credential to use that account and password for connecting to each of them.

I have done the exacte same thing that Bree has done and it worked perfectly for me on my latest 24H2 build.

Good luck !!

G0T R00T ?
su root
mv /home/root/* dev/null ( hehe.. )

eband · Sep 16, 2024

For the record all the old LAN games like Command and Conquer Red Alert 3 and Starcraft worked, so LAN functionality (and my equipment) are still competent. It's just the Windows 11 computer that's acting up.

eband · Sep 16, 2024

Anyhow, when do Cumulative Update Previews roll out? The fourth Tuesday of the month?

Maybe that'll fix it because I'm burnt out.

garlin · Sep 16, 2024

Patch Tuesday is every 2nd Tuesday, Preview Updates are every 4th Tuesday.

Bree · Sep 17, 2024

eband said:
That too didn't work. Here's how I did it:

Created a separate account for all intended computers.

Went to Credential Manager to enter the accounts names and passwords, along with the network names.

Restarted.

Went to a file explorer window and entered all possible combinations of reference to the the network shares.

And the message shown previously still came up.

Just to be certain, you made the local account/password on the PC you want to connect to, and set up the credentials to the 24H2 PC that wants to connect? If so that should have worked. By default the latest builds of 24H2 Pro will not let you make an outgoing connection without using a password (it's only in Pro, Home has no restrictions).

The alternative solution for 24H2 Pro is to turn off the SMB signing requirement in Group Policy.

Control SMB signing behavior (preview)

How to disable SMB signing on third-party servers in Windows 11 and Windows Server.

learn.microsoft.com

eband · Sep 17, 2024

About the first question: come again? I don't know what you're asking.

Each of the other computers had a unique login and password created and I included them in the Credentials Manager on my Windows 11 IoT Enterprise LTSC 2024.

By the way, I said Windows 11 IoT Enterprise LTSC 2024, not Pro. I bought it off from some guy online if you must know.

I guess it doesn't apply.

EDIT: I just saw the option anyways. Should I disable it as the instructions imply?

jimbo45 · Sep 17, 2024

Windows Networking always seems hit and miss -- There's no inherent problem with Windows iot enterprise. Try from that machine pinging the other ones and from the other ones ping the iot enterprise machine. Also check you haven't blocked "remote connections to this computer" - use control panel get to it via the windows tools and allow connections. Allow also "network discovery" also to be enabled. I suspect the problem is in File explorer -- it's getting really long in the tooth these days.If you've got the IP addresses you can add that to "favourites" to browse network. A Pain but that seems to be the most universal get around.

This networking problem seems to occur more times than there are Hot Dinners on this planet. I rarely if ever have Network problems with Linux -- works straight OOTB.

Cheers
jimbo

eband · Sep 17, 2024

Pinging works, network discovery is on. For all the things that I tried, please refer to the first message on the thread. In the TLDR description of that very post, I did almost everything that should be done when networking the computers together.

@jimbo45, I'm sorry, I'm a little slow, but how do I enable "remote connections" exactly?

EDIT: The error was the "check spelling error," meaning Windows 11 didn't recognise the network names or even the existence of the networked computers. I will show the message again:

Even though there have been no solutions that got me closer to solving, I want you guys to know that you guys rock! I didn't expect to be getting replies because on other forums, I had none. Thank you for the help and I hope I can help the community out as well.

I might sound a little obnoxious , but that was not my intention.

Thank you. I guess I'll just wait for the next update.

jimbo45 · Sep 17, 2024

eband said:
Pinging works, network discovery is on. For all the things that I tried, please refer to the first message on the thread. In the TLDR description of that very post, I did almost everything that should be done when networking the computers together.

@jimbo45, I'm sorry, I'm a little slow, but how do I enable "remote connections" exactly?

EDIT: The error was the "check spelling error," meaning Windows 11 didn't recognise the network names or even the existence of the networked computers. I will show the message again:

@eband

Cheers
jimbo

Windows 11 cannot access other computers, but can be accessed by the other computers

Member

My Computer

Member

My Computer

Member

My Computer

Member

My Computer

aka Mama Glass

My Computers

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computers

Member

My Computer

Member

My Computer

Active member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Similar threads