can't awaken second computer in seamless control

from Stardock Forums

I'm excited to start using Multiplicity!

I have three machines:

  • SLACK, my primary. It has three monitors and runs Windows 11
  • LAKE, a secondary. It has a single monitor and runs Windows Server 2019.
  • SLIDE, another secondary. It has a single monitor and runs Windows Server 2019.

In seamless mode, I can move my mouse towards LAKE and it works fine. The monitor turns on (if it wasn't) and I can interact with the computer.

But SLIDE doesn't work. I can connect to it with Remote Desktop, no problem; and there's no issue pinging it of course. Multiplicity will show that it's "Now Controlling SLIDE" if I have the status window option enabled.  But nothing I do turns on the monitor so I can't actually interact with that computer.

I guess there's some setting I must fiddle? Anyone know what it is?

 

 

multiplicity
2,930 views 3 replies
Reply #1 from Stardock Forums Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

Reply #2 from Stardock Forums Top


But SLIDE doesn't work. I can connect to it with Remote Desktop, no problem; and there's no issue pinging it of course. Multiplicity will show that it's "Now Controlling SLIDE" if I have the status window option enabled.  But nothing I do turns on the monitor so I can't actually interact with that computer.
End of quote

Try:

The destination PC need to be set to respond to WAL btw... Usually done in the BIOS.

Sean Drohan
Stardock Support Manager

Multiplicity - Control multiple PCs using one keyboard and mouse
Reply #3 from Stardock Forums Top

Changing the wake on LAN setting didn't help.

I don't think this can be a surprise, as wake-on-LAN is intended to power on the machine, not kill the screen saver or take the monitor out of power-saving mode. The other machine works fine without wake-on-LAN set.

Maybe my first post wasn't clear. The machine in question is powered-on. It's screen is in power-save mode, since it's not being accessed. I expect it to work like the first machine: the monitor enters power save after a time, but if I use Multiplicty to control the machine, it should wake up again.

Other mouse-sharing programs don't have this problem on this machine.