Reply to thread

Message

<blockquote data-quote="Zoidberg77" data-source="post: 920694" data-attributes="member: 114314">I had a similar problem once with a device which needed the server to be online but wouldn't open any windows share and didn't generate much lan traffic either. I used a script to ping the device and to switch the active power scheme to prevent standby:[CODE]@echo offpowercfg -getactivescheme | find /i &quot;Ausbalanciert&quot; &amp;&amp; (goto OffLoop)powercfg -setactive 381b4222-f694-41f0-9685-ff5bb260df2e&nbsp;:OffLoopping -n 1 -w 5000 192.168.2.43 | find /i &quot;TTL&quot; &amp;&amp; (goto Online)timeout /T 60 /nobreakgoto OffLoop&nbsp;:Onlinepowercfg -setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c:OnLooptimeout /T 300 /nobreakping -n 1 -w 5000 192.168.2.43 | find /i &quot;TTL&quot; &amp;&amp; (goto OnLoop)powercfg -setactive 381b4222-f694-41f0-9685-ff5bb260df2egoto OffLoop&nbsp;exit [/CODE]Of course you would have to adapt the power schemes to your needs (I utilized &quot;Balanced&quot; and &quot;High performance&quot;) and adapt the GUID (check with &quot;powercfg -list&quot; in a command prompt).Maybe it helps <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />&nbsp;P.S.: This will only work if PS++ won't force standby and let Windows handle everything.</blockquote>

[QUOTE="Zoidberg77, post: 920694, member: 114314"] I had a similar problem once with a device which needed the server to be online but wouldn't open any windows share and didn't generate much lan traffic either. I used a script to ping the device and to switch the active power scheme to prevent standby: [CODE]@echo off powercfg -getactivescheme | find /i "Ausbalanciert" && (goto OffLoop) powercfg -setactive 381b4222-f694-41f0-9685-ff5bb260df2e :OffLoop ping -n 1 -w 5000 192.168.2.43 | find /i "TTL" && (goto Online) timeout /T 60 /nobreak goto OffLoop :Online powercfg -setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c :OnLoop timeout /T 300 /nobreak ping -n 1 -w 5000 192.168.2.43 | find /i "TTL" && (goto OnLoop) powercfg -setactive 381b4222-f694-41f0-9685-ff5bb260df2e goto OffLoop exit [/CODE] Of course you would have to adapt the power schemes to your needs (I utilized "Balanced" and "High performance") and adapt the GUID (check with "powercfg -list" in a command prompt). Maybe it helps ;) P.S.: This will only work if PS++ won't force standby and let Windows handle everything. [/QUOTE]

Verification