You shared them from a 192.168 then changed it to a 10. Make sure the new network is in trusted not public.
techsupport
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
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.
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
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.
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.
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.
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.