What conditions are sufficient for Windows computers to see each other in a networked environment?

Question

Computer networks

I connect offices via L2TP.
All offices should have a different subnet ala 192.168.1.0/24, 192.168.2.0/24, 192.168.3.0/24, etc.

I want computers to see each other in a networked environment.

What conditions must be met for this?
Maybe they should all be put into the 16th mask? That is, in one broadcast domain?
Or it is necessary to raise some WINS server there (I did not delve into the topic).
And will it be possible to climb network spheres, for example, to different working groups?

That is, in one office, make a working group Office1, and in another - Office2. Will they be able to open each other's balloons? Or do we all need to do one working group?

If anything - Windows Server'a, there is no domain controller, there is no active directory. There is nothing at all, only Mikrotiks and that's it.

Answer 1

so that Windows computers can see each other in a networked environment?

The Network Neighborhood theme is outdated and abandoned. No one cares anymore about making computers visible in a networked environment.

And will it be possible to climb network spheres, for example, to different working groups?

If you access by ip-addresses, then this can be done this way (in the explorer \\192.168.1.222, the balls on this host will be visible). To do this, you do not need to see them in the network environment and it does not matter what networks they are in, as long as the routing is configured. If you want access by computer names, then either WINS or DNS.

Or do we all need to do one working group?

Not necessary. If the network environment does not care, then the workgroups do not care.

Answer 2

The theme of the network environment is really outdated.
Technically, access is determined by routing, but visually, in order for the network environment to show, you can try to play around with the Master Browser setting.
You can forcefully assign Master Browser through the registry; without this assignment, computers periodically wrest this role from each other.
On one computer in the subnet, configure:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters
"MaintainServerList"="Yes"
"IsDomainMaster"="True"
on the rest, respectively:
"IsDomainMaster"="FALSE"
"MaintainServerList"="NO "
I have a domain in the same subnet and there are no problems, therefore,

Answer 3

NETBIOS as a whole is extremely full of holes and is no longer recommended. In more or less normal organizations, all personal balls are forcibly closed. NETBIOS traffic between client devices is carefully filtered. Only one/two carefully controlled, possibly DFS distributed, servers remain.

Answer 4

According to the classics, push all PCs into one network group and assign one common as on all PCs for more or less central access to resources + normally working routing.