You definitely need to have Wake on LAN from S4/S5 set to Power On - Normal Boot if you want WOL to work (regardless of any relationship with USB Wake). It also needs to be understood that the system attempting to wake the NUC needs to be sending a proper magic packet (i.e. just creating LAN traffic is not going to do it).
As for CIR Wakeup, the remote has to be understood. When you say a "generic samsung" remote, what are you referring to? A remote that came with, for example, a Samsung TV? This kind of remote is NOT going to be understood (it is definitely NOT "generic"). You need a proper multimedia remote or an All-In-One unit like the Logitech Harmony. Here are links to a few that I have that definitely do work:
Hope this helps,
Thank you for your reply Scott.
- If wake on LAN is disabled, wake over USB wont work. It is very simple to test, disable wake on lan and you will notice that the NUC doesn't booth on keyboard press. Hence my comment on first post of this thread.
- For sending magic packets, i've tried different solution in particular FING, running on mobile devices on my network: https://www.fing.io/
- Regarding CIR, i understand what you say and I'll test it according to your suggestion.
For WOL to work you have to enable it in your OS as well. For Windows there are settings for it in the NIC properties. For Linux ethtool can do it.
Also make sure the device you send the magic packet from is in the same network segment. If it is connected via WLAN and the AP is not a simple (layer 2) bridge into the LAN network, but instead acts as a (NAT) router for a different segment, WoL will not work.
I've enabled wake on lan following this tutorial in less than a minute, on the OS level.
Basically there is a checkbox on your NIC properties in the device manager in windows.
Sending magic packets works well and turn on the NUC as expected. I've updated my first post.