1. I’m not using Firewall. TVServer is killed only once by nnCron and then is started successfully (due to nnCron logs). Moreover, this scheme worked more than 1 year for me, until 1.1.0* was released. Now TVServer is almost always inaccessible after resuming until I manually restart it through Windows console or when I start TVServer console pressing the icon, which is opened NORMALLY without pushing message “TVServer is not started. Would you like to start it?” (like it was in much earlier “buggy” versions). Only after that MP “sees” the TVServer. I assure you, this happens ONLY in 1.1.0*. Downgrading to 1.0.2. solves the problem TOTALLY.
2. Again, in earlier versions I used MS loopback adaptor using the same subnet as the PC to solve MSSQL problems (I did have problems when TVServer tried to connect to MSSQL DB) and it worked without any problems. OK, this might sound strange, as I’m not a sysadmin. Sorry.
Then I switched the MS loopback adaptor off, as the problems were solved by MP’s team.
Now in 1.1.0* I tried to use it again, but without any success.
I didn’t remove it, but I configured MP and TVServer to use a “real” PC’s IP.
Anyway, if MP and TVServer are both configured to use a “real” IP, why should they try to use the MS loopback adaptor’s IP, which might cause problems? Why, if it is pre-configured?
In network connections priorities I have: (1) “real” dynamic PC’s IP , (2) static MS loopback adaptor, (3) SS2 IP.
3. Do you mean that PowerScheduler now can restart SS2 driver?
Again and again, I always used my cheap Korean remote, configured through IRLink SW to emulate pressing Windows “send to hibernation” without any problems. And it worked more than a year. Now you say I should “map the Power button to MP's own "Suspend" action instead”. Again, that sounds strange.
2. Again, in earlier versions I used MS loopback adaptor using the same subnet as the PC to solve MSSQL problems (I did have problems when TVServer tried to connect to MSSQL DB) and it worked without any problems. OK, this might sound strange, as I’m not a sysadmin. Sorry.
Then I switched the MS loopback adaptor off, as the problems were solved by MP’s team.
Now in 1.1.0* I tried to use it again, but without any success.
I didn’t remove it, but I configured MP and TVServer to use a “real” PC’s IP.
Anyway, if MP and TVServer are both configured to use a “real” IP, why should they try to use the MS loopback adaptor’s IP, which might cause problems? Why, if it is pre-configured?
In network connections priorities I have: (1) “real” dynamic PC’s IP , (2) static MS loopback adaptor, (3) SS2 IP.
3. Do you mean that PowerScheduler now can restart SS2 driver?
Again and again, I always used my cheap Korean remote, configured through IRLink SW to emulate pressing Windows “send to hibernation” without any problems. And it worked more than a year. Now you say I should “map the Power button to MP's own "Suspend" action instead”. Again, that sounds strange.