Windows 10: Remote Desktop Host Sleeps After Only Five Minutes

I host a computer that is used by a few people in a small organization. We use Windows Remote Desktop (RDP) to access the computer - even me and the computer is in my basement. RDP works fine and everyone is able to get access to the computer and do their work.

Last fall I figured out how to use network enabled Wake on Lan to remotely wake up a sleeping computer. Once I had educated my users on how to use Wake on Lan, I enabled sleep mode on the computer and set it for 30 minutes. Keeping the computer sleeping when not in use has several advantages and I intend to continue to keep it set up this way.

There is a problem, however. Despite the computer's sleep setting being set to 30 minutes, when there is a remote desktop connection, the computer goes to sleep after only 5 minutes of idle time. This is distacting as you can't leave your remote work for more than a moment or sleep knocks your connection down and you have to log back into the remote connection. I know that it is sleep that is knocking down the connection because when you try to log in again, you cannot do so until you run the Wake on Lan application to wake the computer back up. Then it lets you sign right in again. (I've also just gone into the basement and looked at the thing - it's asleep!)

I've tried extending the sleep time and set the display timer to never. This does not change things. When using RDP, the computer sleeps after 5 minutes of idle time. If you work locally, sleep is normal and the machine sleeps after 30 minutes.

I cannot find any settings in Windows that would allow me set timers differently than from the standard power settings. Why is this happening?

:)

 

Remote Desktop - Remote Computer is Sleeping

Got a question that I could answer if I was at the office to try it... Trying to connect remotely to an HP desktop at work.

If the HP is in sleep mode, I can't remote into it. Here's the scenario: Couldn't remote into the HP... Called a co-worker he noticed is was in power saving mode & moved the mouse, it woke up. Then I was able to remote in.

Would "Wake on Lan" in BIOS allow me to wake up the computer through a remote desktop login request? Are there other settings?

EDIT: Both PC's on XP Pro 32

 

Keep Remote Desktop going if Host falls asleep

Hi,

I am using my home PC (Win 10) to connect to my headless Server (Win 2016) via Remote Desktop.

If my home PC goes to sleep then my Remote Desktop session pauses and then resumes once my home PC wakes up.
This is quite annoying especially if something is running on the server and then my home PC goes to sleep. I don't want to keep my home PC on all the time just to keep the remote desktop session alive. Is there a way to keep the remote desktop session alive whilst my home PC sleeps.

The only solution to come to mind is to run TightVNC instead. Any other suggestions?

 

remote desktop connection

You will need to analyse the various stages that form part of the remote desktop connection. This will require some time and patience.

A remote desktop connection consists of these components:

• A host (which must run Windows Professional). This is the machine that you wish to control.
• A client (which can run any version of Windows). This is the machine that you work on.
• A link that connects the client with the host.

Is the host on the same network as the client or is it on a different network?