Lost network with W11 24H2 install

Perhaps unwisely(!) I have just upgraded a W10 laptop to W11.. While the W10 machine can see my other W10 laptop there is no sign of the W11 machine and "network path cannot be found".

Tried all know fixes including several network resets. Even the wifi on the W11 machine seems unreliable.

System details added. I have seen elsewhere that 24H2 can cause issues with networking. Sadly none of the tutorials (if that is what you mean by 'search'?) actually helped.

What is stumping me is that the laptop was fully visible and accessible when running W10 but my W10 desktop cannot resolve the W11 laptop at all. On the occasions that I have had a 'glimpse' of it in the network (generally after a network reset) the network path has been unobtainable. I have even tried the 'fix' on here in GpPol to no avail.

Hoping someone here understands the vagaries of networking in Windows.

Do this on all systems in network..

add "LanmanWorkstation" as an additional startup dependency for the "Function Discovery Resource Publication" (FDResPub) service, which seems to do the trick. To do this, you simply open an elevated command prompt (i.e. use the "run as administrator" right-click context menu option to start cmd.exe), then execute the following command:
sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation
Restart

Make sure these services are set to automatic and running

DNS-Client – Server
Function Discovery Provider Host
Function Discovery Resource Publication
SSDP Discovery
UPNP Device Host
Windows Defender Firewall

All done, thanks, glas, and 'success' with the script, but so far sadly no improvement.

Press the Windows and "R" keys simultaneously, type or paste
"msdt /id NetworkDiagnosticsInbound" into the "Open" box and click "OK".

Ben

Microsoft has never mastered file sharing. When it works, it works, but when it doesn't what works for one does not work for the next guy.
Try this one then. It's copied from @Brink's tutorial. Share Files and Folders Over a Network in Windows 10

Enable SMB Direct on each computer you want to share between. If you have an older USB network drive or connecting to a previous version of Windows (ex: "Windows 7") than Windows 10, then you will need to enable SMB1. (see screenshot below)
SMB Direct will not be available in the Windows 10 Home edition. You will need to enable SMB1 instead.

If you enable SMB1, be sure to uncheck Automatic Removal.
It is recommended you do not enable SMB1 unless absolutely necessary for security reasons.

If you enable SMB1, it will also enable and have the Computer Browser service to run which could potentially cause 10 minutes + delay in discovering a PC newly connected to the network.




Still no joy, as a workaround, see if you can access the 11 computer using computer name. If you can, you can create a shortcut and pin it to quick access.

• Open File Explorer.
• In the address bar, type the following: \\computername (replace "computername" with the name of the computer you're connecting to).
• Press Enter.
• Note: You can also use ip address in address bar
• Whichever of these methods allows you to get to the other machine, create a shortcut to it on desktop, and pin that shortcut to quick access. You can then delete the shortcut from desktop.

SMB Direct requires a server on the other end (or the Pro edition for Workstations). It also requires a network adapter with RDMA.

It does nothing for you on a home network, unless you have a Windows Server OS or Pro for Workstations.

The OP may also try to enable "Allow Insecure Guest Authentication" in his PCs and see if he has connection to other PCs in his home network.

This web site also advises to make changes to Insecure Guest Authentication for Windows 11 and Windows 10 PCs not seeing each other on the network.