- Bug Reports
-
Bugs
+4
Under review
Computer shows offline after waking up from hibernation
Computer offline in Console after it wakes up from hibernation. The only fix is for end user to restart the computer or restart the ScreenConnect service. I am on 20.11 but this problem has been happening for a while, before 20.11 i know that.
ConnectWise Control Version:
Other (please specify)
Server Affected:
Host Client Affected:
Guest Client Affected:
Customer support service by UserEcho
I've seen the same issue, last 1-2 months on my Access instances. Also on 20.11. After waking from sleep, the machines no longer appear in console as connectible targets. Our workaround has been to execute a script from the RMM side to manually restart the ScreenConnect service, which resolves the issue instantly and without fail.
I know this is an older post, but we have the same issue. This seems to happen if anything interrupts the connection for long enough. If a guest is disconnected from the network for long enough, it will not be available to join after it's reconnected to the network, but other remote access applications installed on the guest will be.
Recently I was able to use Wake on Lan from Control to wake a computer from sleep, but after it woke, I could connect to it in other remote access applications, but not in Control.