Search
Forum Home | Sign Up | Lost Login?
Elltrain
Join Date 04/2009
0

Multiplicity says I have the wrong passcode when connecting.

September 22, 2017 4:38:14 PM from Stardock ForumsStardock Forums

Hi,

 

My Multiplicity software stopped working, after working perfectly fine for months.  I get the message: 

"A connection to DESKTOP-2R66LR4 cannot be made as you have the wrong passcode.  Multiplicity will try to reconnect in the background..."

The thing is, the passcode is correct.  It was correct before, and I have changed it several times to make sure.  I have reinstalled the software on both computers multiple times.  I have disabled Windows Firewall.  I have tried nuking all references to Stardock and Multiplicity from disk and registry (yet the software still pops up with memory of the previous settings), reinstalling, and trying again to no avail.

Both computers are on the same network.  When I click configure from the primary, I get the "multiplicity was able to successfully connect to this computer." message.  There is a different message if the passcode is wrong:

https://imgur.com/a/x6B3a

 

I have not changed the encryption key, which is the default "CHANGEME" on both computers.

Please help.  I rely on this software for my productivity at work.

Search this post
Advanced Search
Subscription Options
Reason for Karma (Optional)
Successfully updated karma reason!
Reply #1
Elltrain
Join Date 04/2009
0
September 22, 2017 4:45:03 PM from Stardock ForumsStardock Forums

I just switched the computers, such that my secondary is primary and vice versa.  Software works fine when I do that.  This is not an option for me, though.

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #2
roodyjs1
Join Date 06/2017
0
September 22, 2017 7:28:38 PM from Stardock ForumsStardock Forums

I am having the same problem. Have used Multiplicity to control remote microPC with no issues. All of a sudden, "wrong" passcode error, though I have changed nothing. Could be due to a Windows 8.1 update I did recently.

 

Post if you find a solution.

 

Jim

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #3
Island Dog
Join Date 06/2003
+922
September 23, 2017 1:22:54 PM from Stardock ForumsStardock Forums

Please contact support so we can get more information.

http://esupport.stardock.com/index.php?/Tickets/Submit

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #4
CStuber
Join Date 05/2013
0
October 10, 2017 6:17:57 PM from Stardock ForumsStardock Forums

 I just started experiencing this same thing yesterday and it has continued into today. Since I didn't see any resolution, I've opened a support ticket. 

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #5
cmwilkerson
Join Date 05/2006
+1
November 17, 2017 8:59:14 AM from Stardock ForumsStardock Forums

Same here. Was working for weeks then after a windows 10 update it decided to stop connecting claiming I am using the wrong passcode.

I am not the passcode is the same as always and I can see it on both computers.

Uninstall and reinstall does not help. It would be nice if Stardock allowed the user to simply change the darn passcode themselves!!!

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #6
sdRohan
Join Date 10/2012
+92
November 21, 2017 11:08:20 PM from Stardock ForumsStardock Forums

Quoting cmwilkerson,
reply 5

Same here. Was working for weeks then after a windows 10 update it decided to stop connecting claiming I am using the wrong passcode.

I am not the passcode is the same as always and I can see it on both computers.

Uninstall and reinstall does not help. It would be nice if Stardock allowed the user to simply change the darn passcode themselves!!!

This:
https://forums.stardock.com/486104/Multiplicity-Support-FAQ#passcodeerrors

And if not, this:
https://forums.stardock.com/486104/Multiplicity-Support-FAQ#reinstalling

 

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #7
sohuntress
Join Date 03/2012
0
November 27, 2017 4:23:13 PM from Stardock ForumsStardock Forums

 Neither of the links in the post by sdRohan dated November 21, 2017 at 10:08:20 PM are working for me.

I am experiencing the same problem as Elltrain. Primary and secondary computers are both Windows 10, and both are up-to-date in terms of Windows updates and drivers. Multiplicity 3.44 KM has been working fine on them up until today, although I have not actually tried to use Multiplicity on this this pair for several days, or perhaps even two or three weeks. Was working fine the last time I tried.

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #8
ledfortr
Join Date 08/2004
0
November 28, 2017 2:17:04 PM from Stardock ForumsStardock Forums

Hey all, the very moment I installed the Microsoft "Fall Creator Update", this error started to happen for me as well.  Can everyone confirm the same thing?  I assume microsoft did something different in their firewall implementation.  

 

I can't find a work-around. 

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #9
ledfortr
Join Date 08/2004
0
November 28, 2017 2:27:41 PM from Stardock ForumsStardock Forums

I got it to work!!!!! I removed my system from the primary and added the secondary through IP address, not name.  BINGO!  Up and running.  I hope this helps. 

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #10
dragon013
Join Date 08/2001
0
May 10, 2018 12:05:16 PM from Stardock ForumsStardock Forums

Sorry, know this is an old thread, but damn-it all, this is a real problem. I have a laptop as my primary computer, and an old desktop as my secondary (old meaning two years, maybe). I have entered the same passcode in each, I installed Multiplicity on both computers from the single file I downloaded -- i.e. no mismatched version issue. This is just stoopit! 

Oh, FWIW, I can ping each computer from the other using both the IP and the computer network names. 

Please tell me how to fix this!

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #11
sohuntress
Join Date 03/2012
0
May 10, 2018 12:44:29 PM from Stardock ForumsStardock Forums

The fix mentioned by ledfortr on 11/29/17 has worked for me sometimes, but not always. This is still an ongoing problem for me.

The info mentioned by sdRohan on 11/21/17 at https://forums.stardock.com/486104/Multiplicity-Support-FAQ#passcodeerrors has not helped.

I have not yet tried a purge and reinstall, which sdRohan pointed to here: https://forums.stardock.com/486104/Multiplicity-Support-FAQ#reinstalling

 

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #12
dragon013
Join Date 08/2001
0
May 10, 2018 7:31:27 PM from Stardock ForumsStardock Forums

I did the purge, and a reboot (better safe than sorry), on both machines. I then installed on the primary machine, and configured (encryption key, passcode, etc.). Using the physically same executable, I installed on the secondary machine, and did the minor configuration. 

It worked! And has continued to work through several reboots of my primary machine (I'm a developer and reboots seem to be part of the game).

Hope this helps.

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #13
sohuntress
Join Date 03/2012
0
May 21, 2018 4:51:26 PM from Stardock ForumsStardock Forums

I have now done the purge and reinstall on both my primary and secondary computers and that seems to have resolved the problem. However, after doing all of that I also had to set the Network Profile (I'm running Windows 10 on both machines) to Private on the secondary computer before things actually started working. But running a Private network profile on both computers seems to be required for Multiplicity to work in the first place.

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #14
ledfortr
Join Date 05/2016
0
October 10, 2018 1:49:08 PM from Stardock ForumsStardock Forums

Hey guys, i had this problem again .  I was able to get it working after a couple of secondary reboots.  I didn't do a flush.  I did try to delete and re-add the secondary.  I also switched from wired to wireless on the secondary and tried to connect via the IP of the interface.  None of that worked.  It finally worked again after second reboot. 

 

I honestly can't work without this software, does anyone know of something less buggy? It seems like once every six months something goofy happens like this and takes me an hour to get sorted.  Any help would be greatly appreciated.

Reason for Karma (Optional)
Successfully updated karma reason!
Reply #15
sdRohan
Join Date 10/2012
+92
October 10, 2018 3:35:28 PM from Stardock ForumsStardock Forums

Quoting ledfortr,
reply 14

Hey guys, i had this problem again .  I was able to get it working after a couple of secondary reboots.  I didn't do a flush.  I did try to delete and re-add the secondary.  I also switched from wired to wireless on the secondary and tried to connect via the IP of the interface.  None of that worked.  It finally worked again after second reboot. 
 

I honestly can't work without this software, does anyone know of something less buggy? It seems like once every six months something goofy happens like this and takes me an hour to get sorted.  Any help would be greatly appreciated.

Very glad you were able to get it to work. We would indeed too like to know what 3rd party software is interfering with MP.

------------
Sean Drohan
Stardock Support Manager

Reason for Karma (Optional)
Successfully updated karma reason!
View all recent posts
Mark all posts as read Delete cookies created by the forum Return to Top
Stardock Forums v1.0.0.0   #108492   web02  Server Load Time: 00:00:00.0000735  Page Render Time:
Facebook Twitter YouTube Google+