search

basildane / WakeOnLAN

Wake On LAN, WakeOnLAN, shutdown software for Windows. A powerful WOL, ping, shutdown, GUI application.
http://wol.aquilatech.com
Other
1.01k stars 147 forks source link

Yes, another WOL over Internet issue #113

Open newdude72 opened 6 years ago

newdude72 commented 6 years ago

So I'm confused. Locally WOL worked fine from one PC to another. I then set up my router to forward UDP port 9 to the local static IP of a PC 192.168.0.231. Here at a remote location PC I set up WOL using the public IP of my router as the broadcast and 192.168.0.231 as the FQDN /IP. I set the remote PC to listen and locally I clicked Wake up. The listener displayer all the information of the wake up packet. I assumed it would work fine but when I tried to actually wake up over Internet it doesn't wake up. Any help from anyone greatly appreciated as I'm now 1200 miles away. What did I miss?

basildane commented 6 years ago

The way WOL works, you cannot send it to an IP address. The reason is that when the machine is off, it doesn't have an IP address. So, you must broadcast the message to a network segment, for example, 192.168.0.255. The NIC on the computer must be configured to listen for it's MAC address on the network. When it's see's the message, it will trigger the motherboard to power on.

I have a program called Agent to help you do this. It has to run on a server that is online of course. Another option is to use your router to forward port 9 to a broadcast subnet such as 192.168.0.255, if it can. Some can, some cannot.

As for testing, this is a complex subject and it doesn't work for everyone. Testing before you go on a trip is very important.

Do you have the ability to access your router's configuration web page from where you are currently located?

newdude72 commented 6 years ago

Hello, and thanks for the reply. You were kind enough to help me a couple years back with another issue. I will once again donate.

Ok, so the computer I want to wake up is the host and this computer is the remote.

I just logged in to my router at the host and tried to forward UDP port 9 to 192.168.0.255 and it says invalid address. Am I dead in the water?

From: Basildane Sent: Sunday, July 1, 2018 4:59 PM To: basildane/WakeOnLAN Cc: newdude72 ; Author Subject: Re: [basildane/WakeOnLAN] Yes, another WOL over Internet issue (#113)

The way WOL works, you cannot send it to an IP address. The reason is that when the machine is off, it doesn't have an IP address. So, you must broadcast the message to a network segment, for example, 192.168.0.255. The NIC on the computer must be configured to listen for it's MAC address on the network. When it's see's the message, it will trigger the motherboard to power on.

I have a program called Agent to help you do this. It has to run on a server that is online of course. Another option is to use your router to forward port 9 to a broadcast subnet such as 192.168.0.255, if it can. Some can, some cannot.

As for testing, this is a complex subject and it doesn't work for everyone. Testing before you go on a trip is very important.

Do you have the ability to access your router's configuration web page from where you are currently located?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

newdude72 commented 6 years ago

BTW, I have it powered back on. I guess my WOL is the nice next door neighbor who went over and turned it on for me. I now have two PC’s on-line that I have access to. I would love to be able to figure this out.

Thank you

From: Basildane Sent: Sunday, July 1, 2018 4:59 PM To: basildane/WakeOnLAN Cc: newdude72 ; Author Subject: Re: [basildane/WakeOnLAN] Yes, another WOL over Internet issue (#113)

The way WOL works, you cannot send it to an IP address. The reason is that when the machine is off, it doesn't have an IP address. So, you must broadcast the message to a network segment, for example, 192.168.0.255. The NIC on the computer must be configured to listen for it's MAC address on the network. When it's see's the message, it will trigger the motherboard to power on.

I have a program called Agent to help you do this. It has to run on a server that is online of course. Another option is to use your router to forward port 9 to a broadcast subnet such as 192.168.0.255, if it can. Some can, some cannot.

As for testing, this is a complex subject and it doesn't work for everyone. Testing before you go on a trip is very important.

Do you have the ability to access your router's configuration web page from where you are currently located?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

basildane commented 6 years ago

I just logged in to my router at the host and tried to forward UDP port 9 to 192.168.0.255 and it says invalid address. Am I dead in the water?

That is normal. Most routers do not forward to broadcast addresses. That is why I wrote the Agent program. If you have a server that is always on in your home, you can run the Agent on it. It will broadcast the packets for you. If you don't have a server, then I don't think you are going to be able to do this over the Internet.