It seems that when the PC has been sleeping for a too long time (say 48h) it cannot be waken from the internet (but this is still possible from the LAN). In the WoL app, I had also to set the subnet mask to 255.255.255.255, as it was not working with the default 255.255.255.0 (which is adapted when configuring the WoL app to operate from the LAN itself, not from the internet).ĮDIT: Well, actually it doesn't work that well. Actually I am even using my personal domain name that point to the public address, it works. So now, from the internet I can wake up the PC using the public IP address of the router, the port xxxxx, and the MAC address of the PC. I have installed on Wake-on-Lan app on my phone, and on the router I have redirected a port xxxxx to the port 9 on the PC. So the PC normally goes to sleep and is longer waken up permanently. In the settings of the Wifi card in the device manager I have finally re-checked "Allow wake-up only by magic packet", as it was initially. Meanwhile, Linux does allow the wake patterns to be customized, but when an ARP query is made, the system still doesn't even know yet what kind of connection it'll be receiving nor from whom – this might be improved by Ethernet NICs supporting "ARP offload", but I don't know if that's a thing on your hardware. (For example, my Android file manager automatically tries to connect to configured network servers so that it could show the green/red "online" indicator.) ![]() So your system will be woken up if another computer in the LAN tries to reach it via SMB or SSH or HTTP. Unfortunately, Windows doesn't offer any configuration on what patterns it'll enable – it's all or nothing. This does not inherently prevent the computer from going to sleep – but the problem is that it'll wake the computer on any connection attempts, not limited to just RDP. Allowing inbound RDP at port 3389 from the entire Internet means you'll be receiving unwanted RDP connections every minute – testing your system for common passwords and/or unpatched exploits that used to be plentiful in the Windows RDP server code.ĭisabling the "Only allow management stations." option activates "Wake on pattern" functionality, in which the OS configures the network card to recognize specific packet headers such as ARP queries or TCP SYN handshake packets. ![]() If your RDP connections can wake the computer, so can anyone else's. The RDP access (and thus the wake-up) must be possible from the internet (for RDP I have already opened port 3389 on the box). It's a mini fanless PC that does not use much power when idle, but I would like a more satisfactory solution: how to wake a it when accessing it with RDP, without disabling the automatic "go to sleep" bahavior? And when I put it to sleep manually, it is always awaking on its own (I mean without doing anything for that). The problem is that the PC does not longer go to sleep by itself. Now it's ok, the RDP connection wakes up the PC. I then unchecked "Allow wake-up only by magic packet", which was checked by default. But still the PC is not awaken by the RDP access. Wake-on-Lan is enabled in the BIOS, and in the settings of the Wifi card in the device manager I have checked the option "Allow this device to wake up the PC from sleep". When it is asleep a tentative RDP access does not wake it. It is configured to automatically go to sleep (simple standby, no hibernation) after a certain inactivity period. I have a CI329 Zotac PC with Win 10 Pro, that is to be used for occasional RDP access.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |