How to prevent a computer from going to sleep while connected over a network.

[jcb1972]

I have a wired network at home with several networked computers. One of them is a server which I use to store pictures, music, movies, etc. I have the server set to go into sleep mode when not in use. The drive on the server which holds all of the files is mapped to my main workstation.

When I boot up my main workstation it automatically wakes up the server. The problem is that my server will go to sleep while I am connected to it. If I am working on a video in Premiere the server will go to sleep even though the video I am working on is on the server.

What network settings can I adjust on the server to prevent it from going to sleep once I have connected to my mapped drive with my files?

Thanks in advance for the help!

 

[The Paladin]

I don't understand why you would want to have a "server" to go to sleep at all.
the sleep settings are in your power setting under control panel

 

[bill001g]

I don't think there is a setting that will do that. It seems to only "think" your pc is active based on mouse and keyboard usage. I know they had a major issue when things like youtube switches to HTML5 and you were running video in the background. For some reason the so called multimedia settings no longer detected this as activity. I think they finally fixed that. They had to add special multimedia settings to even allow you to watch long video when you had the sleep options turned on, it used to just turn off in the middle of a video.

There would have to be special option that prevented the machine from going to sleep if there was remote disk activity. I do not think that option exists but file sharing features is one of the things that is different between the versions of window10...I still don't think that option exists.

Your best bet is likely to just let the machine in always on mode. In general the CPU will drop into low power mode by itself when it is not actually being used much.

 

[Solandri]

When your computer "connects" to the server, it isn't constantly querying the server. So all the server sees is a data request from your computer, then nothing for long enough for it to go to sleep again.

You could however use a small batch file I created to diagnose another problem. It writes a random number to the selected drive every few seconds. Run it in a command prompt window and it should keep the server awake for as long as your computer is on.

Type the following into a file named keepawake.bat, and run it in a command prompt with the current drive set to the server (you may have to map the networked drive to a drive letter).

:repeat
@echo %RANDOM% > tmp.txt
ping -n 8 127.0.0.1 > NUL
goto repeat

 

[jcb1972]

When your computer "connects" to the server, it isn't constantly querying the server. So all the server sees is a data request from your computer, then nothing for long enough for it to go to sleep again.

You could however use a small batch file I created to diagnose another problem. It writes a random number to the selected drive every few seconds. Run it in a command prompt window and it should keep the server awake for as long as your computer is on.

Type the following into a file named keepawake.bat, and run it in a command prompt with the current drive set to the server (you may have to map the networked drive to a drive letter).

:repeat
@echo %RANDOM% > tmp.txt
ping -n 8 127.0.0.1 > NUL
goto repeat

That is pretty cool. I may have to give it a try. Thanks!