Windows 10, Version 1809. Network does not show computers

Anonymous
2018-10-19T21:34:40+00:00

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?

Windows for home | Windows 10 | Internet and connectivity

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.

0 comments

243 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-10-29T07:28:27+00:00

    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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-10-29T06:49:44+00:00

    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.

    https://answers.microsoft.com/en-us/windows/forum/all/local-network-problems-with-1903/97086935-7cfe-4227-ac7f-87ecd46ad83b

    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

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-10-28T22:04:45+00:00
    1. 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.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-10-28T21:28:21+00:00
    1. 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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-10-28T14:53:22+00:00

    I have this problem on and off since v 1809.  Now at 1903.  Problem only exists on 2-3 year old Dell desktop.  Other computers on my network are older HP desktop and older Dell laptop.  All W10 V1903.  Strangely, the problem only exists on my newer Dell desktop.  It could not see itself, but could see the other two.  The other two could see each other, but not the newer Dell.  This is a great fix!  Thank you!

    Was this answer helpful?

    0 comments