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.
If computer discovery is not on turn it on. Can also try turning it off with and without reboots along the way. Try \computer name and try ip address \192.168.1.xxx in explorer to see if it can be see anyway.
MS is ignoring the elephant in the room.
@CSMAD, @Scottisrael,
Using the computer name or the IP address was yet another of the listed workarounds for the problem, but it is just another workaround not the fix of the root cause of the bug that MS is failing to address and correct.
If computer discovery is not on turn it on. Can also try turning it off with and without reboots along the way. Try \computer name and try ip address \192.168.1.xxx in explorer to see if it can be see anyway.
MS is ignoring the elephant in the room.
I was able to see the Public and Default user folders using either technique on the main PC.
I then went to the second PC I hoped to access, and shared the documents folder for one of the users on that PC, giving read/write access to "Everyone". This made all of that user's folders visible.
Any risk if computer discovery set only for Private network?
If computer discovery is not on turn it on. Can also try turning it off with and without reboots along the way. Try \computer name and try ip address \192.168.1.xxx in explorer to see if it can be see anyway.
MS is ignoring the elephant in the room.
In the task scheduler, you can have functional discovery stop and restart with multiple triggers which may mitigate the problem.
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.
@johnb3030,
It looks to me the FDResPub only publishes the resources once when it starts up, even if the service is up and running it does not keep refreshing and it does not rediscover the computer unless the service is restarted.
The computers fail to show up if FDResPub starts up before the network is ready, by restarting the service again later it fixes the problem temporarily, if you lose the network FDResPub will need to restart to publish the computer again. It looks to me that there is no automatic recovery for this service.
This bug has been going on for a long time starting with V 1809, but MS seems to be ignoring it and it is still an unresolved issue even with the latest Development builds.
