The default config works, so that is not the problem.
It is possible that some clients don't work with the default config, as they try to use SMBv1 or an old NetBIOS connection (on port 139), and this is all disabled in recent samba versions (and in Windows) due to security reasons. And with some you have to specify that you want to use SMBv2 to connect (some receivers with older kernels have this requirement for example).
But Windows simply tries all protocol versions available, so that is not relevant for Windows.
Do you see the receiver in Explorer Network? If so, do you get the error when you click on it? If not, when do you get the error?
Does Windows see network connection as "Home" or "Public"? If not "Home", the Windows Firewall will block all SMB connections.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.