Did Windows 10 April Update break network discovery and Samba support?
Everything you need to know is here:
https://blogs.technet.microsoft.com/filecab/2016/09/16/stop-using-smb1/
In summary:
SMB 1.0 is BAD. Don't use it. You probably don't need it anyway (we'll get to that).
Because it's so bad, Microsoft has begun removing it from Windows completely, starting with the Windows 10 1709 Fall Creators Update. Right now, if you just update an existing system that already had it, you get to keep it. But if you start fresh with a new copy of Windows, it won't be there. Soon, it won't even be available to install, and soon after that it will be actively removed by a normal Windows Update. At that point, it will likely just be a normal monthly patch, and not even a full feature upgrade.
In other words, there's no point bothering to re-install this back on your system. You're setting yourself up for a fight that's not gonna go your way. You might win today's battle, but the problem's gonna come back (probably sooner than you think) and you'll eventually lose that war.
Fortunately, very few things still require SMB 1.0, and most of those that do are the result of running outdated software on some other system, such that you can also update the other system and restore service.
One of the most noticeable places which still relies on SMB 1.0 by default is the network browsing feature in Windows Explorer (formerly Network Neighborhood). However, you can fix this, too, without using SMB 1.0:
- Find the
Function Discovery Provider HostandFunction Discovery Resource Publicationservices and set their startup types toAutomatic (Delayed Start). - The next time you start network browsing, follow the prompts to enable Network discovery.
Do this for all Windows computers on your network, and everything is fine again, using the much nicer WS-DISCOVERY protocol.
Recommended Actions
It seems that windows is abandoning SMB 1.0, and currently my NAS (which is only two years old) doesn't support whatever "Network Explorer" protocol they have moved on to. So for now, your supposed to leave SMB 1.0 disabled, manually enter the necessary information into Credential Manager, and manually connect to the network drive. Setting the two "Function Discovery" services to Auto Delayed didn't help me, but that is supposed to recover the Network Explorer.
To recover the behavior where you are prompted for username and password when connecting to certain NAS devices, I had to "enable insecure guest logons". Otherwise Windows will just give up after trying your username (not telling you what failed nor why).
Alternative Actions (to recover the "old behavior" of windows)
Enabling the optional feature SMB 1.0/CIFS Client and restarting the computer will fix network discovery.
You may still get "Error code 0x80070035 - The network path was not found" if the samba device you are connecting to does not have a user account name that matches your windows account name.
There are several ways to fix the above "missing username" issue (despite it appearing that its a different kind of issue). The first is by placing a valid entry in the Windows Credential Manager. In my case, the entry was for the domain AS5002T, the username admin, and my password.
A second method, which will recover the way windows worked in the past, is to instead "enable insecure guest logons". Insecure guest logons are used on many consumer NAS devices, as a way to let unauthenticated network users "preview" the shares on the NAS.
A third method would be to simply add your windows username to the samba server's list of usernames.