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.
- That's really interesting. My newer Dell desktop is connected to my Comcast gateway via LAN. But the other two, it has not mattered whether they are on WiFi or plugged in to the LAN, they still didn't see the newer Dell.
morens1345
Yes that is true, if the PC cannot see itself , it is also not visible from any other computer on the network, regardless on how the other computers are connected.
Once it is visible locally it will show also on the other PC's on the local private network.
Hi galileo1564,
Searching online I found another suggestion that seems to solve this problem in windows 10 1903 and also on the insider builds 20H1, without using the workaround to restart FDResPub, but I cannot explain why.
CharitableComputing.org
Third: Make sure you have Enable Remote Desktop enabled... even if you do not plan on accessing your computer remotely. Always remember, if you don't have a password on your account, you can't access the computer remotely anyway. This is found under Settings, then System, and finally the last choice on the bottom left.
I want to point out that with Insider builds 20H1 (currently build 19008) the bug is even more solid).
If I change the setting to Enable Remote Desktop, the problem disappears without using the workaround to restart FDResPub.
Perhaps enabling that functionality changes the time that FDResPub is started ?
I don't really know how to see what makes the difference, but It works for me on all the machines that were failing, even mixing machines running 1903 and 20H1.
Looks like magic, but would be interesting to know why it changes the behavior.
Perhaps you can try and add your comments.
Thanks.
FG
After researching this problem for some time, I believe I have pinned it down to Computer Name setting. Change your computer name to something else then reboot and change it back again (reboot again).
Solved this long-running issue for me! Give it a go.
Hi Plarini,
It has been over a year using the workaround to restart FDResPub, but today I saw another suggestion and tried it out both on v 1903 and 20H1.
See my previous reply above to Galileo.
Perhaps you may want to try it out too.
Thanks.
After researching this problem for some time, I believe I have pinned it down to Computer Name setting. Change your computer name to something else then reboot and change it back again (reboot again).
Solved this long-running issue for me! Give it a go.
skvenus99,
Changing the computer name doesn't change anything for me.
It may work the first time you change the computer name because it does a network reset.
When I change it back and reboot it fails again as usual.
Keep in mind that with 1903 the problem is intermittent, but on the same machine with Insider build 20H1 the problem is solid after each reboot.
If I Enable Remote Desktop I cannot make it fail, tried many reboots without a single error.
