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.

  • Intheflsun@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month ago

    You shared them from a 192.168 then changed it to a 10. Make sure the new network is in trusted not public.

    • GasMaskedLunatic@lemmy.dbzer0.comOP
      link
      fedilink
      arrow-up
      1
      ·
      1 month ago

      I have checked that numerous times. The network is set to private. Sometimes it switches to Public if I turn on my VPN, but for testing purposes I’ve disabled that until I can successfully access a file share. One step at a time.

      • Intheflsun@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        Only 2 things I can come up with now is dns not updating on the router, or check and see if something added or edited the host files and that’s referencing the old network.

        it’s always dns

        • GasMaskedLunatic@lemmy.dbzer0.comOP
          link
          fedilink
          arrow-up
          1
          ·
          1 month ago

          I flushed my DNS records and flipped a couple settings off, but no change. I’ll experiment with DNS more by removing it from the equation when I have time. Thanks for the suggestion.

        • GasMaskedLunatic@lemmy.dbzer0.comOP
          link
          fedilink
          arrow-up
          1
          ·
          1 month ago

          I changed the DNS on the router and the devices to Google’s 8888. Cleared my hosts file, too, but still can’t access my files over the network.

  • dual_sport_dork@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 month ago

    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:

    • Ensure both machines are in the correct time zone and have their clocks set correctly. Windows authentication will silently and mysteriously fail if either computer’s time is off too much, IIRC around 4 hours.
    • Ensure both machines are updated to the same Windows build. Some dissimilar builds of Win10/11 are incompatible with each others’ network shares for no readily identifiable reason. I’ve run into that one before.
    • GasMaskedLunatic@lemmy.dbzer0.comOP
      link
      fedilink
      arrow-up
      1
      ·
      1 month ago

      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.