There is nothing wrong and nothing to fix. In order to support WOL, something *has* to be active to watch for and react to the magic packets. The purpose of the sleep state (S3) is to minimize the power being utilized while there is nothing to do. This minimization is necessarily limited to the portions of the system that aren't necessary to handle wakeup events.
Hope this helps,
First of all thanks for your answer
On the other hand i think my "problem" shouldn't have happened. Why? My previous server (My 2009 Fujitsu Esprimo Mobile V5535 Laptop) just didn't have this odd problem. I was using my laptop about 3 years in a row - with same software (same win 7 edition), same programms and same settings. As a result Ip was not active (not online) in the same
network ip scanner app.
Even my main pc (2008 HP Pavilion a6240 Desktop PC) ip seems to be inactive when my pc sleeps.
My network ip scanner just says (i copy paste them)
"online status uncertain (based on pottentialy cashed data)" and
" Host is hidden (did not reply to ping request)"
Anyway, it may be smth in hw either in nuc's or newer pc's..
Again, I say you have no problem. Your IP scanner is getting its data from the IP (DHCP) server's cache (which is used to ensure this PC will get the same IP address when it does awaken (if within timeout period, of course)). Have you changed your DHCP server recently?
I used the same ip, subnet, gateway and dns servers that my old server (Fujitsu Esprimo Mobile V5535 Laptop) used to have. I always use a static "intranet" ip for my servers and clients (like 192.168.x.x).
So maybe this?
We could speculate all day long. At the end of the day (pun intended), all that matters is whether this PC is too awake and thus wasting power unnecessarily. If you are that concerned about it, measure this and see..
Anyway doesn't matter. Everything works fine. Just wondering why different behavior between my ex server and my today's nuc.
Scott thanks 4 your quotes and answers:)