D
DanMcD674
Guest
I have a wireless home network with 4 client computers and a Windows Home Server with shared folders. Of the four clients, there are two laptops running Windows 10, a desktop running Windows 8.1 and a desktop running Windows 7. At some recent point the two laptops became unable to access the shared drives on the server. They both can access the internet, and see the server and all the devices on the network, but when I try to access the server I get the following error.
Windows Cannot Access {SERVER}
Error Code 0x80070035
The network path was not found
When I run diagnostics, it finds the issue "One or more network protocols are missing on this computer," and "Windows Sockets registry entries required for network connectivity are missing."' It is unable to fix the error. I typically also use a NET command to map two locations on the shared server drives to drive letters on the client, but when I try that I get "'System Error 53 has occurred. The network path was not found."
Both of these Windows 10 computers used to be able to access the shared drives on the server, and the two desktops running Windows 7 and Windows 8.1 still can. I'm not sure exactly when the Windows 10 computers ceased being able to access the drives because neither are my primary computer.
I've tried resetting all the WinSocket protocols and changing my network adapter settings, but nothing has been successful in restoring my connection to my shared server drives.
I did recently upgrade my router from a Cisco/Linksys E4200 to an ASUS TM-AC1900 and played around with the settings on the router but I don't think that's where the problem lies because the two desktops aren't having a problem.
I could use some help getting this fixed. My laptops don't have large hard drives, and I rely on my shared server drives to store all of my valuable data.
Continue reading...
Windows Cannot Access {SERVER}
Error Code 0x80070035
The network path was not found
When I run diagnostics, it finds the issue "One or more network protocols are missing on this computer," and "Windows Sockets registry entries required for network connectivity are missing."' It is unable to fix the error. I typically also use a NET command to map two locations on the shared server drives to drive letters on the client, but when I try that I get "'System Error 53 has occurred. The network path was not found."
Both of these Windows 10 computers used to be able to access the shared drives on the server, and the two desktops running Windows 7 and Windows 8.1 still can. I'm not sure exactly when the Windows 10 computers ceased being able to access the drives because neither are my primary computer.
I've tried resetting all the WinSocket protocols and changing my network adapter settings, but nothing has been successful in restoring my connection to my shared server drives.
I did recently upgrade my router from a Cisco/Linksys E4200 to an ASUS TM-AC1900 and played around with the settings on the router but I don't think that's where the problem lies because the two desktops aren't having a problem.
I could use some help getting this fixed. My laptops don't have large hard drives, and I rely on my shared server drives to store all of my valuable data.
Continue reading...
