New
#171
Well, major disappointment. What I thought had finally fixed the problem turns out not to be so! Had I had time to test things out I would have discovered this fact prior to my posting. No joy, network discovery is still broken. Sure hope that MS will release a fix for this soon, I've had enough already!!!
Understand your disappointment!
We just have to wait for a MS fix. NETBIOS is just not running and that is what is in use in the Insider builds.
I hear ya there! The whole thing just really is uncalled for! I see this type of oversight or shortcoming in a lot of programming this day and age! Shameful really!
After much trial and error, I finally found a method of trial and success. I tried all solutions offered on this thread, to no avail. So I tried a few out-of-the box options and found one that seems to be working!!!
We have 10 computers in our office, 8 running Win10 and 2 running Win7, on the same Homegroup. All of the Win7 computers could see ALL of the other computers on the network, no problem. But ALL of the Win10 computers could not see all of the other Win10 computers. How to fix this?
The default in Win10 is to have NETBIOS turned off (or set to auto, which is basically off). The trick appears to be turning that NETBIOS setting on. Here are the steps of what I did, on my network, to get Win10 machines to be able to see each other on the NETWORK tab in File Explorer:
1- Click the Start Menu or Cortana search and type "network." (Or Click on Settings -> Network&Internet)
2- Select Network and Sharing Center when it appears.
3- Click on Change Adapter Settings in the left pane.
4- Right-click on your Ethernet/Wireless adapter and select Properties.
5- Select the TCP/IP v4 protocol and click Properties.
6- Click the Advanced button.
7- Click the WINS tab and check the box Enable NetBIOS over TCP/IP.
8- Click OK.
9- Click OK.
10- Click Close.
I did the above steps on EVERY one of the Win10 computers and then powered it off. After all computers were changed and powered down, I rebooted the main computer that the Homegroup was originally set up on first. Then I rebooted each other computers and voila... I can now see each and every Win10 computer from any other computer.
Hope this helps some of you!
But, that is only a part solution for many networks. Nowadays there are many NAS, and other LInux devices, that don't show with the forced NetBIOS setting.
I have an interesting puzzle. All of my Win10 computers (all running the same version) except one will not display a Linux NAS on my network. The one computer that *does* display the NAS also displays a tsclient as well. Are these two things linked? Especially as, I understand, the tsclient is a Unix thing to do with remote access. Can anyone shed more light on this?
David