What is the problem with network balls when dividing a network with an AD domain into a vlan?

Question

Computer networks

I selected a part of machines from the general network into a separate vlan. Routing between the new vlan "V2" and the old one ("default" on D-Link's switches) was carried out through the D-Link DGS-3120 L3 switch. I configured DHCP-helper on the switch so that machines in the new vlan receive dynamic IP addresses from a common DHCP server for these two vlans.
In principle, everything worked (pinging servers, loading web pages of the local portal, authorization in AD, etc.), but at first I could not get into the network folders of machines using \\<PC_name> (via the SMB protocol). It just didn't open anything, neither by machine name nor by IP address (\\192.168.2.55, for example).
A couple of days later, it just worked.
I would like to know what is the reason and how to avoid this if I introduce another vlan with a new IP network for it.
Computers in the new vlan, of course, normally received IP addresses and were registered through dynamic updates on the DNS server.

Answer 1

Read about NetBIOS, WINS, DNS. About search domains too.