Folks,
I have a domain at home with desktops running W10 Enterprise. Clean installs. The Network location on each shows the domain (with the domain name). When the computers were set up, it took a couple of hours, but each machine was able to browse the network and see every other computer regardless of OS (7, 10, 2008r2 or 2012r2). The DC runs 2012r2.
This week I started upgrading to the, November, Threshold 2 update (build 10586). I used DVD's and just upgraded the OS on each machine, leaving all files in place (never did get the update offered through WU). Worked almost 100% perfectly (leaving each machine attached to the domain, etc.) However, on each machine that I updated, browsing the network is now limited to seeing ONLY the two W7 machines left on the LAN. I have changed every setting I can think of with no success. There are no group policies being applied...
Does anyone have any idea what the update might have changed or defaulted on these desktops? I am not sure how to get started fixing this. Whatever did change, probably was something that didn't work in previous builds or didn't exist, I guess. I also find it odd that they still see the W7 Pro X64 desktops.
Any advice would be appreciated.
Thanks.
Charlie
I have this same problem across the 4 computers on my local network. Network Discovery was fine until they upgraded to 1511 now it doesn't work properly. One thing I have noticed though, is that if you switch them all off, then Network Discovery will work properly on the first one that is switched on and only that one - very strange - particularly as they're all configured exactly the same.
It's clearly a bug in this latest upgrade as there are a number of threads appearing on the internet.
I have the answer. The FUNCTION DISCOVERY RESOURCE service prior to 1511 is set to AUTOMATIC". For some reason it gets changed to manual or disabled during the upgrade. Once this service is running, the machine can be seen during a browse. Not sure why this service is so important now, but it is. I have made sure it is running on all machines. Works like a charm. Maybe the whole master browser thing is changing.... Or this is some kind of bug.... I just don't know. For some reason every browsing problem I have read about involves this service....I have this same problem across the 4 computers on my local network. Network Discovery was fine until they upgraded to 1511 now it doesn't work properly. One thing I have noticed though, is that if you switch them all off, then Network Discovery will work properly on the first one that is switched on and only that one - very strange - particularly as they're all configured exactly the same.
It's clearly a bug in this latest upgrade as there are a number of threads appearing on the internet.
Sorry that doesn't fix it. Despite it been set to manual, that service was already running on both of my PCs. Setting to automatic and rebooting didn't resolve the problem.
The networking aspect is running because I can \PCNAME and browse the PC. I think this is some problem with Explorer itself.
Too bad. I suspect we have different issues then. The issue I am talking about involves browsing and the W10 PC publishing itself to be "browse'd" domain/LAN. I could always hit the device using a qualified name, but post 1511 the upgraded workstations were MIA when browsing. For us, it worked on 6 work stations and 3 servers. I am not sure it is a "bug" or just a way to replace the master browser requirement. Good Luck
I just installed the latest cumulative update on both PCs, restarted and now they're both showing up in explorer. We'll see how long this lasts, but fingers crossed, its resolved now
* It's "better" but not resolved. My wired PC still occasionally gives me the "Network path not found" BS error. It usually happens if I haven't attempted to browse the wireless connected HTPC in a while.
This stuff is getting old fast and should've been fixed by now. It's been an issue for me since Windows 7.
I just installed the cumulative update on a virtual machine running version 1511, but it did not help. Well, it may help a little. I do see the host on which the VM is running, and some (but not all) Windows 7 PC's.
Bart
I have this problem and it is not fixed with the latest cumulative update. That 'Function' service is running, as well.
There is something basically wrong that I believe MS has to fix.
Net view gives a 1231 error and Sysinternals' ShareEnum tells you you don't have any domains or workgroups!
Damned annoying and definitely started with 10586.
