Primary computer can't connect to new computer - Passcode is never right even when as short as 4 digits.

from Stardock Forums

Hello,

My Son just got a new computer and I'm trying to set it up.  I can't connect from my computer (primary) to the new computer (secondary).  His is a replacement.  I deleted from Multiplicity his old computer name and added his new one.  Thus the number of computers in use are the same (four (4)).

 

I already checked:

1) Every computer is on the same subnet.

2) Every computer is using Private Network (e.g. I don't get the message about it  being on a public network).

3) I verified the encryption key is the same.

4) I verified the passcode is the same.  I even used a very simple one of 1957.  I even did copy & paste of the encryption key.

5) I verified the versions are the same.  Primary:  Version 3.57 Build 00103.kvmpro  Secondary:  Version 3.57 Build 00103

When I try to connect I get - Passcode is incorrect.  As I say in #4, I used a simple one of 1957.  I did a copy & past of the encryption key.  It still says Computer Offline on the Primary.

 

What's up?  I have 8 other computers and they all work just fine.

 

Thank you.

multiplicity
5,597 views 7 replies
Reply #2 from Stardock Forums Top

Quoting basj, reply 1

Hello,
Sorry to hear you are having issues. Please review this guide : https://forums.stardock.com/486104/multiplicity-support-faq#connectionissues. Report back if you still need assistance.

Thanks
Basj,
Stardock Community Assistant.
End of basj's quote

 

Hello and thank you Basj,

I had already read the FAQ before posting (maybe I should have included this information).

While the two systems do talk, it is ONLY as far as to say the PASSCODE is wrong.  Yet, I made the passcode as simple as 1957 for the secondary and replicated on the primary.

When I had this issue in the past (with PASSCODE), it sometimes was a version difference.  I checked and  both the primary and secondary are on the same version.

I have been using Multiplicity for years (since it was first out) and never have I been so stumped.

OH, one new thing for me.  This Dell computer came with Windows 11.  The Primary is Windows 10 and won't be moving off of 10 (E5-2667 processors).

I would hope the developers of Multiplicity tested Windows 11 secondary and 10 primary.

 

Bertram Moshier

Elemental: Reforged
Reply #3 from Stardock Forums Top

Additional thought:  Given I have 3 other computers connecting fine, why should this one be different?

Reply #4 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 #5 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

If you reverse what is the Primary and Secondary, does it connect then?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #6 from Stardock Forums Top

Quoting sdRohan, reply 5

Hello,

Sorry to hear you are having trouble.

If you reverse what is the Primary and Secondary, does it connect then?

Sean Drohan
Stardock Product Lifecycle Manager
End of sdRohan's quote

Hello,

Thank you, Sean Drohan, for your assistance.

I got my Son's computer (Ramrat) set up as Primary.  It was able to connect to my system (Caitsith).  To do this I:

1) Used the switch in the upper right hand corner.

2) Entered the Product Key.

3) Set up an entry for Caitsith and entered the passcode on the screen.  I didn't change anything else.  I was able to connect from Ramrat to Caitsith.

 

Next I switched the roles back and again when connecting from Caitsith to Ramrat I get a Passcode failure!  Thing is the passcode for Ramrat is simple:  1957

So what I'm seeing is:

Primary: RAMRAT
Secondary: CAITSITH
Result:  SUCCESS

Primary: CAITSITH
Secondary: RAMRAT
Result: FAILURE (Passcode not valid, but its a simple 1957)


FINALLY:  I removed Multiplicity from CAITSITH and RAMRAT and reinstalled.  Yes, I know they both report being on the same version, but ...

After uninstalling and reinstalling it worked, finally.

Thank you for your help,

Bertram Moshier

Reply #7 from Stardock Forums Top

Quoting Bertram_Moshier, reply 6

After uninstalling and reinstalling it worked, finally.
End of Bertram_Moshier's quote

Pleased to hear it.

Sean Drohan
Stardock Product Lifecycle Manager