Windows 11 network share not visible from other Win 11 machines <sigh>

mingle · Nov 19, 2024

Hi Guys,

Still experiencing an ongoing issue with a lack of connectivity to network shares between one Win 11 machine and a bunch of others.

The offending machine can connect to the shared drives on all of the other machines (and they can all connect to each other), but none of the others can connect to the shares on it.

I've checked the various network and sharing settings across all of the machines and they all appear to be the same. Also required services also seem to be running across all machines.

They are all running the same version of Win 11 (23H2).

The 'offending' machine is connected via wireless to the router.

Passwords disabled. SMB disabled. (tried both of these enabled and no change)

I can see the machine in Explorer (SURFACEGO2), but when I click on it, (after a 20 second delay), it displays the following error (see attached, showing the initial network error and the trouble-shooter diagnostic results).

I've checked-out a few online solutions, which are usually a bucket-full of half-arsed possibilities which I'm supposed to throw against the wall and see if any stick - they didn't!

So if anyone has any decent suggestions, that would be great.

My last option is a clean install of the OS, then rebuild my apps on top of that - obviously I'd like to avoid that if possible!

Cheers,

Mike.

hsehestedt · Nov 19, 2024

Before going into a long set of troubleshooting steps, have you tried connecting to that machine using an IP address rather than a computer name? If so, what happens?

If you need detailed directions on how to do this, let me know.

glasskuter · Nov 19, 2024

Go to Settings > Network & internet. At the top of the screen, make sure that the computer shows Private network and NOT Public network. If it shows the network to be public, click there and change it to Private.

If your wifi adapter is Intel try this Hint Our fellow member @hsehestedt posted recently to see if it helps. On systems using Intel WiFi adapters, open Device Manager and locate your WiFi adapter. Right-click that adapter and select Properties. Go to the Advanced tab. Look for a setting called Packet Coalescing. Disable that setting. This worked for me.

For what it's worth, under "windows features turn on and off", I have SMB 1.0 off, but have SMB direct turned on.

EDIT: I didn't see that @hsehestedt had come into the thread while I was writing. He's the man when it comes to networking and sharing issues.

mingle · Nov 20, 2024

hsehestedt said:
Before going into a long set of troubleshooting steps, have you tried connecting to that machine using an IP address rather than a computer name? If so, what happens?

If you need detailed directions on how to do this, let me know.

Interesting... When I connect (in Explorer's address-bar) using the IP address: "\\192.168.20.12", the two shared drives "D" and "E" appear in the main Explorer window. I can then successfully access the shares!

What gives? It's somehow not resolving the computer's network name?

<EDIT> I CAN ping the machine using the computer name (SURFACEGO2) as well as the IP address...

I hope this gives you a clue as to what's up?

Cheers,

Mike.

Win7ine · Nov 20, 2024

mingle said:
Interesting... When I connect (in Explorer's address-bar) using the IP address: "\\192.168.20.12", the two shared drives "D" and "E" appear in the main Explorer window. I can then successfully access the shares!

What gives? It's somehow not resolving the computer's network name?

<EDIT> I CAN ping the machine using the computer name (SURFACEGO2) as well as the IP address...

I hope this gives you a clue as to what's up?

Cheers,

Mike.

Did you try resetting all Networks on all machines? Check WORKGROUP Names are all the same and that all machines are not part of a business Network.

Lima · Nov 20, 2024

Firewall?

mingle · Nov 20, 2024

Thanks for the additional replies...

I know it's not the Firewall - all set the same and can connect via IP address.

I'd also prefer NOT to rest the network, as it's almost working now...

Hoping to here back from @hsehestedt, as if I can solve the issue with the computer network name, it's sorted.

Cheers,

Mike.

hdmi · Nov 21, 2024

Have you verified that these 5 services are set to autostart and are running?

DNS Client
Function Discovery Provider Host
Function Discovery Resource Publication
SSDP Discovery
UPnP Device Host

Simply run the command below in a command window to see if they are.

Code:

for %i in (Dnscache fdPHost FDResPub SSDPSRV upnphost)do @sc qc %i|findstr "SERVICE_NAME START_TYPE DISPLAY_NAME"&sc query %i|findstr STATE

Wolfzz · Nov 21, 2024

mingle said:
Hi Guys,

Still experiencing an ongoing issue with a lack of connectivity to network shares between one Win 11 machine and a bunch of others.

The offending machine can connect to the shared drives on all of the other machines (and they can all connect to each other), but none of the others can connect to the shares on it.

I've checked the various network and sharing settings across all of the machines and they all appear to be the same. Also required services also seem to be running across all machines.

They are all running the same version of Win 11 (23H2).

The 'offending' machine is connected via wireless to the router.

Passwords disabled. SMB disabled. (tried both of these enabled and no change)

I can see the machine in Explorer (SURFACEGO2), but when I click on it, (after a 20 second delay), it displays the following error (see attached, showing the initial network error and the trouble-shooter diagnostic results).

I've checked-out a few online solutions, which are usually a bucket-full of half-arsed possibilities which I'm supposed to throw against the wall and see if any stick - they didn't!

So if anyone has any decent suggestions, that would be great.

My last option is a clean install of the OS, then rebuild my apps on top of that - obviously I'd like to avoid that if possible!

Cheers,

Mike.

Have you try this as it fixed my issue

With a fresh install of 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.

mingle · Nov 21, 2024

Wolfzz said:
Have you try this as it fixed my issue

With a fresh install of 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.

Thanks for the reply... I think 24H2 introduces another set of networking stuff-ups... Thanksfully I'm still on 23H2

mingle · Nov 21, 2024

hdmi said:
Have you verified that these 5 services are set to autostart and are running?

DNS Client

Function Discovery Provider Host

Function Discovery Resource Publication

SSDP Discovery

UPnP Device Host

Simply run the command below in a command window to see if they are.

Code:

for %i in (Dnscache fdPHost FDResPub SSDPSRV upnphost)do @sc qc %i|findstr "SERVICE_NAME START_TYPE DISPLAY_NAME"&sc query %i|findstr STATE

All services are running (on all systems), apart from upnphost (again, on all systems), so I don't think that's the issue.

fixer · Nov 21, 2024

If this machine is normally logged into using a PIN rather than a password, try logging in using its password. If that is successful it only has to be done once.

ChrisPbass · Nov 21, 2024

mingle said:
Hi Guys,

Mike.

I would just like to commiserate with you. W networking is SUCH a pita because it seems like it works just fine, then it doesn't. You think you're doing something wrong or are incompetent and then, voila, the connection is back.
I have one PC on our network that just never seems to want to exist. the settings are all correct, according to this forum.
I map it. It disappears. Now I always go to the address bar and type in \\offendingPC and, voila, everything works again.

And this reminds me that I need to get a static IP for this particular PC so thanks!

hdmi · Nov 21, 2024

mingle said:
All services are running (on all systems), apart from upnphost (again, on all systems), so I don't think that's the issue.

While it certainly is true that the UPnP Device Host service doesn't directly handle Network Neighborhood browsing, it primarily facilitates automatic device discovery and resource sharing on a network, and therefore could potentially have an impact on the functionality behind the "Set up network connected devices automatically" checkbox in Advanced sharing settings. When the UPnP Device Host service is disabled, it may prevent the system from correctly using network discovery protocols, which could interfere with the ability of Network Neighborhood to properly display and access shared resources. Here are a few reasons why this might be happening:

Device Discovery: UPnP helps in automatic device discovery. If it's disabled, devices might not appear correctly in the Network Neighborhood.
Service Dependencies: Some network discovery and resource-sharing features rely on UPnP. Disabling it might disrupt these services.
Network Configuration: Disabling UPnP can affect network configuration settings, making it harder for devices to communicate and share resources automatically.

Network Neighborhood relies heavily on network discovery protocols like WS-Discovery, NetBIOS, and SMB. If any of these protocols face issues or aren't fully supported on either end, Network Neighborhood might not function correctly. Network Neighborhood might not always refresh its network cache properly, leading to stale or missing information about available shared resources. Certain services like Function Discovery Resource Publication and SSDP Discovery play crucial roles in making devices discoverable on the network. If these services have intermittent issues, it could affect the visibility of (or the ability to access) shared folders in Network Neighborhood. Even though firewall settings might allow access through the UNC path, certain rules or profiles might still interfere with Network Neighborhood's discovery process. Network Neighborhood depends on timely responses from other devices on the network. Any delays or packet losses can cause it to fail in showing the network resources properly.

In short, even if it turns out that I was wrong about the UPnP Device Host service and how it might explain the specific problem that you are experiencing with Network Neighborhood, relying on Network Neighborhood for accessing shared resources can be hit or miss still nevertheless, due to these complexities. Using the UNC path directly tends to bypass many of these potential pitfalls, making it a more reliable method for accessing shared folders. If you don't want to map a network drive, you could always decide to add a so-called Network Location instead:

To a lot of people, the "Network Location" is that which you can change to Public or Private, but in File Explorer a "Network Location" is referring to something completely different, as Microsoft sometimes (sometimes often) likes to make things as confusing as humanly possible. Complaints about it help to sustain the need for additional bandwidth, which is always good for the economy so, I am not too worried.

Windows 11 network share not visible from other Win 11 machines <sigh>

Well-known member

Attachments

My Computer

Well-known member

My Computers

aka Mama Glass

My Computers

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Jack of all trades – master of none

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Jack of all trades – master of none

My Computers

Similar threads