kyouhyung

Thanks, the problem is now gone, Before your reply, I also tried using the MP Purge tool. I wonder if that also had something to do with fixing the problem.

Hi, I followed the instructions in the link, but the problem still persists. I have two Multiplicity licenses; one KVM and one KVM Pro. Is it possible that the activation server is somehow confused because of this? I made sure the correct computers are activated with each licenses, and my downloads page shows accordingly.

Multiplicity occassionally displays an error like this on the screen. I have a valid and activated license for Multiplicity KVM. While the software still works normally, this error dialog is becoming quite annoying. Please help me fix this.

I have two computers set up in seamless mode, and I want to set up a hotkey to quickly toggle to and from one and another. It looks like you can only set up hotkeys to change to a specific computer. Is it possible to set up a hotkey as my description? Also, it would be nice to be able to set up a hotkey to switch to computer on "TOP" and "BOTTOM", in addition to left and right that are currently available.

[quote who="sdRohan" reply="4" id="3795095"] To be sure of that, try using this on each MP PC: https://cdn.stardock.us/support/uploads/MPPortFix.zip [/quote] Hi, it turned out to be the firwall issue. They were configured correctly as per the manual, but the Connectify network was configured as a public network, hence the connection issue occurred. I have opened the public access of the Firewall rules for the Multiplicity for the time being until I find a way to c

Thanks for the reply. Shouldn't the computers 192.168.100.1 and 192.168.100.2 considered to be in the same subnet? I'm trying to connect from ~100.2 to ~100.1

This is a diagram of the setup I am having trouble making connection to the target computer in this setup. The workstation sits in the office mostly in headless configuration, and I use my laptop as a terminal to control the machine. The ports and firewall settings have been double checked, and all the networking between the workstation and the la