Main computer Multiplicity shows Disconnected

Version 3.6 Build 00105.kvmpro

from Stardock Forums

Hi,
Multiplicity has been tops for years.
I recently got upgraded to broadband on fibre and was issued a new modem/router.
The main computer is data wired in to the router/modem (not wi-fi).
Nothing was changed besides that switch and everything else is working fine.

My MAIN computer Multiplicity icon is now grey and showing (Disconnected).
I have Network set to Private.
I've checked the other computer keys and encryption keys, both on the main computer and secondaries.
Searching old comments I found one Disconnected where the person found a security in settings. I checked mine is still the same. I have not reinstalled Multiplicity, nor changed anything.
I've rebooted several times. I restarted Multiplicity processes, both from the pop-up and from Win.
I unloaded and restarted Multiplicity.
I flushed the DNS cache.

How do I get Multiplicity to re-connect?

Many thanks!!

 

Stardock Software Multiplicity Type: Question
1,506 views 9 replies
Reply #1 from Stardock Forums Top

Hello,

Sorry to hear you are having issues. Please review this guide for connection issue: https://support.stardock.com/space/SHC/1287946260/Multiplicity+Connection+issues+101. Please try it and report back if you still need assistance. 

Thank you,

Basj,

Stardock Community  Assistant.

Reply #2 from Stardock Forums Top

PS:

I have had Bitdefender from a long time back.

MP2Control.exe & Multipl2.exe are both allowed in Firewall settings.

Besides, I have not made any changes to those recently.

ObjectDock - Access shortcuts and frequently used applications from an animated dock.
Reply #3 from Stardock Forums Top

Bitdefender is where I would look first, and not because you changed anything in it.

The standard firewall fix we point people at is MPPortFix, and that only writes Windows Firewall rules. A third party firewall has to be done by hand. So a Bitdefender ruleset that was fine before can still be incomplete now, because what changed underneath it is the network it is making decisions about.

Your whitelist is also shorter than it needs to be. Alongside Multipl2.exe you want MPRDP64.exe, multi2_64, multisrv64 and multiplv64.

Ports are TCP 30564 (service), 30565 (clipboard), 30567 (audio) and 30569 (remote screen, which is the 3.x one, so it applies on 3.6).

If you would rather not add all that blind, turn Bitdefender's firewall off completely for one attempt and see whether the Primary goes green. That tells you whether you are chasing the right thing.

One more, specifically because the router is new. Remove the Secondary connection and re-add it by the Secondary's IP address rather than its host name. A new modem/router usually hands out a different DHCP scope, and name resolution is the piece that quietly stops working while everything else on the network looks completely normal.

Worth rebooting the router itself too, not just the PCs.

Reply #4 from Stardock Forums Top

Hi Basj,

 

Thanks for your suggestion and link to that info.

I've followed it all, checked and double checked all computer settings (none of which were changed) and they all appear OK. Encryption coordinates and the name & password are correct, but still that Secondary computer can't connect.
I have a third (another notebook) which is connecting fine with the Main computer & no settings were changed to make it work OK.

Firewall settings look OK and are the same as my other Secondary computer.
So it appears to be just the one Secondary which is refusing to connect from the Main one.
I have also updated the problem computer to the latest version of Multiplicity.

What can I try next?

Many thanks, Kerry

Reply #5 from Stardock Forums Top

Hello Kerry,

For more details help on your issue, I have forwarded your issue to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience. Thank you.

While waiting, please provide few information.

  1. Windows 10 or 11? and need its full version and OS Build number for all system. Use Winver.exe for these numbers.
  2. Multiplicity full version number installed on all systems.

Thank you,

Basj,

Stardock Community  Assistant

Reply #6 from Stardock Forums Top

Hi Basj,

Many thanks.

Main Computer:

Windows 11
Ver 24H2
OS Build 26100.9168

Multiplicity
Ver 3.6 Build 00105.kvmpro
It's set to automatically update - check weekly
"No Updates found."

 

Secondary Computer  - NOT Connecting
Windows 11
Ver 25H2
OS Build 26200.9168

Multiplicity4 (I just notice it's a later version)
Ver4.07
This is set to check updates weekly and has installed a later version.
No Build data given.

 

Secondary Computer - still connecting
Windows 11
Ver 25H2
Build 26200.9168

Multiplicity
Ver 3.6
Build 00105

I appreciate your support - thanks
Kerry

 

 



 

Reply #7 from Stardock Forums Top

The secondary that will not connect is the odd one out on version. Your Primary is on 3.6, the secondary that still connects is on 3.6, and the one that dropped off is on 4.07.

Multiplicity needs the same version on every machine, and when you update, every PC running it has to run the new installer. Mismatched versions are the most common cause of a connection failing.

Your working secondary is the control test. Same version as the Primary, same network, same new router, still connecting. That is why nothing you checked on the network or firewall side looked wrong.

Two ways back in step. Put the problem secondary back on 3.6 to match the other two, which is the smaller change. Or bring all three up to 4, which is a major version step and depends on what your licence covers, so worth checking before you start rather than after.

Either way, re-enter the encryption key on that machine by hand rather than comparing it and deciding it matches. Upgrading from an older version has a known issue where the key gets reset, and 4.07 is earlier than the build that addresses it.

Hold off on the Bitdefender rules from my earlier post until the versions line up. If the version gap is the cause, that port list is work you will not need.

One last thing. That machine is set to check for updates weekly, which is how it got out of step in the first place. Whatever version you settle on, it needs to be the same one on all three.

Reply #8 from Stardock Forums Top

Many thanks Haalee.

How do I downgrade from V4 to V3?
Your guide only shows how to UPgrade.

I entered the encryption key by hand but it did not revert the version.

Thanks
Kerry

 

 

Reply #9 from Stardock Forums Top

The encryption key is a security setting, not a version control. Entering it by hand will not move a machine from 4.07 back to 3.6, which is why nothing changed.

Downgrading is a clean removal and a fresh install. Do it only on the secondary that will not connect. Leave your Primary and the working secondary alone.

Run the Multiplicity purge file on that machine: https://cdn.stardock.us/support/uploads/Purge_MP-New.zip

Save your work and close everything first, since the machine may restart on its own. Right-click the file and choose Run as Administrator. On Windows 11 you have to pick "Show more options" first to see that item. If you get "Windows is protecting your PC", choose More info, then Run anyway.

Reboot, then install 3.6 and re-enter the encryption key and passcode so they match the other two. Leave every other setting at its default until you have confirmed it connects.

For the 3.6 installer, use the product key retrieval page: https://www.stardock.com/support/productkeyretrieval. It emails the installers and keys to the address that made the purchase. If what arrives is only the current version, say so here rather than installing it.

Worth knowing if you ever go the other way and put all three on 4. The latest released build is 4.08 from January, so 4.07 is behind it. The fix for upgrades resetting the encryption key is in the 4.2 beta and has not reached a released build yet, which is the sort of thing you run into when machines update at different times.