How to access computers by name between branches?

Question

Domain Name System

In general, the picture is this. There are two branches, between them vpn based on kerio. In one of the branches there are computers in the domain, there is no server, in the other branch there are no computers in the domain, there are no servers in principle.
The problem is that inside the first and second branches, I can separately access the PC by the name of the computers, but from the second to the first branch - no. I know that it is possible to raise DNS based on a domain controller, but in this case, the call only works by the full name, i.e. instead of \\comp1 it will be \\
comp1.domain.zone real name and not by name + domain controller zone.

Answer 1

The short entry is when the machines are in the same 'workgroup', but I'm not sure if the same machine can work in the workgroup and in the domain, most likely not, so you don't have netbios names to resolve.
Be careful, the workgroup mode has a limit on how many machines can connect to another machine at the same time (linux samba does not have such a limit).
Tip:
* network connections on machines on the network must be configured in 'Company network' mode and not 'home network' this affects not only the network, but an alternative, long tinkering with policies on each machine
* the workgroup name on all machines must be same
When there is no domain controller and dns server, I remember setting up in a small network (there really were no options) automatic copying of c:\windows\system32\drivers\etc\hosts by a task in the scheduler from a central file server, the same script was sent from machines to server hostname and ip address, i.e. all machine names were automatically collected on the server and the resulting file was sent back as
hosts which is either a domain controller or samba, according to the mind, any win machine can also but no) I fixed it with a special directory on the server file with a list of links to network machines (a regular .lnk file, created with a script), with a registered name in hosts and a working local network and even a neighboring network with configured routing, access to machines works as expected, just instead of the standard non-working item in the 'Network' explorer on all machines on the desktop there was a link to this directory.
The set of scripts is primitive, all are launched in the scheduler. This mechanism works with a guarantee and is faster than the regular one for 'workgroups', and most importantly, it doesn't care that the network is not a single local one, don't care about license restrictions, it even worked with a remote machine on the Internet (smb is open out to the Internet, wildly not secure, by the way, no need So)

Answer 2

1. Addressing by short name in DNS works if DNS search suffixes are configured correctly.
2. What prevents to enter computers of the second branch into the domain, using the controller in the first branch?

Answer 3

NetBIOS
https://hackware.ru/?p=11458