I recently encountered an error with my router that required a factory reset in order to fix. I figured since I was already resetting everything, I’d might as well reorganize my network. I switched from 192 to 10 based IPs. I got all my devices configured and everything connects to the internet fine, no hiccups anywhere, except when I try to access my Windows network shares using any device on the network. They worked prior to the reconfiguration, but I also did updates when rebooting the machines, so I don’t know what the problem is. The errors I get are 0x80004005 (Unspecified error) when attempting to access \10.0.1.{deviceIP} and 0x80070035 (The network path was not found.) when attempting to access \{deviceName}. I’ve disabled all my firewalls, I’ve tried the registry changes, reconfiguring services, reconfiguring and even resetting network settings (including NetBIOS), and I’m out of ideas as to what the issue could be. The device shows up under Network on other devices, but attempting to access it hangs for a minute or two and then gives 0x80070035. FWIW, my network is configured to have 10.0.0.x be infrastructure (router and DNS), 10.0.1.x be personal devices (PCs, laptops, phones, anything I own, etc.), and 10.0.2.x is DHCP for visiting/guest devices or anything I can’t configure myself.
Any help is appreciated.
Two stupid questions:
Are you accessing these shares by IP, or by name (WINS)?Edit: I can’t read.What does your netmask look like? 255.255.255.0, or…?
Other forehead-smackers I would check:
Subnet mask is 255.255.0.0. Router defaults to that so it’s what I put in on all the machines I’m trying to connect. Devices are all on the same time and zone. I’ve updated all the machines as much as I can, though all three devices fail KB5034441 with download error 0x80070643, but this shouldn’t be the problem since they were doing this before the problem arose as well. Shouldn’t, but I guess it could be since this is Windows. All 3 (share device, main PC tested and verified prior to reconfiguration, laptop) are Windows 10 Pro 10.0.19045.4355.
Well, that shoots several of my theories.