Windows 10, Version 1809. Network does not show computers

Running the test batchfile in an elevated CMD prompt on an offending computer to show up in the network then it disappears 20 to 30 minutes later.

Router has been powered off and recently upgraded. This issue has been ongoing since SMB 1.0 was deprecated due to security issues and as someone else indicated activating Remote Access is also a security issue which had gapping holes that MS patched recently

I've been using the workaround to restart FDResPub for 3 years from v 1809 and up now v 20H2 and also insider builds 20251.1 , no SMB of any type is running, sharing and discovery enabled on private network,  it works fine on my 6 computers.

If the network drops it could be when the computers go to sleep and comes back,  a second condition has been added in the task scheduler for that situation.

Here are the settings I use on the machines that are exhibiting the problem. 

Edit:

Note that to avoid the Credential Manager problem that clears the credentials after a reboot you should use a user password to start the task, leave "Do not store password" option unchecked and enter the password when asked.

This new problem about Credential Manager clearing credentials on reboot showed up recently with latest Cumulative updates of windows 2004 and 20H2. 

(I got the Credential issue with build 19042.685 and I unchecked "Do not store password" option to avoid the problem)

Running the test batchfile in an elevated CMD prompt on an offending computer to show up in the network then it disappears 20 to 30 minutes later.

Router has been powered off and recently upgraded. This issue has been ongoing since SMB 1.0 was deprecated due to security issues and as someone else indicated activating Remote Access is also a security issue which had gapping holes that MS patched recently

The only thing that I can think of is to turn the network discovery service off manually then to restart in manually.

One last effort would be to clear the network map on your router. This will clear up conflicts or mismatched ip addresses and computer names. (For most people, they will have have to reset the router.)

Tried that script months ago and does not fix the issue between a 2004 and 20H2 machine. Neither are visible to the other. Have to use \computername. in Windows file explorer to see the shares on either machine.

I am not sure what you are referring to regarding disabling the trigger. The script type of command that I put in Task Scheduler turns functional discovery off then back on.

I have some machines that run 2004 that are happy with this solution.

Try this with NO modifications.

Start the offending computer and check for misbehavior. then run the following as a command script or just do so at an ELEVATED prompt.

@echo off

cmd /c net stop FDResPub

cmd /c net start FDResPub

If the above works then your machine is unhappy with Discovery Function. Some put this script to be run at startup.  The problem is that it must be located in the directory that you specify and not be moved or deleted. To get around that limitation, the following is put into Task Scheduler directly.

And, this can be achieved without a script file by defining the task as follows in Task Scheduler:

Name:  FDResPub

Description:  Restart the FDResPub service.

Run whether user is logged on or not - Do not store password.

Configure for:  Windows 10

Trigger:  At Startup

Actions:  (here is the magic for no script)

    - Action:  Start a program

    - Program/script:  cmd

    - Add arguments:  /c net stop FDResPub && net start FDResPub

    - Start in:  (leave empty)

Conditions:  start only if the following network connection is available - Any connection

Settings:  (leave defaults)

Hope it works for you like it did for me.