Reply to thread

Message

<blockquote data-quote="Guzzi" data-source="post: 560419" data-attributes="member: 55213">AW: MPstandbyHandlerHi Josch,I have the following setup: - Central TV-server (all fine, sleeps and wakes up, no additional tools except MP stuff necessary) - Using S3 to let the box sleep when not in use- NAS for mediafiles - also using S3 for sleepingOn the clientPCs thus 2 things have to happen: Waking the TV-server (is now done within MePo WOL function, works fine) plus waking the NAS.To wake the NAS I used hybernatetrigger in the past. Works, but sometimes failed (don't know why). I replaced this now with MPstandnyhandler 2.0.0.9 - just for the purpose to send a WOL magic packet to the NAS, when clients resumes from hibernation.I still have the situation, that sometimes the NAS does not wake up .... the TV server always does.To make sure I have defined 3 steps in the MPstandbyhandler:1. check networkconnection to the router (to make sure, ip-connectivity is properly up, DHCP-renewal, or whatever)2. call a script wol.bat to send the magicpacket to the NAS3. another check networkconnection to the NAS to make sure, NAS is up and runningThe logic seems nice - but from time to time I have the situation, that NAS will not resume when resuming the HTPC.Checking the logs, it seems, the first networkcheck times out - thus the WOL packet probably can't be sent to the NAS. I am using DHCP on the HTPCs.So any idea what/how this could improved to safely wake the NAS? SHould I reinitialize the LAN connection? How could this be done?THanks in advance, GuzziLogs from unsuccessful resume:13.01.2010 00:40:34 - INFO&nbsp; &nbsp; System PowerEvent: ResumeAutomatic13.01.2010 00:40:34 - INFO&nbsp; &nbsp; OnResume13.01.2010 00:40:34 - INFO&nbsp; &nbsp; System PowerEvent: ResumeSuspend13.01.2010 00:40:34 - INFO&nbsp; &nbsp; OnResume - Already resuming13.01.2010 00:40:35 - INFO&nbsp; &nbsp; OnResume - Unable to show splashscreen, MPstandbyHandlerUser not running13.01.2010 00:40:35 - INFO&nbsp; &nbsp; Job Load - Loaded RESUME job NetworkCheck13.01.2010 00:40:35 - INFO&nbsp; &nbsp; Job Load - Loaded RESUME job ExternalCommand13.01.2010 00:40:35 - INFO&nbsp; &nbsp; Job Load - Loaded RESUME job NetworkCheck13.01.2010 00:40:35 - INFO&nbsp; &nbsp; NetworkCheck - Waiting 20s for network interface LAN-Verbindung 313.01.2010 00:40:37 - INFO&nbsp; &nbsp; Check Network Connection - Interface LAN-Verbindung 3 is UP13.01.2010 00:40:37 - INFO&nbsp; &nbsp; NetworkCheck - Connection successfull, trying to ping host &quot;xps-01&quot;13.01.2010 00:40:39 - INFO&nbsp; &nbsp; Ping - Connection to host &quot;xps-01&quot; timed out13.01.2010 00:40:39 - WARNING&nbsp; &nbsp; NetworkCheck - Host &quot;xps-01&quot; could not be reached13.01.2010 00:40:39 - INFO&nbsp; &nbsp; Command Start - Starting (20s): C:\WOL\wol.bat13.01.2010 00:40:42 - INFO&nbsp; &nbsp; NetworkCheck - Waiting 20s for network interface LAN-Verbindung 313.01.2010 00:40:42 - INFO&nbsp; &nbsp; Check Network Connection - Interface LAN-Verbindung 3 is UP13.01.2010 00:40:42 - INFO&nbsp; &nbsp; NetworkCheck - Connection successfull, trying to ping host &quot;xms-01&quot;13.01.2010 00:40:42 - INFO&nbsp; &nbsp; Ping - Host &quot;xms-01&quot; successfully reached within 0ms13.01.2010 00:40:42 - INFO&nbsp; &nbsp; NetworkCheck - Host &quot;xms-01&quot; successfully reached13.01.2010 00:40:42 - INFO&nbsp; &nbsp; OnResume - Done</blockquote>

[QUOTE="Guzzi, post: 560419, member: 55213"] [b]AW: MPstandbyHandler[/b] Hi Josch, I have the following setup: - Central TV-server (all fine, sleeps and wakes up, no additional tools except MP stuff necessary) - Using S3 to let the box sleep when not in use - NAS for mediafiles - also using S3 for sleeping On the clientPCs thus 2 things have to happen: Waking the TV-server (is now done within MePo WOL function, works fine) plus waking the NAS. To wake the NAS I used hybernatetrigger in the past. Works, but sometimes failed (don't know why). I replaced this now with MPstandnyhandler 2.0.0.9 - just for the purpose to send a WOL magic packet to the NAS, when clients resumes from hibernation. I still have the situation, that sometimes the NAS does not wake up .... the TV server always does. To make sure I have defined 3 steps in the MPstandbyhandler: 1. check networkconnection to the router (to make sure, ip-connectivity is properly up, DHCP-renewal, or whatever) 2. call a script wol.bat to send the magicpacket to the NAS 3. another check networkconnection to the NAS to make sure, NAS is up and running The logic seems nice - but from time to time I have the situation, that NAS will not resume when resuming the HTPC. Checking the logs, it seems, the first networkcheck times out - thus the WOL packet probably can't be sent to the NAS. I am using DHCP on the HTPCs. So any idea what/how this could improved to safely wake the NAS? SHould I reinitialize the LAN connection? How could this be done? THanks in advance, Guzzi Logs from unsuccessful resume: 13.01.2010 00:40:34 - INFO System PowerEvent: ResumeAutomatic 13.01.2010 00:40:34 - INFO OnResume 13.01.2010 00:40:34 - INFO System PowerEvent: ResumeSuspend 13.01.2010 00:40:34 - INFO OnResume - Already resuming 13.01.2010 00:40:35 - INFO OnResume - Unable to show splashscreen, MPstandbyHandlerUser not running 13.01.2010 00:40:35 - INFO Job Load - Loaded RESUME job NetworkCheck 13.01.2010 00:40:35 - INFO Job Load - Loaded RESUME job ExternalCommand 13.01.2010 00:40:35 - INFO Job Load - Loaded RESUME job NetworkCheck 13.01.2010 00:40:35 - INFO NetworkCheck - Waiting 20s for network interface LAN-Verbindung 3 13.01.2010 00:40:37 - INFO Check Network Connection - Interface LAN-Verbindung 3 is UP 13.01.2010 00:40:37 - INFO NetworkCheck - Connection successfull, trying to ping host "xps-01" 13.01.2010 00:40:39 - INFO Ping - Connection to host "xps-01" timed out 13.01.2010 00:40:39 - WARNING NetworkCheck - Host "xps-01" could not be reached 13.01.2010 00:40:39 - INFO Command Start - Starting (20s): C:\WOL\wol.bat 13.01.2010 00:40:42 - INFO NetworkCheck - Waiting 20s for network interface LAN-Verbindung 3 13.01.2010 00:40:42 - INFO Check Network Connection - Interface LAN-Verbindung 3 is UP 13.01.2010 00:40:42 - INFO NetworkCheck - Connection successfull, trying to ping host "xms-01" 13.01.2010 00:40:42 - INFO Ping - Host "xms-01" successfully reached within 0ms 13.01.2010 00:40:42 - INFO NetworkCheck - Host "xms-01" successfully reached 13.01.2010 00:40:42 - INFO OnResume - Done [/QUOTE]

Verification