Wrong passcode continuous error, laptop failing to connect

Hello,

 

I've been using Multiplicity for over 6 months now, and just recently one of my laptops has all of a sudden gotten these errors:

 

'connect can't be made due to the encryption key being incorrect'

'connection lost because secondary did not respond in time' 

 

Nothing has changed at all, no settings changed, the laptop has worked just fine in the past. Any ideas?

6,862 views 11 replies
Reply #1 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 #2 Top


Hello, 

I've been using Multiplicity for over 6 months now, and just recently one of my laptops has all of a sudden gotten these errors: 

'connect can't be made due to the encryption key being incorrect'

'connection lost because secondary did not respond in time'  

Nothing has changed at all, no settings changed, the laptop has worked just fine in the past. Any ideas?
End of quote

Is the 'laptop' a corporate \ work PC subject to rules by them? If so, is it not an admin account?

What happens when you (re)set the encryption?

Sean Drohan
Stardock Support Manager

Reply #3 Top

Sorry missed this. The laptop is just a personal laptop. Again - it worked for almost a year with no issues at all and suddenly it's been very choppy. How do you reset encryption?

Reply #4 Top

Quoting xerislight, reply 3

Sorry missed this. The laptop is just a personal laptop. Again - it worked for almost a year with no issues at all and suddenly it's been very choppy. How do you reset encryption?
End of xerislight's quote

If it's now just 'choppy', it would not have to do with encryption.  Were you still having encryption issues, you would not be able to connect at all.  However, were the connection so bad, I could see you getting any such errors.

In any event, the best test is to have all PCs connected via ethernet - is that possible?

Sean Drohan
Stardock Support Manager

Reply #5 Top

No, most modern laptops (including the one I'm using here) do not have ethernet. I have 3 laptops and 2 PC's connected. 2/3 laptops and both PC's have no issues ever... it's just this one specific laptop that consistently has problems. For the record: none of the laptops are connected via ethernet, but 2 of them have no 'choppy' issues, and one of them does. 

Reply #6 Top

Quoting xerislight, reply 5

No, most modern laptops (including the one I'm using here) do not have ethernet. I have 3 laptops and 2 PC's connected. 2/3 laptops and both PC's have no issues ever... it's just this one specific laptop that consistently has problems. For the record: none of the laptops are connected via ethernet, but 2 of them have no 'choppy' issues, and one of them does. 
End of xerislight's quote

The other issue that can contribute to poor performance is if the PC in question is getting hammered.

Sean Drohan
Stardock Support Manager

Reply #7 Top

Was this issue ever solved?  I just added a new laptop into my mix of systems and now I am getting constant "connect can't be made due to the encryption key being incorrect" errors despite the encryption keys being set the same and none of the secondaries requiring encryption.

Reply #8 Top

Quoting Kalaxis, reply 7

Was this issue ever solved?  I just added a new laptop into my mix of systems and now I am getting constant "connect can't be made due to the encryption key being incorrect" errors despite the encryption keys being set the same and none of the secondaries requiring encryption.
End of Kalaxis's quote

Please see:

https://forums.stardock.com/486104/multiplicity-support-faq#passcodeerrors

https://forums.stardock.com/490645/page/1/#3724480

Sean Drohan
Stardock Support Manager

Reply #9 Top

Unfortunately, neither of those apply to my situation.  It is not the passcode but the encryption key and I do not have the checkbox selected.

Reply #11 Top

Quoting Kalaxis, reply 10

I am still evaluating the results and if there is a reoccurrence but on the surface, it seems as though the Purging and re-installing steps here on my primary system worked:

https://forums.stardock.com/486104/multiplicity-support-faq#reinstalling
End of Kalaxis's quote

Excellent.

Sean Drohan
Stardock Support Manager