Why does a host, receiving an address via DHCP, not have access to a DHCP/DNS server?

Question

Computer networks

There is an office 192.168.1.0/24 hidden behind a microtic (let it be 6.19) through which (between them there is also a squid for 80 and 443, but this is not relevant) he goes to the Internet.
There is a data center in which ESXi 5.5.0 1331820 is installed, on which a terminal server and mikrotik x86 6.19 are deployed. (On ESXi there are two virtual switches, in one there is a physical network card (Internet) and the first port of the Mikrotik, and in the second the second port of the Mikrotik (internal network) and the port of the terminal server) Between OVPN Mikrotiks in ethernet mode, local interfaces and tunnels are assembled into a bridge. On the terminal, the address from 192.168.1.0/24 - everything works. Traffic is running.
There is also a data center in which ESXi 5.5.0 1623387, and the rest is the same as in the first data center. Traffic is not running.
Or rather, it doesn’t go at all, you can get a DHCP address from 192.168.1.0/24 to the terminal server, well, or through the winbox you can see (but not connect) two microtics, but that’s all. Ping dhcp server - timeout (DHCP lives with DNS and domain controller at 192.168.1.1), everything except broadcast traffic - silence. From Mikrotik from the second data center, all 192.168.1.0/24 is available.
Firewall rules were disabled. During the first install, Mikrotik was exported from the first hypervisor and deployed to the second one. Then on the second, reset the conf and set it up by hand. Then install Mikrotik manually with subsequent configuration. The result is the same.

Answer 1

and the route is from the grid 192.168.0.0 192.168.0.255 to 192.168.6.0 static? otherwise your network does not know about this addressing in its subnet, see route print on the server that sees this network and add it on other computers or build routing on Mikrotik and also to addresses 192.168.1.0