It seems Window's network discovery / name resolution doesn't work anymore on computers freshly reset with the new April update for Windows 10 (Build 1803). (Computers that were merely updated don't seem to be affected.)
My local network consists of a modern NAS drive using samba for sharing, plus a couple other Windows 10 computers (in addition to the one I'm typing on). All computers have the network configured as a private network.
Before the April 1803 update, going to File Explorer -> Network would show a list of windows computers, including the NAS. I could then browse the NAS, mount it as a network drive, etc.
This "network discovery" behavior still works on computers that were merely updated to 1803, however resetting the computer to a fresh 1803 install seems to break network discovery. On reset computers, going to File Explorer --> Network results in Nothing. Nada. No name resolution. No network discovery. Nothing shows up.
When I try to manually connect to \\AS5002T or \192.168.1.46 (my NAS) on the updated 1803 computers, it works (I can browse the NAS files). But on the reset 1803 computers, connecting doesn't work anymore at all. In the best case, I just get "Network Path not Found".
Googling "network discovery Windows 1803" shows I'm not the only one having problems. Some people have observed certain "Function Discovery" services not running, and on the reset computer I noticed that SMB 1.0 features are disabled by default.
Anyone know if this is a recognized issue? What fixes there may be? Perhaps people don't know about this issue because it only affects computers reset with 1803?
In total, the problems are for reset, fresh Windows 10 computers with update 1803.
- Network Discovery is not working, shows no computers on network
- Cannot connect to Samba share