Windows 10, Version 1809. Network does not show computers

I wonder what makes the adapter (some, not others) not be up and ready. Actually, I have the problem on WIFI, too. I just had NB2 boot with ETH disabled and use WIFI, and I can browse to and access NB1, but NB2 doesn't show up on Network explorer, until I restart publishing service.

Also wonder what in RDP makes the problem go away. Could lead to some other solution. I may upgrade to Win Pro, although not just for this.

I will look into adding Task Manager job, too.

Thanks, fg.

@IvanTorres,

Yes the problem is a timing problem, when the FDResPub service is started up before the Ethernet network adapter is up and ready. It only fails with some Ethernet adapters but not all.

Since you have a Windows Home Version restarting FDResPub is the best option since you cannot enable Remote Desktop.

If you scroll up in this thread at the top of page 18 there is an example of how to set up the task to restart FDResPub automatically with Task Scheduler, no need for a batch file, just the command directly into the created task.

Regards.

@IvanTorres,

Hi Ivan,

Depending on the router you could have 2 different network names for Ethernet and Wi-Fi 2.4Ghz and a different name for Wi-Fi 5Ghz.

That is not the cause of the problem you are having with ethernet.

This is a bug that has been going on an off for quite a long time with different versions of windows and needs to be properly fixed by Microsoft.

In the mean time there are a couple of different workarounds described in this thread.

What version and Build of windows is on your 2 machines ?

What is Brand and type of router you are using ?

Perhaps your laptop is connecting to Wi-Fi 5Ghz while the Desktop connects to Wi-Fi 2.4 and that could explain the 2 different network names.

Hello,

Thanks for your reply, sg.

Windows builds.
NB1 - Edition Windows 10 Pro

Version 2004

OS build 19041.804
NB2 - Edition Windows 10 Home

Version 20H2

OS build 19042.804
This NB2 on Win Home is the one with the problem. I've always used Win Pro, but this one is a recently bought gaming laptop that didn't have a Win Pro option (and may not be good for gaming if it activates more services and processes). I haven't upgraded since don't need it that badly. (Using Chrome Remote instead of RDP) If upgrading guaranteed solving this problem, I might think about it, but gaming might be impacted.

My router has only 2.4 GHz - Technicolor MediaAccess TG788v v3.
About Network names, I was referring to "Network Location" that can be displayed on network device browsing, not Access Point or SSID. This is what Windows apparently calls network profiles, which they initially name based on the SSID apparently. However, when you connect later through ETH IIRC it doesn't reuse the same "Network Location"/profile and asks for a different name (confusing). At that point I probably just named that profile "Network 2". I changed that yesterday using local sec policy on Win Pro, but I see it doesn't affect the problem.

It seems there's a timing problem on startup of FDResPub. On booting, all needed services are running but the NB2 machine doesn't show on network. If the FDResPub is restarted, NB2 shows immediately. Furthermore, NB1 can be shut down and rebooted following day and NB2 is still discovered given FDResPub restart.

As of now, my workaround is a shortcut to a batch file for restarting FDResPub when I need to have both machines see each other. I could improve this by setting up running the batch on startup (easier) or using Task Manager. There may be a way to fix the timing, but I haven't looked much into service startup triggers, delayed starts, etc. All relevant services are on automatic start and running.

@IvanTorres,

Hi Ivan,

Depending on the router you could have 2 different network names for Ethernet and Wi-Fi 2.4Ghz and a different name for Wi-Fi 5Ghz.

That is not the cause of the problem you are having with ethernet.

This is a bug that has been going on an off for quite a long time with different versions of windows and needs to be properly fixed by Microsoft.

In the mean time there are a couple of different workarounds described in this thread.

What version and Build of windows is on your 2 machines ?

What is Brand and type of router you are using ?

Perhaps your laptop is connecting to Wi-Fi 5Ghz while the Desktop connects to Wi-Fi 2.4 and that could explain the 2 different network names.

"Anyway, workaround is restarting FDRP service if PC2 on ETH, or switching it to WIFI."

Another workaround mentioned by fg2001 in this thread is to Enable remote desktop connections.