Network shares not working on 1803

Eagle51 said:

Some have had success fixing the 0x80070035 by renaming their PC's - Change Computer Name in Windows 10 | Windows 10 Tutorials

I've executed the commands on my previous post in both computers and then proceeded to rename both: they both can see both machines on Network tab, but still can't connect to each other, neither by name nor IP address. I've also tried messing with the Network ID option on System settings: I've tried to set it to a domainless workspace called WORKSPACE and to the other option that says "I'm a home user". Both made no difference.

Hey Phaellow,
Hmmmm ... I'm not sure why you keep getting 0x80070035, especially using \\IPADDRESS ... Look thru this tutorial to see if it might help - Share Files and Folders Over a Network in Windows 10

Note: Since you've changed PC names, you should check Credentials Manager on each PC and see if they still have the proper Credentials (pcname,username,password) for the other PC. To change the PCNAME, you'll have to delete the credential and manually add it back with the correct PCNAME.

Control Panel > Credentials Manager > Windows Credentials

Eagle51 said:

Hey Phaellow,
Hmmmm ... I'm not sure why you keep getting 0x80070035, especially using \\IPADDRESS ... Look thru this tutorial to see if it might help - Share Files and Folders Over a Network in Windows 10

Note: Since you've changed PC names, you should check Credentials Manager on each PC and see if they still have the proper Credentials (pcname,username,password) for the other PC. To change the PCNAME, you'll have to delete the credential and manually add it back with the correct PCNAME.

Control Panel > Credentials Manager > Windows Credentials

Hey, thanks for reminding me that Windows Credentials existed. I was able to delete the old HomeGroup credentials. However, that didn't have any effect. I also followed the tutorial and made sure that the required services were running and set to Automatic start. In the meanwhile, I've also disabled the SMBv1 client. I created a share using the advanced share method and I couldn't get it to connect on the other computer, either via \\IPADDRESS or \\COMPUTERNAME. Using the share full path also still doesn't work.

In advanced features may need need to enable SMB1 protocol if it's now disabled. I had to do it to see shares on XP. I never used homegroup though, just plain network path.

Eagle51 said:

Hey Phaellow,
Check each PC's hosts file and see if there are any references to your PC's IP/PCNAME. If there are no references, you could try adding them in the following format and you must be using static IP's for this to work.

Check Windows Services and see if it TCP/IP NetBios Helper is running. It's default start type is Manual (Trigger), but you might need to set it to Automatic.

I did this but it made no difference: the computer is clearly resolving the name, it's the connection that's not working. I also checked the TCP/IP NetBios Helper and it is Automatic (albeit delayed) and running.

91fw said:

In advanced features may need need to enable SMB1 protocol if it's now disabled. I had to do it to see shares on XP. I never used homegroup though, just plain network path.

That's right, but as I'm using only Windows 10 machines (and later 7), SMBv1 shouldn't really be required. I've already tried it with it enabled and it doesn't solve my issue.

If you haven't already, try disabling IPv6 - Enable or Disable IPv6 in Windows

Note: Reboot PC's after disabling IPv6.

Eagle51 said:

If you haven't already, try disabling IPv6 - Enable or Disable IPv6 in Windows

Note: Reboot PC's after disabling IPv6.

Sadly, this didn't solve it.