Home network discovery not working after latest W10 Update

I've tried three different "fixes" and the network is still a mess. Can see different units on various units but no unit sees all units. My wifes documents directory/files seem to have been made read only and she can no longer use them from other computers.

Have been wondering if those having troubles can still use the cloud and whether the problem is related to MS big push to it

ALSO, this morning, opened exel and before I could use it I was forced to agree to a new license agreement. ??? office 2013 that has been installed for months.

No issues with office 2016 here, or any other software. Fully patched 10586.14 10 Pro clean install.

@linw

I agree there is a problem with host discovery in Win10. At the moment my Win10 can't even see itself under Network.

The reason for my post on smb versions is that the implication is actual host name resolution if fixed by disabling smb2/3 and forcing smb1. If I run Get-SmbConnection in powershell after connecting to a samba server it tells me I'm connecting via smb3. If it couldn't resolve the host name I wouldn't be able to connect.

As for the WD NAS device it looks perhaps like a variation of this issue:
http://answers.microsoft.com/en-us/i...a-b85ae133c887

Accessing NAS's from Linux has always been a struggle since these devices all seem to use archaic versions of samba or something similar. In Linux you are forced to do a manual CIFS mount and pass it a deprecated security mode for NT lanman ( sec=ntlm ) and not an SMB version ( which is another option ) in order to make the connection since the default in cifs or using a linux file manager is more in line with OSX and Win7+.

I'm not sure if Windows can make a specific mount of a remote share using a different set of options than the global ones. Maybe it's something powershell can do.

EDIT: Don't remember if I said this or not but Microsoft is aware of this issue of host discovery - Well, one Microsoft employee is anyway:

I wanted to let everyone know on this thread that I have been able to reproduce the issue in my environment and I have logged an issue with the product group to have them take a look and provide feedback.

I will update this thread again once I have some more information.

---

Adam Rudell | Windows Networking Beta | Microsoft Corporation


Thursday, November 19, 2015 6:02 PM

Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586

Public or Private network type? The default for Public is off and for Private it's on. Still shouldn't change it once you set what you want though? Unless you connected to a different network like a coffee shop free WIFI or something.