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?

Hi there

Can you give the actual registry key you changed / deleted --there's loads of LanmanServer parameter entries --which one ?

Never mind --found it -- now working.

BTW to enable a share again I found if you add the share permission with your LOCAL user name (even if you are logged on with an Ms account) it will also work for the Ms account too.

Looks like finally this stuff is getting fixed.

Cheers
jimbo

Under Parameters, I had a key called "SMB2". If you don't see that key you don't have my problem!

linw said:

Under Parameters, I had a key called "SMB2". If you don't see that key you don't have my problem!

Hi there

just altered my post --it's fixed now --thanks.

Cheers
jimbo

Did you have that SMB2 key as well, jimbo?

linw said:

Did you have that SMB2 key as well, jimbo?

I had it on the "Rogue" machine -- don't know how it got there -- but it's gone now. I re-booted just in case --I think it's always worth re-booting if you change anything in the registry.

Interesting thing also my Logitech Audio server doesn't keep disappearing when it's not in use either --it shows up all the time in Network now when its active.

I never had the SIZE parameter BTW.

I think also if you want to create Passwords for shares you can create credentials --I'm leaving that for the moment --when something is working I'm dis-inclined to "fix it". !!!!!

Note running x-64 on build 10240.

Cheers
jimbo

Glad to hear I have been of help, jimbo. I didn't even need to boot or get out of regedit before it magically worked!

Of course I rebooted to make sure it still worked:)

Must say this is a weight off my mind knowing it is not a win 10 issue (not directly, anyway!). I also hate being beaten by these infernal devices. Glad I wasn't paying myself wages for the time spent!

Cheers,

Lindsay.

Would you guys share the registry key you are referencing?

jimbo45 said:

BTW to enable a share again I found if you add the share permission with your LOCAL user name (even if you are logged on with an Ms account) it will also work for the Ms account too.

Dude, I had asked you several times if you had done just this, and you told me you had....

Regardless, the registry hack is probably dropping you back to SMB1 which will be much slower than SMB2 and less secure.. For you local firewalled network, the security may not be an issue (although, there have been viruses known to take advantage of SMB1)...