Network shares not working on 1803

I have three machines on my network and mainly used the printer share. Two of them are on Windows 10 Pro and one on Windows 7 Home Premium. They all used to belong to a single homegroup which was set up on one of the Windows 10 Pro machines.

After the 1803 update on both Windows 10 machines, I've had issues with machine discovery which have been fixed by looking at some other threads and enabling the two missing services. Now, both W10 machines can see each other (and themselves) on the network tab, which didn't work before. However, they can't connect to the other machine.



After the diagnostics utility, I get this:



It roughly translates to "Machine is available but not responding to connection attempts. A firewall or security setting might be blocking the connection on the file and printer sharing port."

I've correctly configured both machines Share settings to not use password and turned on the shares for Private networks. The network is configures as private on both machines.

I've tried pinging them from each other and it works too.

I'm not sure what else I should do. I've tried messing with permissions but it doesn't seem to make a difference. I also am not sure how I set the permissions for the printer.

After the 1803 update on both Windows 10 machines, I've had issues with machine discovery which have been fixed by looking at some other threads and enabling the two missing services. Now, both W10 machines can see each other (and themselves) on the network tab, which didn't work before. However, they can't connect to the other machine.

1. By other machine, do you mean the Win7 PC ?
2. Can you access each PC by their IPADDRESS (i.e. File Explorer > Address Bar > \\192.168.1.x ?

Eagle51 said:

1. By other machine, do you mean the Win7 PC ?

No, I'm troubleshooting this only on the Windows 10 machines, for the time being. So, by other machine I mean the other W10. I wrote that to clarify that it wasn't the very same machine, in which I can see the available shares.

Eagle51 said:

2. Can you access each PC by their IPADDRESS (i.e. File Explorer > Address Bar > \\192.168.1.x ?

No, the very same connection error as the OP happens. Everything is exactly the same, except with the IP address instead of the hostname. I'm sorry I failed to mention this in the OP, but I had already tried it too.

Are you running any 3rd party firewall ?

Home group has been removed now so can't use that you have to use workgroups. Ipv6 isn't used now so remove it from all pcs. As it's now workgroup it's worth removing any shares and make new ones

Eagle51 said:

Are you running any 3rd party firewall ?

No, I'm running the Windows Firewall. I currently have Avira Free Antivirus installed, but this issue also existed when using only Windows Defender, and as far as I know Avira doesn't have a firewall of its own.

Samuria said:

Home group has been removed now so can't use that you have to use workgroups. Ipv6 isn't used now so remove it from all pcs. As it's now workgroup it's worth removing any shares and make new ones

I've created folder shares brand new, and reactivated the printer share from its settings tab. However, no computer seems to be able to connect and see the available shares on the other, even when using the full path for the share.

No, I'm running the Windows Firewall. I currently have Avira Free Antivirus installed, but this issue also existed when using only Windows Defender, and as far as I know Avira doesn't have a firewall of its own.

1. Have you checked Windows Firewall to make sure it's allowing File & Print Sharing?
2. Have you tried resetting Windows Firewall to defaults?

Eagle51 said:

1. Have you checked Windows Firewall to make sure it's allowing File & Print Sharing?2. Have you tried resetting Windows Firewall to defaults?

I have. I did not try resetting the firewall, but I just did and no effect occurred.

I have now tried resetting most network settings:

Code:

netsh advfirewall reset
ipconfig /flushdns
nbtstat -RR
netsh int ip reset
netsh winsock reset

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