This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
In Win10, v 1809 I go to "Network" in file explorer and no computers are showing - neither my computer nor other computers on the network.
I was able to find the ip address of the computer I was searching for and successfully ping it via command prompt.
Any ideas?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
None of the concerns in this thread have anything to do with routers. The change was with Microsoft Windows updates and/or Windows 10 annual refreshes. I'm sure the net discovery will populate those machines but in all reality, we here are not discussing if it might be a router concern mainly because it was and has been established to be a change in windows 10. We'd be best off focusing on windows to get this concern fixed.
Hi Garth,
I think you misunderstood my intention in posting this. I'm not suggesting there is a problem with the router.
The problem we are all dealing with is the failure of recent versions of Windows 10 to see other computers on a network for the purposes of file sharing. My experiment demonstrated that a brief loss of network connectivity even though quickly restored may cause some computers on the network to no longer see others that they should be seeing. Running the task to re-start Function Discovery Resource Publication will fix it, but this only happens automatically at bootup, and if connectivity is lost for whatever reason it shouldn't be necessary to reboot all systems to restore it.
Disabling the trigger did not fix the issue here it is still broken on Windows10 2004
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.
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.
