Cant seamless to secondary after it resumes from sleep

from Stardock Forums

Fairly straightforward, unsure if anyone has any ideas on a solution.  If i use Multiplicity to wake my secondary from sleep I cannot seamless to it.

If i restart the multiplicity service on my main via services.msc or via the taskbar/gui, i can immediately mouseover.

Its like it doesnt rediscover it when waking from sleep.   For now ive created a batch to restart the service but thats mighty clunky :)

multiplicity
16,523 views 11 replies
Reply #1 from Stardock Forums Top

Hello,

Sorry to hear you are having issues.

Need a little more info, please.

Version of Windows ( full number version ) use winver.exe for that info

Version of Multiplicity your using too.

 


AzDude
Stardock Community Assistant

Reply #2 from Stardock Forums Top

windows is 20H2 (19042.662) but its been happening for quite some time.  

multiplicity is 3.51 build 00097 .kvmpro

if you need anything else lmk

Sins of a Solar Empire: Rebellion
Reply #3 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.

 

AzDude
Stardock Community Assistant

+1 Loading…
Reply #4 from Stardock Forums Top

klepp0906,

If I recall, you have had numerous posts about WOL issues in your rather complex network (again, if memory serves me). 

I believe you had it resolved at one point, yes?  If I am not mistaken it had to do with prioritizing your multiple NICs, yes?

We even added a warning to MP as a result if I am not mistaken:

Sean Drohan
Stardock Support Manager

Reply #5 from Stardock Forums Top

yes, that was me and it was/is fixed by ensuring the interface metric is set higher than your physical network card.  

wake on lan is working.  

seamless is working until i put my secondary to sleep

upon waking it from sleep via multiplicity, seamless will not work until i restart the multiplicity service on the primary at which point i can immediately begin seamless.  

its weird considering as i mentioned, wake on lan works fine.  also if i open the multiplicity gui it shows the secondary as on, and also says "multiplicity was able to successfully connect to this computer" if i click on the gear.  Yet no seamless until i restart the service then it instantly works. 

At a loss on this one, at least for now. 

Reply #6 from Stardock Forums Top

As a test, what happens if you wake the secondary using another wake on lan utility rather than from Multiplicity?

Reply #7 from Stardock Forums Top

Quoting Neil, reply 6

As a test, what happens if you wake the secondary using another wake on lan utility rather than from Multiplicity?
End of Neil's quote


Sorry, just woke up.  I tested it and after I put it to sleep I woke it via "Wake on LAN" by aquilatech.  Same issue.  I cant seamless until I restart the multiplicity service.  Then it instantly begins functioning.


Reply #8 from Stardock Forums Top

Quoting klepp0906, reply 7


Quoting Neil Banfield,
reply 6

As a test, what happens if you wake the secondary using another wake on lan utility rather than from Multiplicity?



Sorry, just woke up.  I tested it and after I put it to sleep I woke it via "Wake on LAN" by aquilatech.  Same issue.  I cant seamless until I restart the multiplicity service.  Then it instantly begins functioning.



End of klepp0906's quote

But you have to restart the service on the primary not secondary?

Reply #9 from Stardock Forums Top

Quoting Neil, reply 8


Quoting klepp0906,
reply 7






Quoting Neil Banfield,

reply 6


As a test, what happens if you wake the secondary using another wake on lan utility rather than from Multiplicity?



Sorry, just woke up.  I tested it and after I put it to sleep I woke it via "Wake on LAN" by aquilatech.  Same issue.  I cant seamless until I restart the multiplicity service.  Then it instantly begins functioning.






But you have to restart the service on the primary not secondary?

End of Neil's quote


correct.  i first began by manually restarting the multiplicity client but then assumed it was probably the service so began by doing that via the services.msc gui.  Finally just created a batch/shortcut on the desktop to double click every time which is the best I have at the moment. 

Reply #10 from Stardock Forums Top

And then what happened? Got the same problem on the W10 installation on my Steam Deck. The device wakes up from sleep, I can ping it immediately, so the LAN connection is working, but I have to restart the Multiplicity Service on the primary to get it going.

Reply #11 from Stardock Forums Top

Quoting kaiuno, reply 10

And then what happened? Got the same problem on the W10 installation on my Steam Deck. The device wakes up from sleep, I can ping it immediately, so the LAN connection is working, but I have to restart the Multiplicity Service on the primary to get it going.
End of kaiuno's quote

And it then works, yes?

There is an easier option than going into services to restart the MP process:

Sean Drohan
Stardock Product Lifecycle Manager