@fg2001
This is an erratic problem. Timing issues are frequently at the root of erratic behaviors...ipso facto, timing is most likely "a" if not "the" probable culprit. Different hardware configurations frequently lead to variations in timing. This issue cannot
be solved by the users. It is an issue that must be addressed within the Windows network plumbing which only MS can do.
The best that can be accomplished for now is to "kick" the FDResPub service whenever a machine logs on or wakes up. Hence, the workaround.
As a side note: It would be very interesting to know if networks that contain/utilize a WINS server exhibit this issue. I do not have access to a Windows Server (Windows 10 Pro does not provide the WINS service) and cannot test against this. If anyone
out there does have a WINS server on their network...it would be at least interesting to hear if this issue occurs on a server based network.