Unable to connect to SMB2 share by short name?

Question

FreeBSD

Good afternoon!
There was a problem connecting smb2 network shares on Windows 10 Pro by short name.
There is the following infrastructure:
A server with FreeBSD5 (ip - 1.1.1.1) on which SMB2 spheres are raised, DNS, DHCP, WINS
DHCP gives, in addition to the standard DNS parameters, a suffix, and the WINS server address
In this option, everything works. That is, a Windows client can connect to the network folder both \\servershare and \\servershare.domain
As part of the LAN upgrade, the DHCP role was transferred to a piece of hardware from Mikrotik
On DHCP Mikrotik is specified as DNS, WINS - 1.1.1.1 and DHCP option 15 - required DNS suffix. (By the way, the DNS suffix was also specified in the Domain option)
The client receives all DHCP options.
"servershare" resolves but fails to connect to \\servershare while connecting to \\servershare.domain correctly.
I don't know where to look next. Unfortunately, it is impossible to abolish the old ball, at the moment.

Answer 1

try not to hand out the Microtome any options 15. just specify

DNS, WINS - 1.1.1.1

everything else should be done by your FreeBSD5.

Answer 2

There are not many clients, but I would not like to manipulate end customers.
I did not try to add to lmhosts. I'll try.
The option when only DNS, WINS is specified on 1.1.1.1 on DHCP microta, unfortunately does not work.
Perhaps it should be mentioned that microt shares networks, namely:
SMB,DNS,WINS - 1.1.1.1
Client - 2.2.2.2