My guess is that it is related to the master browser table somehow.
Basically, SMB protocol elects a “master browser” from the list of available servers, and that server supplies the list of network resource supplying servers. When the “network” is queried, it is really asking these questions on the wire:
[client–broadcast] Who is the master browser?
[master browser–broadcast] I am!
[client-- to master browser] Give me a list of resources in this workgroup.
[masterbrowser-- to client] This is my list.
I have noticed that there can be issues getting windows hosts to stop being the master browser/get windows hosts to accept a master browser that is not a windows server host— and in this circumstance, getting the windows host master browser to accept SAMBA hosts as service hosting devices.
I dont really want to call malfeasance on microsoft over it, but I haven’t been able to properly enroll a netbios named SAMBA client since windows XP.
I always just static IP the devices, and connect to them by IP address.