Windows 10: W10 Ent Build 10586 Domain PC's unable to browse network

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.*Huh

Any advice would be appreciated.

Thanks.

Charlie

:)

 

Printer connectivity, W10

A weird problem has occurred, and seems to have done so only after a new build update.

I have a simple home network setup, with my main PC as a "server" ( as in hosting printers that are shared) Recently I reinstalled as native, W10 on the 2 main computers used, using an iso from 23/01/2016. The main computer is W10 Pro, while the other is
W10 Home. Build was still 10240 on PC1, build on PC2 is 10586. Now build on both is 10586, but no difference.

After initial setup, and installation of printers, the small Canon laser, LBP6000 was detected and installed as default. This was shared, (with no password protection on the networks) and was duly installed/added on the second PC, together with the other
printers.

All were tested, and responded on both PC's.

Today, requiring a print from the second PC, it printed to the wrong printer, and on re-specifying the correct one, just failed to print.

On checking, I found that the LBP6000 no longer showed in Devices and Printers on this PC2.

The troubleshooter when told which printer to check basically came up with an "Unable to connect. Check connection powere etc." error message. I knew the printer was OK on PC1, so the asked to add a printer on PC2, browsed for and found the printer only
to be told the same.. Unable to Connect..

Went back to all settings to check.. no changes required, just not seeing anything for that printer on PC2.

Removed device from PC1, and left for W10 to redetect.. It could not load the printer, so checed with Canon(previously the driver was 'available with W10' now a x64 driver is available. Downloaded, installed, rebooted, found the printer, made default. checked
sharing.... etc...

Then checked on PC2 again.. still no printer showing. Installed new driver on PC2, and was asked to upgrade old existing driver.. but after this still no printer.

What is more strange is that even though the printer does not show as a device, it is detected and connected to if I troubleshoot printing, but will not print from PC2.....

Any ideas???

 

Update KB4022714 fails to update

I reinstalled w10 on wed 14, worked fine, Friday unable to login to ms account. Talked to the manufacture of pc, they restored the pc to factory settings.

I am unable to download the cumulative update, it keeps failing. I did the digicab trouble shooter, it fixed a few things, still unable to download the cumulative update. What can I do next? This pc is not useable. Its a 10586 build.

***Post moved by the moderator to the appropriate forum category.***

 

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....

 

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 *Smile

* 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.