Primary always show "disconnected" even if swapping Primary/Secondary roles between PCs

No matter which PC i set as Primary, it always shows disconnected. The secondary always shows connected.  I can switch roles between PCs and whichever is secondary shows connected and whichever I set to Primary always shows disconnected.  I have uninstalled/reinstalled on both PCs multiple times and rebooted between installs.

6,995 views 9 replies +1 Loading…
Reply #1 Top


No matter which PC i set as Primary, it always shows disconnected.
End of quote

A Primary will show 'disconnected' if no 'Seamless' PC are connected.  Are you using Seamless connections or KVM?

If you are using Seamless, and still see that, are you getting that indicator (disconnected) but can still use Seamless (can transition to them)?

Sean Drohan
Stardock Support Manager

Reply #2 Top

Thanks Sean.  I am using Seamless on both the primary and secondary.  I cannot connect to the secondary (transition to it).  However, at one point yesterday, it was saying that it could connect but that I had the wrong passcode (I did not).  I rebooted both PCs and still couldn't connect.  I changed the passcode and still received the same wrong code error.  I get same issue if connected by name or just IP.  I have even run the purge script on both and done fresh installs, still no connection.

 

Reply #3 Top

Quoting jbe117, reply 2

Thanks Sean.  I am using Seamless on both the primary and secondary.  I cannot connect to the secondary (transition to it).  However, at one point yesterday, it was saying that it could connect but that I had the wrong passcode (I did not).  I rebooted both PCs and still couldn't connect.  I changed the passcode and still received the same wrong code error.  I get same issue if connected by name or just IP.  I have even run the purge script on both and done fresh installs, still no connection.
End of jbe117's quote

As a test, change he passcoded to something easy on both PCs, 123456789 for example, and try again.

Sean Drohan
Stardock Support Manager

Reply #4 Top

Thanks again, Sean.  I wasn't specific enough above.  I did make it a fairly easy passcode  - 7 characters.  Still no connection.  

Reply #5 Top

Has this ever worked, or no, this is the 1st time and it never has?

Quoting jbe117, reply 2

However, at one point yesterday, it was saying that it could connect but that I had the wrong passcode (I did not).
End of jbe117's quote

Just once or now always when you test the connection?

Are they both connected to the same network and on the same type - for example, they are both on Ethernet?

As a test, please ensure both are indeed ethernet-connected.

Sean Drohan
Stardock Support Manager

Reply #6 Top

The primary was previously a secondary and was able to connect to its primary at the time.  However, we have made some network changes recently and the primary is in the original VLAN that it previously was but the secondary (new laptop) is actually in a different VLAN.  However, both VLANs can talk to one another and ping works between them.  But perhaps this is problematic for Multiplicity.  I'll have to test putting the primary into the same VLAN as the laptop.  I'll get back to you and let you know.

Reply #7 Top

Quoting jbe117, reply 6

But perhaps this is problematic for Multiplicity. 
End of jbe117's quote

Indeed.

Yes, please do let us know.

Sean Drohan
Stardock Support Manager

Reply #8 Top

That did the trick.  I should have known better.  Thanks for your help and insight (and for kicking my brain into gear o_O  )

Reply #9 Top

Quoting jbe117, reply 8

That did the trick.  I should have known better.  Thanks for your help and insight (and for kicking my brain into gear   )
End of jbe117's quote

Excellent and thanks for the effort and feedback.

Sean Drohan
Stardock Support Manager