Wake-On-Lan not working after a long sleep

Hi,
If your WOL works correctly but times out after a certain time all you need to do is set up static IP within the computer which will be on WOL as well as your router.

If you have not yet configured static IP within your computer -

Open Windows Start menu.
Open Control Panel.
Classic view: Open Network Connections
Category view: Select Network and Internet Connections, and then Network Connections.
Double-click on your active LAN or Internet connection.
Click Properties.
This opens the Local Area Connections Properties window.
In the General tab, highlight the Internet Protocol (TCP/IP) item, and click Properties.

This opens the Internet Protocol (TCP/IP) Properties window.
In the General tab, click Use the following IP address, and enter:
- IP address. The static IP address you want to assign to this computer. (make sure it's not xxx.xxx.x.1 as that's what your router is configured to)
- Subnet mask. Subnet mask used by your router. (255.255.255.0)
- Default gateway. IP address of your router's default gateway. (xxx.xxx.x.1)
- Make the preferred DNS to 8.8.8.8 and Alternate to 8.8.4.4
Click OK.

Then:
Click OK to close each window.
Restart your computer.


Now you need to configure your router.
Within the router look for something called DHCP, you will have to look for something like "Reserve DHCP"
Click on that and you should be able to see your computer and it's IP address, add it to the reserves (There will be different machines with reserved IP's however they will have the expiry time and date)
Don't forget to apply the settings and then save and quit


To check whether your IP is now fully static run cmd
In the cmd enter ipconfig/all
Look for something that says DHCP enabled, if it states yes then you have done something incorrectly, if it says no then everything is now set up and you should have no problems with WOL getting timeout

Hope this helps ^^



Resources - hotComm FAQ: Assign Static IP Address (Windows XP)

I setup a Lenovo M53 for my mother in CA, but will soon be returning to my home in Kansas City. I want to keep it in good working order for her, and have uses for it myself, while at home working on my Arch Linux computer. She will be keeping it completely turned off most of the time, so I wanted to be able to turn it on at will. I got wol working just fine, but like everyone on this thread, it stopped working after a minute.

I eventually realized the fault was with the AT&T Gateway because after a minute, it saw that the Lenovo was not active, and would not forward the wol packet to it. Of course, AT&T U-verse tech support (and advanced support that you pay for if they solve the issue) was useless, since I had to teach them how wol works in the first place. They were convinced a computer could not be turned on after it was off just by receiving a packet. Anyway, AT&T U-Verse doesn't have the option to just use a modem and your own router. You have to use their gateway, and you can't even define internal static IP addresses for the devices connected to it.

Here's how I got around it (probably missing a lot of steps, but this should be enough for somebody else to figure out how to do it):

1. I bought "BUFFALO AirStation N300 Open Source DD-WRT Wireless Router (WHR-300HP2D)"
2. Set a switch on it to "Bridge"
3. Unplugged my linux computer from the AT&T Gateway and plugged it into the Buffalo dd-wrt router.
4. Connected an ethernet cable from the AT&T Gateway to the "Internet" port of the Buffalo dd-wrt router.
5. DON'T DO THIS -> Used the web interface on the Buffalo dd-wrt router to disable wi-fi (Wireless Network Mode Disabled). TURNS OUT THE AT&T GATEWAY WIFI LOSES ABILITY TO CONNECT TO DEVICES WHEN BRIDGED DEVICE HAS WIFI OFF
6. In the web interface, under Administration Router Management, Remote Access, I enabled HTTP remote access. (For some reason, whenever I tried to use HTTPS, I completely lost access to the web interface and had to start over after doing a hard reset.)
7. Unplugged my linux computer from the Buffalo dd-wrt router, and plugged it back into the AT&T Gateway.
8. Unplugged the Lenovo from the AT&T Gateway, and plugged it into the Buffalo dd-wrt router.
9. Used whatsmyip.org from my linux computer to find the AT&T Gateway public IP address, let's call it att.pub.ip.add.
10. In the AT&T Gateway web interface, set up a custom port forwarding that I called Buffalo HTTP to forward port 8080 to the Buffalo dd-wrt router.
11. Accessed the Buffalo web interface through the internet at att.pub.ip.add:8080 (of course, I put in the address found from whatsmyip.org)
12. In the Buffalo web interface, Administration WOL tab, checkmarked to enable WOL on the Lenovo that is now connected to the Buffalo dd-wrt router.
13. Verified WOL from the web interface worked well, no matter how long the Lenovo was turned off.
14. Really though, I wanted to issue a command from a terminal in my linux computer and have it turn on the Lenovo without using the Buffalo web interface, so had to do some more port forwarding.
15. First, went into the web interface of the AT&T Gateway and set up a custom port to be forwarded to the Buffalo dd-wrt router; let's call it BuffPort. (Can keep a tab open to both interfaces)
16. Back in the Buffalo web interface, under Services Management, enabled SSHd and related stuff, including the same custom port (BuffPort) that will be forwarded from the AT&T Gateway.
17. In the Buffalo web interface, under Administration Router Management, Remote Access, I enabled SSH Management and set the custom BuffPort remote port again.
18. Got ssh from my linux computer into the Lenovo working
    
    
    Code:

    ssh -p BuffPort root@att.pub.ip.add

19. Figured out that the wol command didn't work in a straightforward way, but that the command that did work was stored on the Buffalo dd-wrt router, and could be printed to the screen with
    
    
    Code:

    nvram get wol_cmd

20. Here is the command that can be ran from my Linux computer to turn on the Lenovo:
    
    
    Code:

    ssh -p BuffPort root@att.pub.ip.add '$(nvram get wol_cmd)'

The last step above is all that's related to this thread, but I also had to do some trickery to be able to ssh directly into the Lenovo from my Linux Computer because for whatever reason, I was not able to setup port forwarding using the Buffalo dd-wrt web interface. Here's how I was able to do it from the ssh terminal though:

Code:

iptables -t nat -I PREROUTING -p tcp -d $(nvram get wan_ipaddr) --dport Buff2Port -j DNAT --to 192.168.11.140:Buff2Port

iptables -I FORWARD -p tcp -d 192.168.11.140 --dport Buff2Port -j ACCEPT

Where 192.168.11.140 is the internal IP address the Buffalo dd-wrt router has for the Lenovo connected to it, and Buff2Port is another custom ssh port being forwarded to the Buffalo dd-wrt router from the AT&T Gateway. To make these port forwarding commands last after a reboot of the Buffalo dd-wrt router, I used the web interface to save them as a firewall script. It's in the Administration Commands tab. Just copy the commands in there, run them, and click the "Save Firewall" button.

A command for turning off the Lenovo from my Linux computer is as follows:

Code:

ssh -p Buff2Port Win7User@att.pub.ip.add 'shutdown /s /t 1'

Where, of course, Win7User is the username setup for ssh (using bitvise). I had to do similar stuff to get RDP working as well.

I was even able to get around the problem of att.pub.ip.add not being static by using another great feature of the Buffalo dd-wrt router: ddns. I found a completely free way to do it, but that's enough for this post.