New
#11
During the upgrade from one build to the next all security settings are return to default. This means you have to go through all settings and change as appropriate.
During the upgrade from one build to the next all security settings are return to default. This means you have to go through all settings and change as appropriate.
I suppose you mean privacy settings, not security settings?
Yes the privacy settings were all reset. However, I do not believe that these have anything to do with the problem at hand.
I did not change any security setting in the first (build 10240) installation, and I assumed that the subsequent upgrades did not change anything either.
Bart
Does net view give a 1231 error?
Run Sysinternals' ShareEnum. It tells me I don't have a domain or a workgroup!
All these errors are saying we can't communicate with the browser master I think. SMB version problem just introduced?
But still the big question is why isn't everyone's network affected?
That's another good question! After all, we have given them a lot of good info on where to look.
The MS social network thread on this said that the info had been passed to the appropriate MS people.
Strangely, I don't seem to have a master browser, now. That won't help.
I have done some more testing and, like others have said, it definitely seems to be a SMB version issue.
If I turn off SMB 2&3 in the Lanman client I can then see all shared devices, including my NAS WD Mybooklive that was invisible since 10586. I can access the NAS shares also but I can't access the other device shares. I get the dreaded 80070035 error and that means that my Lanman client is asking the Lanman server to display its shares but because the SMB version is different, there is no communication and that results in the client issuing the 80070035 path not found error.
I have tried various combinations but can't get it working as pre 10586.
As far as I can see, all my five win 10 10586 comps have got messed up SMB versions hence a failure to communicate the shares.
I have left my main comps in the mode where I can see the NAS and hope that MS will fix this soon.
Today, I had two updates installed, KB3120677 and KB3118754. No solution for the browsing problem.
Funny thing is that the new Update app is lying about the Update history. It says that KB3120677 was installed on November 25, but that only happened today. Good old Control Panel Update tells me the correct date.
Well, may be the update arrived on November 25 and I rebooted this morning. I believe that the reboot date is more relevant.
We continue waiting!
Bart
Yep, we wait. Wonder how hard it is to see how to fix it considering it was fine pre 586?