Recent issue with new secondary PC
Stardock Forums
Hi. I've been using Multiplicity for several years, and generally it has worked fine.
Recently, I have replaced one of the secondary PCs with a new one, and although Multiplicity ultimately works, it seems to struggle and require several attempts. I'll try and provide you with as much detail as I can.
Typically, this is the sequence of events:
From the host PC, Multiplicity says it successfully connects to the secondary. Sometimes the video in the window (KVM) is black. If this is the case, I generally close the window, wait a bit, and then open a KVM window again. Sometimes it's black, but sometimes I'll have the desktop of the secondary computer, but the mouse is invisible (yet does interact with desktop items as I invisibly hover over them).
Another window close, and reopening after a bit of time, and if the same situation doesn't happen, what I often get is the mouse pointer being visible, but not interacting with anything (can't click anything, items do not react to mouseovers, etc).
Usually after another window close, wait and window open, I'll get the proper functionality.
This is not always the sequence of events Sometimes it'll just be some of these, or all, or things hook in on first try (I think).
This same setup previously worked okay with the older secondary PC.
Originally, I thought it might be an Ethernet issue, but that doesn't seem to be the case (and I remedied any issues that would have affected that). The PCs are networked together, connected directly to the latest version of the Bell Fibe 1.5gig modem.
So, it seems it is taking quite a while (or multiple attempts) for Multiplicity to hook together the two PCs (mouse, video and keyboard data transmission), even though the 'Successfully Connected' message appears quickly each time, and even testing the connection using the Multiplicity control panel always seems successful.
I played around with various settings, and I think I may have improved on some aspects, but the 'takes multiple tries to ACTUALLY connect, despite Success alert' issue still seems present.
I'm hoping someone can advise me on what to check/try. The new secondary PC is new, as is the Multiplicity install on it. Both primary and secondary software are updated to the latest version.
