Windows 10, Version 1809. Network does not show computers

Back to square one and waiting... hopefully able to get some work done in the meantime.

ms doesn't care... they are focused only on cloud computing which will eliminate the messy need for computer to computer communications.

Thanks again,

Beverly Howard

@bevhoward, 

I've been using the listed workarounds for almost 2 years now,  never have any issues.

I have 6 machine all running windows 10 Pro and they all communicate to each other fine.

Computer to computer communications is quite simple and there is no way I'll ever use the cloud to transfer or store my files. :-(

Good luck with that concept...😜

Coming over from another threadthat I started a months about the same problem.

Murphy is hard at work... making sure that no questions get answered.

Before I saw the post here about the cmd /c net stop FDResPub etc suggestion, I had gone into the Win8.1 computer's network and sharing settings, and turned ON password protected sharing for the public folders but had not had a chance to test that sitting at the win10 box.

When I got the reply pointing me at those commands, I went back in and turned OFF password protected sharing on the Win8.1 computer before I made the trek up to the Win10 computer, woke it up from sleep and clicked on the Win8.1 computer's shortcut and it connected immediately before I did anything.

As posted here, I don't expect this to last.  The varied stories posted seem to indicate that something in the Win10 computer is randomly turning off network access FROM the Win10 computer, then, when any change is made to probably any network settings, that prompts the Win10 computer to gather itself up and set things up correctly until that random event happens again....

In my case, this change, the SMB change, and a couple of other network tweaks that I have attempted have had the same (temporary) result.

Back to square one and waiting... hopefully able to get some work done in the meantime.

ms doesn't care... they are focused only on cloud computing which will eliminate the messy need for computer to computer communications.

Thanks again,

Beverly Howard

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?

Scott, 

I usually share only one folder on each computer for the purpose of transferring files when I need to from one PC to another never share any public folders or default folders.

I never grant access to "everyone"  just to a specific user(s) and all password protected.   

The more unprotected doors you leave open in your house the easier it is for burglars to get in and rob you...   😜

Who has access to your 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.

@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?