How to fix 0x80070035 error?

[SamD123]

I get an 0x80070035 error when I try to connect to my homegroup, “Window’s cannot connect to \\Office-PC” I have Widows 10 on two PCs and I have been using my homegroup for at least a year and now I get the error message on one of the PCs, an ASUS vivobook, the other PC, a HP Pavilion, can connect to the ASUS . I did a system restore but that did not make any difference.

The ASUS can see the HP and it's folders but the folders are greyed out and when clicked I get the 0x80070035 error. I also have a work group that worked between the two computers but the workgroup on the ASUS no longer works but the HP can connect to the ASUS.

 

[Colif]

But before turning-off everything in the "Network and Sharing Centre" -> "Change advanced sharing settings", I noticed under the "Private (current profile)" -> "HomeGroup connections" section was set to "Allow Windows to manage homegroup connections (recommended)" which didn't look right. Changed this to the second option of "Use user accounts and passwords to connect to other computers", then logged-out and back in which appeared to have fixed the problem.

From https://social.technet.microsoft.com/Forums/windows/en-US/17c9ea7d-52df-4ef9-95fa-0a961d11bfa3/fix-for-cannot-access-nas-drives-sharefolder-is-not-accessible-or-error-code-0x80070035?forum=w8itpronetworking refereed to from http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-explorer-network-error-0x80070035-the/f30a1112-ffa7-4230-b843-ecc7ab8b5119

from same thread:

At last I found the cause of my problem, during a Windows Refresh some Windows features were turned off, make sure this is enabled:-

Control Panel / Programs and Features / Turn Windows Features On or Off and make sure SMB 1.0/CIFS File Sharing Support is ticked

Give those a go

 

[SamD123]

After two week the and trying different methods to correct the problem and with none of them correcting the problem I can now connect my ASUS laptop to my HP Pavilion with out any errors. This happened one time last year also and I have no idea what is causing the problem.