Windows 10, Version 1809. Network does not show computers

I hadn't paid much attention to this, since I seldom had two machines up at the same time. So, I only tried booting to use WIFI this once for testing. After the Auto delayed start, it worked fine on WIFI.

I wonder if having a "very fast" i7 CPU makes some initialization processes finish faster than planned and messes up the timing. On the other hand, wouldn't a Resource Publishing service broadcast or update every once in a while, in case of local changes and new hosts coming on? Since service is running it would update at some point again.

@IvanTorres,

The fastest machine I have has i9 Processors and yes it fails easier on that one, it is a time race between the network adapter being up and ready and when the FDResPub is started, unfortunately it only tries to publish the computer name and resources when it first start up. So if it fails the 1st time that is it, it doesn't seem to have any retry built in, and that seems silly. Anyway that is why restarting that service at start up or when the computer wakes up fixes the problem.

There was another workaround by eliminating the trigger and changing the start of the service to automatic.

But this workaround works fine for me, I've been using it for a long time. Also I don't have this problem with Windows insider Build 21322.1000, at least not now, but this problem has been changing on and off with various Windows Builds. :-(.

Your W-Fi adapter seems to be one that supports both 2.4 and 5Ghz going to speeds up to 1.5Gbit, but you would need a similar compatible adapter on the router. What about your Ethernet adapter Brand and Driver ?

Intel® Wi-Fi 6 AX201 (Gig+) Product Specifications

I hadn't paid much attention to this, since I seldom had two machines up at the same time. So, I only tried booting to use WIFI this once for testing. After the Auto delayed start, it worked fine on WIFI.

I wonder if having a "very fast" i7 CPU makes some initialization processes finish faster than planned and messes up the timing. On the other hand, wouldn't a Resource Publishing service broadcast or update every once in a while, in case of local changes and new hosts coming on? Since service is running it would update at some point again.

Had problem on WIFI too, changing "Function Discovery Provider Host" and "Function Discovery Resource Publication" Startup Type to "Automatic (Delayed Start)" fixed problem on WIFI, but not on ETH.

Implemented Task Scheduler Job as described on p18, reboot and problem gone. Expect it will stay gone.

Thanks.

Glad it worked for you too.

In my case I've never seen this happening with Wi-Fi, but I think some other users reported it also with Wi-Fi.

It is really a timing issue. The problem with Delayed Start is that you cannot specify how much to delay :-)

What is the Brand and model of the Wi-Fi card ? And what is the driver level and date ?

Had problem on WIFI too, changing "Function Discovery Provider Host" and "Function Discovery Resource Publication" Startup Type to "Automatic (Delayed Start)" fixed problem on WIFI, but not on ETH.

Implemented Task Scheduler Job as described on p18, reboot and problem gone. Expect it will stay gone.

Thanks.

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.