Multiplicity says I have the wrong passcode when connecting.

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.

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

Please contact support so we can get more information.

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

 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. 

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

 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.

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. 

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. 

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!

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

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.

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.

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.

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

Mine too recently stopped working. I tried changing the pass to numbers only, then ran the purge script on both computers and re-installed. It is working again, but with a strange side effect..........my secondary computer can be on either the 2.4G or 5G connection to my home network and everything works fine. However, the primary computer can ONLY be on my 2.4G network to connect. The moment I switch to 5G I get the wrong passcode error even though it was literally just working. This started for me after the Fall Windows update I finally accepted yesterday. I do not think it is third party software interfering but rather how Windows is handling traffic from 5G networks. I hope you find a solution, I'm on the trial right now and obviously will not purchase if I can't get it to work correctly.

Hi.  I had posted about this in my own thread, but wanted to add my voice to the group in this thread.

Every once in a while (month or so?), Multiplicity suddenly claims the passcode is incorrect, and won't accept it, regardless of what you try.  It's obviously a bogus error alert, as the passcode hasn't changed (and, ultimately, the software will suddenly operate without any protest, as if nothing happened).

For me, I think I usually solve it by rebooting, or just waiting it out.  No idea what triggers it, or why it only lasts for a while.  I wish this would be looked into, as it definitely seems to be some glitch that happens from time to time.

Hello,

Sorry to hear you are having trouble.

As you have pointed out, you absolutely can change it yourself...

There are many suggestions here - of what they did to resolve their issue - I do hope you had the chance to review them all.  Mine were:

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

In particular:

As a test, change them all to:  123456

To see if it is a case or special character issue.

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

Sean Drohan
Stardock Support Manager

found this cause this just cropped up for due to the secondary causing my primary mouse to disappear (for like the 5th time and ive only had the software a week).  A couple restarts of the service on both sides via keyboard (that didnt work and required me to entirely restart pc's) led to this newly found problem now. 

The suggestion to purge your entire install and re-do everything is insane.

I mean cmon guys - its time to go through your software a little more thoroughly.   You charge 100 bucks and ive had 100000x the problems that ive had with mousewithoutborders which is free.

The perk i wanted from this (wol) that mwb didnt, doesnt even work for me (meanwhile it does with every other software ive tried, but i want to avoid using multiple software to accomplish the same thing). 

Already purchased so it is what it is, but i'd expect better from any developer.   This has obviously been happening for years.  

can still seamless right over to it, but the KVM sees it as offline.  sigh

klepp09056,

Sorry to hear you are having trouble.

Exaggeration to make a point I am certain - to showcase your frustration - we get it.

What has - a passcode issue?

Of the handful here that reported a passcode issue, most have reported having found a root cause and/or a solution (Windows Update, network type change, IP instead of hostname, etc).  

As you would suspect, anyone seeing issues has to be diagnosed as these were.  If it is seen to be something systemic - something obviously defective in the app - of course, we want to know that an address it - it just takes time to get there - to figure out what the few have in common that the hundreds of thousands of other installs do not. 

That said and keeping this thread on topic, are you still having passcode issues, klepp0956?  If so, what have you tried from this thread and it still failed?

Sean Drohan
Stardock Support Manager

I wont argue.  a bit of hyperbole sure.   And yes, thank you for realizing my frustration.   Going from having no problems at all, to several in a short time is frustrating and led me there.   but we'll say 5x the problems as going from 0 to having 5 or so pressing issues sounds about right.

Of course mwb doesnt offer wol, and it doesnt offer kvm, so its not apples to apples.   whereas the seamless which it does has worked without fail.   So again, i can be objective.

anyhow - to stay more on topic.  I've tried everything ive found perusing google and the forums here barring a purge or reinstall.  I finally have everything how I want it, and it was working fine with no changes to anything (outside a few service restarts on both sides of the fence to try and bring my mouse cursor back to the primary).   I dont want to have to resort to the nuclear option.   Its not like i have buffer flushing off and had a huge power loss that could have corrupted data or something, this shouldnt happen by itself.

seamless continued to work.

pinging was fine.

the gear icon says it can connect.

actually connecting said "bad password"

tried changing password

tried removing and re-adding the pc

tried disabling/reversing primary/secondary.

restarted pc's

restarted services.

restarted tray icon.

checked windows firewall

via kvm mode it continued to show as offline.   of course somehow, as quickly as it broke - between the time you posted and now it began working again.

I did notice that after connecting to the offending pc, i moused over the multiplicity icon in the tray which greeted me with a crash.  it disappeared from the tray.   kvm still functioned.  seamless still functioned.  it still showed online etc.

so i restarted that pc yet again.  Now its back/working in its entirety.  

Pretty janky i'd say, but its working for now. 

I'd really like to understand why that happens (the breakdown between password/connection), and under what conditions the mouse cursor decides to disappear when seamless'ing back over so as to avoid it in the future until the root can be addressed software side.

this is no fun.  I have a few toddlers, and am increeeedibly busy with work.   Unfortunately im also ocd to a fault, so when something like this breaks i pretty much stop all-else until i fix it.  (imagine my chagrin over the WoL not working lol)

Well,

Well, glad it is working now - even if it's somewhat a mystery how you got there...

If you have issues in the future, we just want to handle one at a time and in their respective thread - I'm sure the reasoning is clear.

If it was not already understood, Multiplicity is a dear product to me personally. It's an under-appreciated product IMHO; one where - if people that have multiple PCs used it just once- they would quickly wonder how they ever got along without it.  I myself could not do my job as effectively were it absent. 

We care about Multiplicity a great deal and even more so for the clients that use it.  Anyone having issues - who might initially curse the product for them - we want to make evangelists for it because their issues were addressed promptly and with care. 

Thanks for your feedback.

Sean Drohan
Stardock Support Manager

I dont disagree whatsoever.   With a bit of polish, and even fewer features added - it ought to be king of the hill and certainly would validate its asking price.

it just needs some love in the bugs/reliability realm first and foremost.

FWIW that is exactly why i get a bit irate over it,  i came into it expecting greatness as ive been a groupy user for ages and my workflow requires it.   I'll never go without.  

I expected, and still do - for it to be the same with multiplicity.   It just seems consistancy/reliability has been a problem and this is with brand new installs as of a week ago.  I do want to continue using it for sure.  already becoming accustomed to not having to wrench my neck in a circle to get to my other pc's

Noted on keeping the topics where they belong.  Thats my bad. 

It is disappointing not knowing what the fix was, but enough hammering back and forth of the switches and it "caught" again i guess.  

I contacted support about this a month after I bought M3.

They launched the new version that month, and said I would need to upgrade to get it working.

I don't think so...

Just tried it again, same results...

Feel free to give me a working version of the software, but I will not be paying for it again.

You own Mutiplicty 3 and have access to the latest version of it - no other person has access to a greater version (one does not exist).

https://store.stardock.com/myaccount/products

Sean Drohan
Stardock Support Manager