Reply to thread

Message

Hi Michael.

I checked the network with a WOL tool for all the clients & the server, all woke up as needed everytime I tried with the WOL tool. THe problem lies within MP or the powerscheduler++ plugin. I noticed that when the clients resume from sleep they do not seem to send the signal to the server to wake up.

So I tried uninstalling the plugin on both server and clients, then installed the server side first, followed by the client side. Then I rebooted and then they worked and woke the server up. However after trying it again a few more times I get the dreaded message "could not connect to tv service" and sometimes MP will then lock up and I then have to ctrl alt & delete. Reopening MP though will then wake the server so there is something not happening when the client resumes from sleep that happens when I restart MP. Could this be a plugin issue with Powerscheduler++ given that it is happening to both clients??? Everytime the WOL tool was used on both my laptop on phone the server would wake instantly as it should do, only MP would not wake it.

I have now set the option within MP config to restart MP when resuming from sleep and so far this is working everytime. However not sure why have to have this option enabled though.

<blockquote data-quote="richardc1983" data-source="post: 923597" data-attributes="member: 131658">Hi Michael.&nbsp;I checked the network with a WOL tool for all the clients &amp; the server, all woke up as needed everytime I tried with the WOL tool. THe problem lies within MP or the powerscheduler++ plugin. I noticed that when the clients resume from sleep they do not seem to send the signal to the server to wake up.&nbsp;So I tried uninstalling the plugin on both server and clients, then installed the server side first, followed by the client side. Then I rebooted and then they worked and woke the server up. However after trying it again a few more times I get the dreaded message &quot;could not connect to tv service&quot; and sometimes MP will then lock up and I then have to ctrl alt &amp; delete. Reopening MP though will then wake the server so there is something not happening when the client resumes from sleep that happens when I restart MP. Could this be a plugin issue with Powerscheduler++ given that it is happening to both clients??? Everytime the WOL tool was used on both my laptop on phone the server would wake instantly as it should do, only MP would not wake it.&nbsp;I have now set the option within MP config to restart MP when resuming from sleep and so far this is working everytime. However not sure why have to have this option enabled though.</blockquote>

[QUOTE="richardc1983, post: 923597, member: 131658"] Hi Michael. I checked the network with a WOL tool for all the clients & the server, all woke up as needed everytime I tried with the WOL tool. THe problem lies within MP or the powerscheduler++ plugin. I noticed that when the clients resume from sleep they do not seem to send the signal to the server to wake up. So I tried uninstalling the plugin on both server and clients, then installed the server side first, followed by the client side. Then I rebooted and then they worked and woke the server up. However after trying it again a few more times I get the dreaded message "could not connect to tv service" and sometimes MP will then lock up and I then have to ctrl alt & delete. Reopening MP though will then wake the server so there is something not happening when the client resumes from sleep that happens when I restart MP. Could this be a plugin issue with Powerscheduler++ given that it is happening to both clients??? Everytime the WOL tool was used on both my laptop on phone the server would wake instantly as it should do, only MP would not wake it. I have now set the option within MP config to restart MP when resuming from sleep and so far this is working everytime. However not sure why have to have this option enabled though. [/QUOTE]