Sometimes KVM secondary PC mouse does not respond to clicks with Multiplicity 4 Pro Beta 1 & 2.

from Stardock Forums

Sometimes, not always, the KVM secondary PC does not respond to mouse clicks.  The cursor ia active and moves as intended, but I cannot click on or select anything on the screen.  If I close the window and re-connect it works normally.  Had this problem in Version 3, same thing now with Multiplicity 4 Pro Beta 1 and 2.  Happens perhaps 1 out of every 4 or 5 attempts.  Otherwise everything is great.

multiplicity
3,353 views 7 replies
Reply #2 from Stardock Forums Top

Thanks Basj.  I'm now on Beta 3 (strange, it is not available as an "update", have to seperately downoad the file and install).  I use Bitdefender which is a bit more difficult to modify the firewall rules, but I think I've got most of them on the Primary conputer, probably have to do it on the secondaries as well(?).  Can only add the executables as exceptions and I've done 8 of them, maybe too many, but not ure which I really need.  Not much carryover from the Windows firewall rules.  So far I have not encountered the problem, so I think we're on the right track.  Do I need to modify the secondary's rules as well?  Starting to work on them, but would like to know which executables I need to add exceptions for.

 

TouchTasks - Access tasks with ease on Windows touchscreens.
Reply #3 from Stardock Forums Top

Hello,

Betas are not official release, that is why it will not appear as an update. As for the rest of your questions, I have forwarded it 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

Reply #4 from Stardock Forums Top

Quoting jlegg4, reply 2

Do I need to modify the secondary's rules as well? 
End of jlegg4's quote

It is always the best choice, yes.

Quoting jlegg4, reply 2

but would like to know which executables I need to add exceptions for
End of jlegg4's quote

On the Primary, for KVM, it would use multi2_64.exe and the Secondary would use multisrv64 and multiplv64.

That said, if you continue to have issues, we are going to ask that you eliminate any 3rd party firewall and work to see that it is solid with Window's native. 

Sean Drohan
Stardock Product Lifecycle Manager

Reply #5 from Stardock Forums Top

Thanks.  Will do and let you know how it goes, so far, so good.

 

Reply #6 from Stardock Forums Top

Well, it's been 3 days now without a glitch, so I'd say the problem is solved.  Unfortunately, since I both updated to Beta 3 and made the firewall exceptions I don't know for sure which cured the problem, though I suspect it was the firewall.  I'll let you know if the problem returns, but for now, I'd asy it is solved.  Thank you VERY much for stepping in and helping out and for a fantastic, very usefill application.  Makes life much easier!

 

Reply #7 from Stardock Forums Top

Quoting jlegg4, reply 6

Thank you VERY much for stepping in and helping out and for a fantastic, very usefill application.  Makes life much easier!
End of jlegg4's quote

Pleased to read and you are most welcome.

Sean Drohan
Stardock Product Lifecycle Manager