Why are network resources falling off?

Question

Computer networks

There is a network of about 20 PCs, a mikrotik router with 20 ports (I don’t remember exactly which one). Each has several shared folders for everyone. Periodically, computers disappear from the network environment, or some kind of ball becomes inaccessible. After some time, the computer may become available again. Some computers are not visible at all in the network environment, but they can be accessed via a link through the explorer. All computers on windows 10, in the same workgroup, no AD. Network discovery is enabled, password access to network resources is disabled. Pings go, the Internet works. The problem is only in network detection and falling balls.
How to diagnose the cause of network instability? Maybe there are some monitoring utilities (zabbix? Or is it generally from another opera). Can netbios somehow monitor?
Theoretically, will the NAS solve the problem if all the balls are transferred to it?

Answer 1

Apparently, access goes by name, since the network environment was mentioned. And access by name requires a name server, if there is no server, then a random machine becomes a server. And until the information at the new name server (WINS) is updated, some of the computers are not visible.
We need a server - a "file cleaner", at least RAID1 (2 disks in parallel), each computer has its own user for accessing the file cleaner (a classic solution without a domain controller).

Answer 2

In Windows, peer-to-peer networks (networks without AD) work ... as you described.
This is due to the fact that to determine the list of computers on the network, computers choose "master browser" and this master browser distributes a list of available hosts over the network. If the master browser is turned off, then after this is detected, the remaining computers with Windows begin choosing a new master browser.
Because of this moronic scheme, there may be several master browsers on the network that serve their own set of computers.
When there is AD in the network, the AD controller automatically becomes the master browser, which solves such problems.
You can manually designate the computer that is the "server" in your network as the master browser, and forbid the rest to be nominated for this post. Right heremore about it.

Answer 3

NAS is definitely better. netbois will not help you much, look at the power supply modes in the PC, and the network and firewall settings. According to US, you can assemble it yourself, just keep in mind that RAID0 of 2 disks is not good for data storage.

Answer 4

I had such a problem on the same network of several PCs with different OSes. And nothing helped to solve the problem.
As a result, I created shortcuts for each computer, and as users passed, I understood that they got to those computers where they needed to.
There were no problems after that.
If in a zapadlo users poke shortcuts with pens, then you can create a batch file that will open all shared folders and then close them. Thus, paths will appear for navigating to network resources.

Answer 5

We have a domain controller on the network, an exchanger for Linux. Workstations from Xp to 10.
Shares on the exchanger are indicated through the IP address.
Most computers do not experience problems working with samba, but some sometimes experience a temporary drop in the network share and then spontaneous restoration of access. It does not depend on whether the host is in the domain or not in the domain. But it seems that they are all dozens (I could be wrong). My ten has never done such a disgrace.
One day in general there was a storm for half a day - several hosts at once fell off the ball, then recovered. Then everything calmed down by itself.
At the same time, of course, problem computers at the network level see the exchanger.
If the solution in the form of disabling the computer browser service helps someone, then probably only those whose network resources are specified through netbios names?