This has continued and gotten to the point now that any time one of the computers restarts then I have to change the passcode in order  for them to reconnect with each other properly.

I just noticed a little while ago (after a reboot of the primary) that I could even retype the same passcode, save and then it can connect. So it'd seem that changing it isn't required, it's re-saving it that does the trick.

No, I've not messed with any of the beta versions.

This bug is still present in 4.05 Pro.

I've been keeping an eye on this thread for months and it's done no good. Those canned responses are really not helpful at all.

Hello,
I have forwarded your problem/question again to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience. Thank you.

Basj,
Stardock Community Assistant

No, it's always been a problem for me on Multiplicity 4 Pro since I installed it back in February. I've run the usual gambit of trouble shooting steps like uninstalling, clearing out all the files, reinstalling, updating (multiple times now through multiple versions). I ran 3 relatively fine for years. And as I've said already in this thread you don't even need to change the passcode. Every time any of the machines reboots, I have to go into Multiplicity on the main and re-save the passcodes of all the connected computers. Multiplicity will even claim that they're connected, but you can NOT access the other machines until you re-save the passcodes.