I suspect the feature will be added to a normal update as happened in the Insider builds.
But MS don't tell us anything about these things!
The commands to turn SMB 3 back on are:
Code:sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi sc.exe config mrxsmb20 start= auto
W-10 Pro Insider Preview 1511 (11102)
W-10 Version 1511 (10586)
Neither could see each other.
Ran the Samba removal and now good both ways.
Why do I need Samba anyway?
net view was the clue. OK, both PC's on the Pro, Error 1243 (or whatever), on the Home.
After the Samba fix, both can see each other.
The reason Samba is important is that Linux uses Samba. Many networks will have Linux based NAS boxes so they don't get seen with SMB 2&3 suppressed. Even my networked Brother printer is Linux based.
I am having this problem too but at about a 95% failure rate. No fixes have been attempted. However, even though nothing shows in explorer i don't have any problems running network backups to my main tower, quasi server. After which network members remain unseen.
Yes, you can still access shares but the discovery mechanism is the problem.
I am hoping that the next update to 1511 build will fix it and it is supposed to be coming soon. At least we know that MS has been able to fix it for the Insider builds.
Fingers crossed, then!
I spoke to soon. Went back to previous mode. Can see only the individual PC.
I have build 11102 but that doesn't do anything.
I notice that this problem is NOT addressed in any of the releases.
Has there been any indications that Microsoft is aware and will fix?