As WW says, there more people who have the same problem.
It is not solved yet. However there a couple of things you try.
Add to /etc/samba/smb.conf the following in the first section:
domain master = yes
preferred master = yes
local master = yes
The statement - domain master = yes - will force your receiver to be the master for samba. This is fine when you have not defined somewhere else in your private network another samba master. But if you have done that, you will know it, because you have added that statement to that linux machine.
After adding these statements restart samba on your receiver with the command:
/etc/init.d/samba.sh restart
You do this in a telnet window (DCC is OK)
Doing this, has improved the situation with several users. In my own case the situation improved in so far that the error occurs now much less often. And restarting samba cured the problem in each case.
It remains a problem, but at least you can correct it when it occurs.
You can also check the file /var/log/log.smdb from your receiver. This should not contain any errors.
In case there are errors, try restarting samba again with the above statement.
Willy
Edited by doglover, 14 November 2017 - 13:53.