Can't connect from Primary to Secondary for KVM

from Stardock Forums

I have separated home and office devices via different subnets. Home subnet is 10.0.0.X (secondary PC) and office subnet is 10.1.0.X (primary PC). I can successfully ping and remote desktop from my secondary laptop to primary PC.

But I am not able to connect from primary to secondary via multiplicity. Connectivity is like this below. When I traceroute, from primary PC I successfully hit till WiFi Router's WAN IP. I have configured port forwarding from primary PC IP to secondary laptop IP to allow incoming traffic from WAN port to reach secondary laptop IP.

Connection Setup:
Secondary Laptop -> WiFi router -> Firewall Router -> Unmanaged Switch -> Primary PC.

My question is is it mandatory for both primary and secondary PCs to be in same subnet?

How likely it is for me to have successful connection on Multiplicity once I can ping from primary PC to secondary laptop successfully?

Do you see any issues with my setup in terms of Multiplicity connectivity between primary and secondary devices?

multiplicity
4,607 views 5 replies
Reply #1 from Stardock Forums Top

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

Reply #2 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

I have separated home and office devices via different subnets.
End of quote

That is why it is not working.

I have configured port forwarding from primary PC IP to secondary laptop IP to allow incoming traffic from WAN port to reach secondary laptop IP.
End of quote

The best you may be able to hope for in resolving this is to ensure that the MP ports are also mapped:

Rule Name Port/.exe
Multiplicity Service 30564
Multiplicity Clipboard 30565
Multiplicity Application (clipboard) Multipl2.EXE
Multiplicity Audio Service 30567
Multiplicity Remote Screen Service 30569 (For Multiplicity 3 only)
Multiplicity Application (Remote screen control
MPRDP64.EXE (For Multiplicity 3 only)

And that you are using the IP and not the hostname, ie:

I cannot guarantee it will work, however.

Sean Drohan
Stardock Support Manager

WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from Stardock Forums Top

Thanks Sean.

Yes, those ports are open on both Draytek and ASUS routers for traffic from Primary to Secondary multiplicity clients. Should I also enable port forwarding from secondary to primary multiplicity client IPs ?

Yes I am only configuring with IP as with name it complains. With IP it doesn't complain at the time of setting it up. It is when I click on GEAR symbol on Configure popup that is where I get that error. And the taskbar tray icon remains (disconnected).


I can easily ping either way (primary PC to secondary laptop and vice versa).
The error I get on primary PC is also that "Multiplicity was able to connect to the computer, but your passcode is incorrect." So multiplicity app was able to connect to secondary laptop. But it complains about passcode. It looks like the issue is not at network layer L3 or L4. It more likely might be issue at application or session layer where applications on both primary and secondary are not properly able to talk with each other.

I tried uninstalling both apps and reinstalling with PC restart at both ends, but this has not changed anything. Same error keeps showing.

Appreciate your help with this as everything else in network is working perfectly except the Multiplicity Primary to Secondary laptop communication. And it is very important part of my workflow to keep copying files back and forth and keep managing secondary laptop with primary PC mouse and keyboard.

It will be great help.

Reply #4 from Stardock Forums Top

Happy to say that the problem is solved.

I think the problem got resolved by removing "Only allow connections from the subnet this computer is on" on Secondary Multiplicity client's Security settings. As soon as I removed that, the connection started working. Which also coincide with the observation that failure is at session or application layer and not at network layer.

It is very basic setting and I must have picked up quickly at first glance, but somehow missed it.
This also means the software works exactly as designed.

I confirm also that both PC can seamlessly control each other's monitor in either way Primary - Secondary setup.


Thanks for your help and kind support.

Reply #5 from Stardock Forums Top

Quoting gosahd, reply 3

The error I get on primary PC is also that "Multiplicity was able to connect to the computer, but your passcode is incorrect."
End of gosahd's quote

Then it would be natural to ensure they are correct.  Please see::

https://forums.stardock.com/486104/multiplicity-support-faq#passcodeerrors

Sean Drohan
Stardock Support Manager