Then, Microsoft can be inconsistent or not (no wonder in this), but if the packet is able to wake the pc within the lan, why shouldn't it work from outside the lan? BIOS should not have anything to do with this: it either works or doesn't. What do you mean saying that using the external IP "is another issue"? Is it better or worse? MC-WOL aa□□cc:dd:ee:ff /a 11.22.33.44 (where 11.22.33.44 is the external, internet address of the vodafone router) I don't think I have much of a choice here: that is the address of the lan where the packet is supposed to go Then it should be the router to route the packet to the correct MAC address. ![]() You can set the machine to boot as soon as it gets power.Ĭlick to expand.I thought it was clear from my example: I send the packet to the external IP of the router. You can also just use one of fancy power plugs you can access via the internet. There is very little extra power being used compared to WoL state. Many of the microsoft low power options let you remotely access machine even it is in low power and it will bring the power up. I tend to not bother with this mess anymore. The other common way to do this would be to remotely access your always on pc and ask it to send the WoL. Some routers like ASUS you open a web page remote on your router and ask it to send the WoL packet for you. You must send multiple packet to wake it. On top of this WoL is very flaky sometimes. Technically it should not have a IP header but few WoL clients enforce this. Since WOL only cares about the mac address inside the packet having strange IP doesn't matter. You would then put in port forward rules to 192.169.0.100. The other method is to put in a static ARP entry (not possible on most consumer routers) and map some dummy IP like 192.168.0.100 to the broadcast mac address FF:FF:FF:FF:FF:FF. Many routers disable this because someone can denial of service attack you. The other way this might work is to put in a port forward rule to the broadcast IP. Some WOL clients also enforce that the WOL packet must be sent to the broadcast mac addresses rather than the machine mac address. WOL has no concept of IP addresses so it can not technically be done from a different subnet. I agree it is likely a mac timeout which is why this hack doesn't work on most routers. Can this be of any help in finding a solution? Thank you for your understanding. What am I doing wrong?Īlso, note that in the Vodafone LAN there is always a windows10 PC powered on, because it hosts the SQLEXPRESS used to handle our small database. It is clear Im am missing something vital, and maybe trivial (but not for me). I get the same result message (SUCCESS!! in sending the packet) but nothing happens, and the PC does not wake up. This should take care of the fact that the vodafone router, as every other commercial router, does not support broadcasting, but in this I may be wrong.Īnyhow, if in a pc in the same LAN I try the commandĪll is well, and the pc wakes up without trouble ![]() with static DHCP in vodafone router, I mapped the MAC address of the target pc (say aa□□cc:dd:ee:ff) to its IP address in LAN (say 192.168.1.22).From what I understand, MC-WOL uses port 65535. I am using Matlab MC-WOL.exe command line to send the magic packet to the target pc. The target PC is correctly configured to be awoken, since WoL works perfectly INTHE SAME LAN. My home pc is in a LAN behind a 3 home-and-life router, the pc to be awoken is in a LAN behind a Vodafone Station Revolution router. The challenge is to wake up a windows10 pc from a windows10 pc at home. ![]() It has been literally years I am trying to solve or at least understand a WoW problem.This may be due to my poor understanding of many suggestions I have been reading here and there, so I'll try to summarize what I did and what does not work, in a practical way.
0 Comments
Leave a Reply. |