Windows 10: Can't see other computers in Workgroup on Windows 10 computer
Same problem here
Read all 11 pages of the reply so far, and no dice with anything.
- I'm on Windows 10 10586.63, shares do not show up under Network
- I can access my samba shares file servers with the //<servername> technique.
- shares do show up on the older version Windows 10 10240, including a Brother printer
- one linux server is running Samba 4.1.6
- one linux server is running Samba 4.1.19
I'll keep an eye on this thread, and look into fixes if the problem doesn't sort it self out, and continues to irritate me.
Your mention of NAS4FREE clued me into looking at my NAS4FREE box and sure enough, it had the Master Browser enabled. I disabled it and after weeks of trying all of the other "fixes" and still not being able to see my NAS boxes or other Win10 boxes, they all immediately appeared!
This solved my problems. I did this on my main computer, but it see's itself in the network which was missing and all the 4 other computers now see everyone. I set all the setting to automatic after restarting or starting. As a not someone mentioned the computername and upper and lower case. The one laptop I did this and used all lowercase. At that point in the system properties, after the computer description was chanded, the choice below it is available "To use the wizard to join a group or workplace, click Network ID". That opens a choice of This computer is part of a net business network or a home computer. This choice from business to home required a restart. But this machine is now working. Is it possible the setting were for a business setup rather then a home setup as the problem. I will never know as the above fix above did the trick for all five machines. Have not tried to reboot yet but this could be the killer. I hope not.
Function Descovery Resource Publication
On my first reply the network restored, but i didn't reboot to see if it stayed up.
After a reboot I lost my main computer on all 5 computers.
So I reversed what I did to eliminate and find the service that return the network with all computers.
Started by restarting each of the 8 choices. Only one when restarted brought the main computer back on the network.
The "Function Descovery Resource Publication" when restarted corrects the missing main computer in my setup.
I reset the 8 Services back to their normal setting found on the other 4 computer.
The "Function Descovery Resource Publication" is set as Running and Automatic as found on all my computers.
Then a reboot. Checked the Service setting and they are the same, but the main computer is missing which is the computer I'm setting up the Services on and the one not showing the complete network of 5 computers.
So the test now is restart "Function Descovery Resource Publication" to see if it returns the network on this computer to show itself in the network and also if this computer appears on the other computers sitting in the same room, all showing the Network.
I then restarted the "Function Descovery Resource Publication" and the network shows my main computer back on the network of this computer, and a quick look shows the other computers are now showing the main coumputer.
Conclusion is the "Function Descovery Resource Publication" service when restarted is theway to return the network to show all shared computers. Now we need a fix.
The fix is in 11099 it seems.
A good test of 'fixedness' is to run 'net view' in a command prompt and see whether you get error 1231. If you do, it ain't fixed.
You can be chasing your tail trying to figure some logic as the master browser always works fine so if the master browser moves from one comp to another..........
After many hours/days of searching for a solution to my issue, SMB/CIFS not showing in File Explorer views, I finally narrowed it down to the configuration of the CIFS service itself, specifically that the service was configured as being in the wrong Domain of the hosting server running the SAMBA/CIFS service even though that server was in the same domain as my Windows client machines. I have no explanation for the above being true except that in original configuration I mistakenly accepted default values when I should not have.
The Master Browser aspect being discussed here did have a significant role in this as well as I discovered in my reconfiguration of SMB/CIFS. By default SAMBA/CIFS is set as the Master Browser which in my case is correct. This is true due to the fact that my server which hosts SAMBA/CIFS is a continuous duty constant on 24/7 machine.What I discovered was that this forced election works fine with other Windows boxes that are based on Windows NT/2000/XP. During the Browser election which occurs in the subnet structure of a network were a SAMBA server exists the SAMBA server registers itself in the election with a value of 128. This is true due to administrator configuration of the server as the Preferred Master Browse (ie. default in my configuration). Other computers in a subnet based on NT/2000/XP will accept the forced election of a Preferred Master Browser and will utilize the browser list from the Preferred Master Browser in accordance with the WINS standard.
Enter Windows 10: Windows 10 PRO 10586 being in the NT family seems not to respect the forced election of a Preferred Master Browser previously set in the network subnet so it by default sets itself as the Master Browser which causes conflict with a Preferred Master Browser already existing in the subnet. This does not hold true for Windows 10 Home as such installations are not by default servers. Therefore in most cases viewing/browsing CIFS shares in File Explorer work as expected on Windows 10 Home installations.
Given the above it occurred to me that after using the net view and sbstat routines and discovering that in fact I had a total of 3 Master Browsers on my network subnet that in order to correct this I must somehow force another election to occur between all connected servers on the subnet (2 Win 10 PRO installs and a Linux server hosting SAMBA/CIFS). In my case since I wanted my Linux server to retain the role of Preferred Master Browser I decided to run through the configuration settings of CIFS on the Linux server in which CIFS runs as a Service. To my amazement once I called up the settings configuration screen I found that the CIFS Workgroup name was set to Local, obviously wrong and probably something I had overlooked in initial setup. So changing that entry to WORKGROUP and making certain that Master Browser was selected I saved the configuration setting. Going back to my 2 Win 10 PRO machines I was now able to see/view the SAMBA server name and access all CIFS shares on the Linux server.
To Make certain this would all stay that way I completely shutdown all computers on my network and restarted each one and sure enough the fix stuck and everything was/is now working as intended.
I found an article on the net which was of great assistance to me in all of this and am providing link to it here in hopes it will help others solve their issues as well.
It would seem the reason that 11099 and 11102 now work is that these versions now use NetBIOS for discovery as opposed to WSD that is used in 1511 builds. The great leap back to the future!!
My two 1511 comps can only see each other (except if the 1511 comp is the master browser). They cannot see the Linux based networked printer, or the two insider builds, but both 11099 and 11102 comps see everything, incl the Printer.
But the big question has to be asked - how did this fiasco get out in the wild? Perhaps the reason MS are saying nothing is that they are too embarrassed? Fancy not listing a fixed network discovery in the change list for 11099.
And if MS think we are too critical and/or ignorant, whose fault is that?
Now get the 1511 builds patched or upgraded.
Is there any fix for this available?
Do I have to clean install all my 30 office laptops for them to be able to be visible in build 11099?
Thanks for the tip above.. That was clue I needed.
I was able to fully resolve this issue by having the router perform the Master Browser function.
To date, I have always had my main pc set with Computer Browser service enabled, an all other pc's had the service disabled. It worked fine for years, but of late, it stopped working ; I could still access networked pc's using \\ComputerName, but they were not visible Network in file explorer,
So I now have:
- the Computer Browser service disabled on all pcs
- my router set (RT-AC68U with Merlin 378.55) set with Force as Master Browser ON, and with the workgroup named the same as all the pc's
Everything kicked in after that I can see all pc's, listed under Network in file explorer, on any networked computer.
Last edited by mediaman09; 23 Jan 2016 at 17:05.
first time posting, so might be doing it wrong. In any case I had a similar problem in W10, with the network folder in File Explorer not finding all my computers. The HOMEGROUP did show all members, just the network tab that would not fill out. I have two W10 computers on the network. Tried everything here and some other things involving winsock reinstall. Nothing worked, until I stumbled across this regarding W7
This problem occurs because the Function Discovery Provider Host (fdPHost) service cannot access certificates that are installed or updated after the fdPHost service was started.
It was always the second computer started in the sequence that had the network map problem, so this looked promising. I did exactly as suggested by restarting both
Function Discovery Provider Host
Function Discovery Resource Publication
under Services and both computers showed up on both W10 machines.
There does not seem to be one single problem with this, so maybe for some folks this is worth a try. It is a little more than embarrassing for MS to still have this problem hanging around since W7.
i upgraded 2 computers to windows 10 and java doesnt work on both
Finally installed Win10 on a computer with raw HD. It installed realtively easy.
But I can not figure out how to setup a network to see two Win7 computers on a small business type workgroup.
I disabled Homegroup since I am most comfortable...