Failed to connect to another PC

I had a subscription to version 3 now I purchased a subscription to version 4 when I go to install it the primary computer cannot connect to the secondary computer ... I followed the various procedures that are indicated on your site but I always have the same problem of no connection ... I tried via cmd to do a ping and it's ok ... I also tried to format the PC but it cannot connect .... clicking on the test button gives me an error kindly help me .. thanks

12,393 views 16 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Did you try uninstall Multiplicity v3 first from all your system, reboot and install Mutliplicity v4 on all of them and try connecting again?

Thank you.
Basj,
Stardock Community Assistant.

Reply #2 Top

I had already uninstalled version 3 on both PCs and then installed it

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 #4 Top


I had a subscription to version 3 now I purchased a subscription to version 4 when I go to install it the primary computer cannot connect to the secondary computer ... I followed the various procedures that are indicated on your site but I always have the same problem of no connection ... I tried via cmd to do a ping and it's ok ... I also tried to format the PC but it cannot connect .... clicking on the test button gives me an error kindly help me .. thanks


This is the best resource available for troubleshooting this issue:

https://support.stardock.com/space/SHC/1287946260/Multiplicity+Connection+issues+101

Sean Drohan
Stardock Product Lifecycle Manager

+1 Loading…
Reply #5 Top

I followed the procedure you indicated but the problem of no connection always remains

thanks

Reply #6 Top

Make sure you have set the same encryption code on both ends

Also make sure both ends are running v4 as v4 will not connect to a v3 client.  If you uninstalled v3 first did you also reboot before installing v4?

The firewall may need adjusting if you use a different firewall too.

+1 Loading…
Reply #7 Top

the procedure I did:

I uninstalled v3 on both PCs, restarted both PCs, installed the same v4 version on both PCs ... it gave me an error and I wrote on the forum

(You may need to change the firewall even if you use a different firewall) what should I do?

Reply #8 Top

Quoting Peppe65, reply 7

the procedure I did:

I uninstalled v3 on both PCs, restarted both PCs, installed the same v4 version on both PCs ... it gave me an error and I wrote on the forum

(You may need to change the firewall even if you use a different firewall) what should I do?

I suspect the error you mean is this

If not, what error?

If you tried ALL of the options in the link I provided, including the port fix batch file, the next step is to eliminate any 3rd party app that could be causing the connection failure.  You can do this by doing a 'clean boot' on BOTH PCs

https://support.stardock.com/space/SHC/1346601039/Multiplicity+Clean+Boot

Once under the clean boot conditions (which MUST include being under a new Windows Administrator account - detailed in the documentation), please try again. 

Sean Drohan
Stardock Product Lifecycle Manager

+1 Loading…
Reply #9 Top

I'm disappointed .. I followed your instructions step by step but I don't understand why it doesn't work

Reply #10 Top

Quoting Peppe65, reply 9

I'm disappointed .. I followed your instructions step by step but I don't understand why it doesn't work

If either connection is Wireless, try connect both via ethernet and ensuring they are both on the same subnet.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #11 Top

as you can see from the photo in the primary PC I put 49 as the final number while in the secondary PC I put 50 as the IP and the subnet is the same

 

Reply #12 Top

just for the sake of communication .... I uninstalled the v4 version and reinstalled the v3 on both PCs and everything is working

at this point I ask you why? I hope for a solution from you

thanks

Reply #13 Top

Quoting Peppe65, reply 12

just for the sake of communication .... I uninstalled the v4 version and reinstalled the v3 on both PCs and everything is working

at this point I ask you why? I hope for a solution from you

thanks

Try disabling IPV6 on each PC with V4 installed on each PC, please.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #14 Top

Microsoft strongly recommends against disabling IP6.

Reply #15 Top


Microsoft strongly recommends against disabling IP6.

Quoting sdrohan, reply 13

Try disabling IPV6 on each PC with V4 installed on each PC, please.

It was a test in a process of elimination from several months ago.

Sean Drohan
Stardock Product Lifecycle Manager

+1 Loading…
Reply #16 Top

Understood. It did not, by the way fix my symptoms when I tried it. I'm not sure what fixed the problems frankly because I ended up rebuilding my Win11 install for a second time yesterday and this round it worked without a hitch from the beginning. I do wish I knew what broke it before so I could share the example, but alas...