New
#1
Network Shares not seen with MS account
I have previously asked for help on an issue I had whereby one of my win 10 comps would not let any other comp see its shares unless the requesting comp had a local login. With a MS login you would get the error 80070035, Path not found.
I have spent days (and nights!) trying to find why my main comp was the only one acting like this. I have found the solution.
The offending comp has been through many iterations from win 7, win 8, win 8.1 and numerous Preview builds. This means that there was the likelihood that a setting somewhere would not now be correct. Googling for an answer was just an exercise in frustration as this 80070035 error has been around for years but I never found a link to what I have now found.
I have done a lot of checking of services etc between my comps to no avail. But today I was drawn to the registry settings of the Lanman Server. I compared the problem comp with a good one and after a while I found a discrepancy. The LanmanServer\Parameters had two extra keys that the good comps didn't have. These were 'Size' and 'SMB2'. I deleted both and was amazed to find that fixed the problem (gotta remember I have had a ton of disappointments!). The shares just popped up as they were supposed to!
The actual item that caused it was the SMB2 entry. It didn't matter earlier, but it does now. Clearly, the OS has evolved to make this setting a problem. Why this only affected the MS login I don't know. Maybe some clever person can explain?
Sorry for the long post. Maybe it might help others, especially those who have done a lot of upgrading.
PS Apologies to MS for bagging their networking! Maybe they could check that entry as they upgrade, though?