Multiplicity 4 disconnected using Wireguard VPN

Hi all,

I have upgraded today my Multiplicity 3 KVM Pro to Multiplicity 4 Enterprise. It works fine, and I feel that it's faster then Version 3.

Unfortunatley I have issues to connect to remote PCs on different locations over Wireguard VPN. It worked fine with Version 3. 

It is a private VPN connecting my 2 AVM Fritzbox on 2 locations (home and work). As I mentioned it worked properly by using version 3. 

Pinging remote PCs is successful. I can reach that PC with Remotedesktop Connection from Microsoft. I think Multiplicity causes that problem.

Any ideas? Thanks for your help.

7,223 views 15 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Just to be sure, is the secondary system you trying to connect to also on Multiplicity v4?

Thank you.
Basj,
Stardock Community Assistant.

Reply #2 Top

Yes, all machines are on Multiplicity v4. I can connect with my Laptop (primary) when I'm on the same location; but not on different location using VPN. I've never had not such problems by using v3.

Reply #3 Top

Hello,
I have forwarded 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

+1 Loading…
Reply #5 Top

What does the error message say?

Reply #6 Top

Also, you will want to try creating the connection with the actual local IP of the Secondary, not just use its hostname, Example

Sean Drohan
Stardock Product Lifecycle Manager

 

 

Reply #7 Top

Thak you @Neil and @Sean.

I always use the IP address.

I reconfigured my VPN today and will test from home later to see if it works.

Currently I have a much bigger problem with my setup. Although I am connected to the local network wired, the connection is very slow. Each mouse click takes approximately 15 seconds. No matter which machine. Only one PC is connected each time. If the problem persists, I'll unfortunately have to downgrade to v3, because I didn't have such problems with it.

And sometimes the connection disconnects immediately after it is established, so I have to reconnect several times.

Do you think, purging and clean install would solve that problem?

 

Reply #8 Top

Quoting Mad, reply 7

Do you think, purging and clean install would solve that problem?
End of Mad's quote

Doing it on all MP PCs is always a valid support option.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #9 Top

@Neil

Screenshot of the error is attached below. Reconfiguration of VPN didn't help. 

@Sean

purged all PCs and new installation did not solve the problem. mouse and keyboard are very laggy. It is impossible to work in this condition. Is there anything else I could try or adjust to get it work? 

I rolled back to Version 3 and it works perfect. Is there any chance to work with Version 4? Otherway I think about to ask for refund. :-( 

 

Reply #10 Top


Unfortunatley I have issues to connect to remote PCs on different locations over Wireguard VPN
End of quote

When making that connection are you using (or have you tried) the VPN IP of the remote?

For example, 

-The Primary PC has an active VPN connection.

-The Secondary has a VPN connection

-Thus, both are on the same VPN subnet

-You use the IP of the Secondary VPN connection to create it.  Example:

Sean Drohan
Stardock Product Lifecycle Manager

 

Reply #11 Top

Yes, I always  use the IP-adress, never the name (screenshot below). This because of issues other applications. As I said, there is no problems using the Version 3.

Any issues, any time.

BUT: the main problem is currently, that MP 4 is unusable, because I have to wait 10-15 seconds, till a click of the mouse or pressing a button on keyboard takes effect. This happens by controlling PCs on same location, NOT over VPN.

For example: I click an icon, and see the reaction on the secondary immediatly. But it takes many seconds to see the same displayed on the primary. 

I think, the problem with VPN can be solved. But the issue with that "delayed response" is frustrating.

Reply #12 Top

Quoting sdrohan, reply 10

-Thus, both are on the same VPN subnet

-You use the IP of the Secondary VPN connection to create it.  Example:
End of sdrohan's quote

Just tried now, same error as above: Connection failed due to an unknown protocol error. (3)

Reply #13 Top

The delayed response is probably connections not working in the background and being dropped constantly.

Reply #14 Top

What does it mean exactly? Why do I have any problems by using Version 3? Never had ...

 

Reply #15 Top

Can you veify that, on each PC, the file version for MultiplicityConfig.exe is 4.0.0.4?

Quoting Mad, reply 14

What does it mean exactly? Why do I have any problems by using Version 3? Never had ...
End of Mad's quote

While there are several changes with MP4, it does not eliminate the network itself—some characteristic of it—that is causing issues—issues that we may need to address. 

Is there anything in Windows Event Viewer indicating Multiplicity 4 is crashing?

If you go to your network stack, and remove IPV6 (uncheck it) on each PC, does anything change?

Quoting Mad, reply 11



End of Mad's quote

That IP is a private one, not something I would expect to see for a VPN address - I would think it would be a public address.

WHen the VPN connection is active

-Open a command prompt

-ipconfig

What is the IP of the VPN connection?

Sean Drohan
Stardock Product Lifecycle Manager