Multiplicity 4 pro: "One time passcode is wrong"

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

Thanks!

Hi hishamzr,

Thanks for posting.  There are some things you'll want to make sure are setup correctly:

1. First, make sure you have the latest version of Multiplicity 4 on both Primary and Secondary computers. 

This can be checked by going to the following file path: 

C:\Program Files (x86)\Stardock\Multiplicity

Then right click MulticityConfig.exe and select Properties, then find the "File version" under the Details tab:

If the file version is not the same on both computers, you can retrieve the latest version to download and install it on each from this link:

https://www.stardock.com/support/product-key-retrieval

2. Once you're sure you have matching versions of Multiplicity 4 on each computer, then ensure the Encryption Key matches on all computers (see screenshot below).  

3. You'll also want to make sure the passcode on the Secondary is the same passcode used to add the computer as a KVM connection.

The Encryption Key and passcode can each be set from the Security tab on both Primary and Secondary:

Please let us know if these steps help to resolve the issue.

Best regards,

Adam McGuinness
Stardock Customer Support Specialist

Hi Adam,

Thank you for the information, I did all that, but it did not help.  If the passcodes do not match I get a different error. Anyway the seamless KM works, only the KVM does not. When I do test connection, it says it is OK, but when I try to connect I get the error "One time passcode is wrong"

I checked the version, and both are the same, actually newly installed after using purge.

what is this One time passcode it is asking for, I am using Multiplicity pro for many years, and I never got this error, only after upgrading to ver. 4.

Regards,

Hisham

I can understand the confusion but you seem to be thinking you need this set (and have set it)

With that set, you likely dont see that the KVM remote you are connecting to has a passcode prompting (what you would tell the Primary user to use to connect).

Uncheck that and it should be fine.

Sean Drohan
Stardock Product Lifecycle Manager

It is unchecked, and the problem is still there!

Regards,

Hisham

Do any of the computers have more than one network adapter or more than one up address per adapter?

No.

It used to work with ver 3.

If you run the purge on both PCs, install, and set up from scratch, does it work then

https://support.stardock.com/space/SHC/1347158073/Multiplicity+purging+and+re-installing

Sean Drohan
Stardock Product Lifecycle Manager

no, I did that (with purge)  twice!

PLEASE HELP!!!!

Can you try the latest beta of Multiplicity available on your downloads on the stardock store as it adds in information on what it is trying to connect to and has some connection changes.

Hello,
I have forwarded your problem/question again 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

Thanks!

I installed the Beta version and it did not solve the issue.

Can you record the issue while its happening, upload it to a cloud drive, and post a share link to it here?

Sean Drohan
Stardock Product Lifecycle Manager

The recording:

https://www.dropbox.com/scl/fi/ozkuho476vdsjth8ahqdd/ScreenCaptureProject3.mp4?rlkey=tf7490cn7ayo32pz65y5ubtb2&st=qe9lu662&dl=0

Hi hishamzr, 

I haven't been able to reproduce this.  Just to be extra thorough, when you installed the Beta, can confirm you have installed this on both your Primary and your Secondary computers?  If so, another important thing to test what the issue here is, is to see if this occurs with your Firewall turned off.  

If it remains, can you possibly show us your process of removing this connection and then re-adding it?  And are you able to check if it happens after you've reset your settings back to the defaults?  Would like to isolate the entire reproduction steps of the issue, if possible, including all Security Settings you're using in Multiplicity on both computers.

Best regards,

Adam McGuinness
Stardock Customer Support Specialist

Just to be extra thorough, when you installed the Beta, can confirm you have installed this on both your Primary and your Secondary computers?

Yes

If so, another important thing to test what the issue here is, is to see if this occurs with your Firewall turned off.

Yes 

The seamless KM works flawlessly, the problem happens when I try to connect with the KVM

 

If it remains, can you possibly show us your process of removing this connection and then re-adding it?  And are you able to check if it happens after you've reset your settings back to the defaults?  Would like to isolate the entire reproduction steps of the issue, if possible, including all Security Settings you're using in Multiplicity on both computers

I did that many times, including using purge and reinstalled on both PCs.

I am not new to Multiplicity.

I am considering going back to Multiplicity 3 pro, this is frustrating.

Hi hishamzr,

Thank you for exploring these possibilities.  I understand the frustration, but isolating even basic variables is crucial for reproducing/troubleshooting the issue. We greatly appreciate your patience.

If you're open to it, could you please also confirm that the IP address shown in the KVM connection window matches the correct IP address on your Secondary? If you haven't already, you can run the ipconfig command on the Secondary. If the IP doesn’t match what Multiplicity detects on your Primary, this information would help us pinpoint the issue.

Best regards,

Adam McGuinness
Stardock Customer Support Specialist

Yes, IP is the same

We seem to be running out of recommendations for what this could be and we cannot reproduce it nor do we have any other reports of it.

If you make the current Primary a Secondary (deactivating in the process) and the current Secondary the Primary, can you reproduce this?

Sean Drohan
Stardock Product Lifecycle Manager

I was not able to activate it on the second computer, got a message, cannot connect to activation server.

There is an offline activation method and detailed in the error message. 

Sean Drohan
Stardock Product Lifecycle Manager

I tried the offline, it did not work!