Why don't computers and printers want to register with WINS while they are on the same ip network?

Question

Computer networks

Good day.
Background:
Not long before the problem, there were 2 networks living.
192.168.1.0/24 in one city A and the second network 192.168.2.0/24 in another city B, and between them there was a VPN tunnel over external IP gateways.
Printers and computers from city B were perfectly connected to servers 192.168. and the printer was connected in the same way by name. In both cities, each had its own DHCP.
But one fine day, I had to change the provider, all cities in one contract.
And we connected the Switch of City A and the switch of City B through the provider with a data transmission channel, removing all the gateways, all VPNs.
Network 192.168.1.0/24 began to include city A and city B.
City A and City B both work on DHCP (192.168.1.4)
Static on servers and some printers. In City B, all devices are on DHCP.
Here's the problem... why aren't any devices in city B registered with WINS?
We take the printer and physically bring it to city A, the registration is in WINS, we take it to city B, again it is not in the registration. And even Net-Bios does not work.
net view - no devices from city A to city B and vice versa.
Through the VPN, everything worked fine, in different networks.
After the merger, everything went wrong...
Where to look for the problem? What to pay attention to?
The most interesting why in WINS do not regatsya? Machines can even be in different segments, networks, and will be registered, but not here. What are miracles?
DHCP config just in case:
(there are static clients, I think it makes no sense to write poppies and ip)

dhcp.conf

# NETWORK_A
subnet 192.168.1.0 netmask 255.255.255.0 {
  option domain-name "workgroup";
  default-lease-time 36000;
  max-lease-time 86400;
  authoritative;
  allow booting;
  allow bootp;
  range 192.168.1.40 192.168.1.169;
  option broadcast-address 192.168.1.255;
  option routers 192.168.1.1;
        option ntp-servers 88.147.254.230;
  next-server 192.168.1.4;
  filename "pxelinux.0";
  option root-path "192.168.1.4:/home/bootme";
  option domain-name-servers 192.168.1.1 , 8.8.8.8;
  option netbios-name-servers 192.168.1.15;
        option netbios-node-type 8;
  }

Well, maybe it's not relevant, but for some reason the wins server doesn't want to be a master...

browstat status

C:\>browstat status

Status for domain WORKGROUP on transport \Device\NetBT_Tcpip_{87FB3A52-D6F5-43B7-ACB9-886690EBB91D}
    Browsing is active on domain.
    Master browser name is: SERVER02
Could not connect to registry, error = 5        Unable to determine build of browser master: 5
   Unable to determine server information for browser master: 5
    1 backup servers retrieved from master SERVER02
        \\SERVER02
    There are 27 servers in domain WORKGROUP on transport \Device\NetBT_Tcpip_{22F03A14-D325-23B7-A4C05
    There are 1 domains in domain WORKGROUP on transport \Device\NetBT_Tcpip_{22F03A14-D325-23B7-A4C05

Answer 1

first of all, check if broadcast requests and replies to them reach from B to A and from A to B. stupidly look through wireshark on some machine on network A, if there are any broadcasts that have source IP addresses from network B, then on a machine in network B - broadcasts with source IP from network A. if not, that's the point, the provider could kill them.