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

Basj,
Stardock Community Assistant

OK So, I found another post with a user having WoL issues. I'm pleased to say that I learned the Virtualbox network adapter(s) interfere with WoL (with the exception of Magic Packets). 

After uninstalling Virtualbox entirely, I was able to WoL using Multiplicity. Unfortunately now I have to figure out how to make Virtualbox work with Multiplicity as well. If anyone has the how-to, please let me know. 

I know the whole spiel "take it up with Virtualbox support" comes to mind, but I'd appreciate this being worked from both ends if possible. 

I do actually use Virtualbox for some things, including testing Unity games/apps on multiple platforms. I'm not making any AAA titles but I am aspiring to be productive with these tools. 

Any assistance would be appreciated.

Additionally, when I make the secondary machine sleep using the primary's mouse/keyboard, the mouse becomes stuck and the cursor just dies. Until I reboot the secondary machine entirely, the mouse and keyboard do not function properly and the mouse stops responding entirely. So, that's a separate issue to address.

PSA I did install the beta on both machines, which is what brought my attention to the WoL/Virtualbox issue.

Thanks @basj 

OK, so... after more troubleshooting, I still have the following issues. 

1.  I cannot force the secondary to sleep, and stay asleep. PC instantly comes out of sleep mode. 
   
   
2.  Once secondary PC wakes from sleep mode,  Multiplicity "connects" but doesn't actually allow control. I have to kill the Multiplicity service and restart it on the Primary.
3. When sending the Secondary to Sleep mode, the cursor becomes unavailable, and the Primary never gets the cursor restored. I have to manually reboot both machines, or kill the services on both machines to restore my cursor. 
4. WoL with VirtualBox installed is broken entirely. In order to make Multiplicity a viable product for me  I need these two products be friends. 
5. Still getting occasional delayed / sluggish cursor on Secondary.

Hello,

Sorry to hear you are having trouble.

Are both your PCs Win10 version 2004?

There is not a 'force sleep' option in MP.

The latter is known (Internal ref: Mantis:206824)

I have written a batch file that will restart the MP services - does it work for you:
http://sd.stardock.com/Support/Utilities/PurgeAndBats/MP/mpRestart15.zip

Does the batch file also resolve this?

This is almost always the results of one of the PCs under heavy stress, high network traffic, or both.

Sean Drohan
Stardock Support Manager

Greetings. 

I've managed to solve at least SOME of my network issues by replacing one of my switches, and resetting the other. I also went through the trouble of resetting all of the network devices on both machines and then restricting them to wired networks. 
My network map is FiOS wall > FiOS router > Gigabit Switch > Wall > Gigabit Switch > PC

However, I still experience all of these issues when I eliminate the switches, or one switch and connect both to wifi. 

Funny thing is, I get the best connection it seems when one PC is wired and one is wireless. 

Regardless both PCs are now hardwired, and testing with =< 6ms  ping, at gigabit speeds (900+mbps)
 
Both machines have nothing running at startup, and I went through the special effort of switching off some potential network hogs at startup i.e. Origin, Steam, etc. 

Specs for PC1 (Primary) ManyFaceGod
i7 6950x
64 DDR4 2133 (XMP 3200) Corsair Dom Platinum LE
2x EVGA 1080 Ti FTW3 
OS Drive is Samsung SSD 960 EVO 1TB M.2

Specs for PC2 (Secondary) Odin
AMD Ryzen TR 3990x | OC 4.6Ghz
256 DDR4 XMP 3200 Corsair Vengeance
EVGA 2080 Ti FTW3 Ultra
OS Drive is WD Black SSD 2TB M.2

Both PCs are sitting at low~idling temps and are showing minimal usage at the time of troubleshooting. 

That being said at one point yesterday I had Multiplicity working extremely well and I was able to use it to KVM to my secondary machine (Odin) and absolutely smash some fools in CoD: Modern Warfare with no discernible input lag. 

Then suddenly today, as if from a nightmare, input lag plagues me once again.

I've tried resetting every network device in the line, and reset the NICs, cleared DNS cache on both machines, reset ipconfig, checked the firewalls, and double-checked my port forwarding, and at this moment, the input lag is so bad Multiplicity is entirely unusable, even with both PCs plugged in side-by-side on a 4-port switch.

And I manually reset each service and process multiple times to no avail.

I will update upon further testing and I'll give your script a shot. 

I'm pleased to report your script was successful in restoring input speeds to nominal levels. 
I think the signature is a bit much though. 

I plan to plop this on my Stream Deck and potentially my Object Dock. 

Not sure why this script works better than manually resetting the service? Oh well. 

Thanks again. I'll update this thread if I keep running into issues.

That is not in the script I posted

While it should not be needed, I am pleased it works as a work-around.

Incidentally, do you stream often and on what platform (Twitch?)?

Sean Drohan
Stardock Support Manager

My activity on Twitch recently is lacking, but I've been planning on being more active soon.