Waking up from sleep mode

Hello,
Sorry to hear you are having issues. But, just to be sure, your primary do wake up, just that your secondary not waking up, correct?

Also have you tried looking for information here: https://forums.stardock.com/486104/multiplicity-support-faq

Thanks
Basj,
Stardock Community Assistant.

Hi Basj,

Thanks for your reply. To clarify: they each wake up from sleep. The problem is that I can then no longer move the cursor freely between the two machine's screens.  Previously, I was able to just use the keyboard and mouse of the primary to interface with both systems.  The only workaround I have is to restart the primary.  As soon as it's restarted, Multiplicity is working correctly again and it continues to do so until after it's been back to sleep.  Every time it sleeps, Multiplicity isn't working when it wakes up.

Brian

Have you tried out that FAQ link I given above, specially those Troubleshooting tips?

Thank you,

Basj,
Stardock Community Assistant

Yes, and it's given me at least one lead to follow up.  When trying to solve the problem by manually connecting the secondary I have run into an issue that's highlighted in the User Manual: Troubleshooting.  It points the finger at my firewall, which is of the Bitdefender variety.  I'm perfectly willing to suspect that an over-zealous Bitdefender firewall is the cause of the problem.  Unfortunately, just turning the firewall off temporarily hasn't fixed it.  I'll check with their support.

Many thanks,

Brian

Hello again. I've not yet asked Bitdefender about this because I may have fixed it.  I found that there were already a couple of rules set up in the Bitdefender Firewall.  Listed were rules for multiplicityconfig.exe and multipl2.exe.  In each case, those executables are allowed to use any port, network, protocol or IP address.

The example in the troubleshooting guide I referred to in my earlier response just says "Multiplicity Service" and a port number.  I then had a bright idea... I went and checked the Bitdefender Firewall set up for the secondary.  That has an additional rule for multisrv.exe, so I added an identical rule to the master's list of exceptions and it worked to the extent that if I put the master to sleep and then woke it, everything was fine.  I shall have a confirmation in the morning when I wake up both systems.  All being well it will be 'problem solved'.  Fingers crossed...

Many thanks for your help.  If it's not fixed, I still have a lot of other leads to follow up from the links you sent me.

Brian

It worked like a charm again this morning.

Thanks again.

Brian

Awesome, really glad to hear that.

Thank you,

Basj,
Stardock Community Assistant