A frustrating ongoing home network problem!

SingleAction

Member
Jul 27, 2006
63
0
66
I have 4 Win 10 computers. 3 are hard wired, and 1 on wifi. The last couple of years especially after some cumulative updates, it seems to create havoc with my network settings. The one most consistent problem is network discovery among all 4 computers.
This has been on going for the last 2 years. I've had home networks for years with XP, Vista, Win 7, Win 8 and never had this problem.
Currently, the first computer I boot up in the morning becomes the "boss" of the network. After all 4 machines are up and running the first can normally see everything on the network, and can see shared folders with any of the other 3 machines! When you go to any of the 3 other machines, it a crap shoot to what they see or don't see. One will not see itself, but sees the second and third machine only, and so on. All the machines are on the same network with the same settings. This configuration and settings originally worked fine when I first started with Win 10.

I have tried every setting that's been recommended on various sites over the last couple of years, but nothing seems to work. Every so often after an update, without me doing a thing, or change settings, I'll have an normal running network where everyone sees each other. but it doesn't last very long.
So what I've been doing is if I want to copy a file from one computer, that I don't normally see, I have to boot the computer I want to copy the file to first.

BTW, this condition followed me moving once, and 3 different routers, so it's not connection or hardware problem.

I'm sorry that I'm not more computer literate in my explanation of the problem!
 
Feb 25, 2011
16,963
1,597
126
Sounds like name resolution is borking, and discovery isn't helping. Could be firewall issues too.

Why no just give everything a static IP address and use those instead?
 

razel

Platinum Member
May 14, 2002
2,337
90
101
Ensure the network settings are set to 'private' otherwise network discovery will have issues, often not work at all. Additionally if you frequently update router firmware that can create a different network connection name when you connect, which again may cause your connection to go 'public' by default. If you know the computer name, it should be able to connect. I do when I benchmark routers. Even in a mesh setup, as long as the network is private and I know the computer name then file shares work fine. Some routers will also add a TLD. For eg. GoogleWiFi defaults to .lan. So if you computer name is LapCrush, you can access it via \\lapcrush\ and \\lapcrush.lan\