Wake-On-Lan not working after a long sleep

Hi All,
I have a relatively old laptop (Lenovo Thinkpad x61) which is running 32-bit Windows 7 and has an intel NIC.

I have been trying to setup wake-on-lan (inmy local network) for this machine for a couple of days and haven't been able to make it completely work. I have upgraded the bios and the drivers on the machine to the latest versions and also enabled WOL in the bios and in the driver for the NIC. When I put the machine in sleep and then after 10 - 15 minutes send a magic packet from a remote machine, it does wake up.

The problem is, when the machine goes to sleep and stays in sleep mode for a long time (over night), then I can't wake it up any more. The machine is still in the sleep mode (it does not hibernate), but I think it turns off something after being in sleep for a while.

Does anyone have any idea what the reason could be?

Thanks,
Amir

I have the same machine(X61) and the same problem. What I have discovered is that when the scheduler wakes the machine overnight for some activity, such as WMCE updates, the LAN device looses the WOL capability. Logging on after this and disable/enable the adapter restores WOL. I set up a simple scheduled task to wake up and then go to sleep and when it fires and the machine goes back to sleep the WOL capability disapears. The machine is connected to a switch which shows the status of the connection. After the scheduled wake/sleep the LED for the port goes out indicating the port is no longer active.

I don't have a solution to the bug but if you look at the tasks that are scheduled or that have run recently and set them so that they do not wake the machine it should circumvent the problem.

I am looking for a real solution but have not found one.

I've spent more hours than I care to relay on this (including tons of forums, buying a second computer to verify, chatting with tech support, etc) and still can't get all the kinks worked out. Long story short, wake on LAN doesn't work after a long delay. I can wake it up from sleep or off for short time (up to about an hour) after that time it enters said state but if it's sleeping or off for longer periods (ie overnight, or during the day while I'm at work) it just won't wake up.

Here are a few pictures of my settings: https://picasaweb.google.com/1174755...CO-M_I3u8LOGCg

To minimize possible router issues I connect my Comcast SB5120 cable modem directly to my machine (both are windows 7x64, one home one pro). I'm using the packet sniffer and able to get the magic packets I'm sending from my Android phone over 3G so I know my firewall settings are correct (I've turned off all antivirus as well). When it doesn't wake up after a long period the first thing I do is run the sniffer and it works so I know my IP didn't change.

I've tried this on a Dell XPS 8300 and an Asus Essentio Desktop (Model: CM6850). I've used both the internal NICs and purchased an Intel PCIx NIC. All with the same outcome which leads me to two possible conclusions:

1. My cable modem is going into a sleep mode (which I doubt cause I don't think it has that ability) which leave one culprit:
2. Windows 7 setting/bug

There has to be a green setting or bug or something that turns off the NIC after a few hours. It's really frustrating as I travel for work and really want this feature to work.

Any advice would be most appreciated...

Hi @mikepfly2, Did you find a solution to your problem? I have the exact same problem...

Nope, never got it to work. Very frustrating. Just gave up...

Check out this thread, seems like it's an ARP issue...
I can't fix it cause I don't have telnet access to my NetGear router (already mailed their support),
But if you do have telnet access to you router, this seems like it should work! let us know if it worked for you...

I didn't see the link to the thread you're referring to, but interested. Not clear what it means to have Telnet access to your router; is that a router setting, a service provider setting, or a LAN NIC setting?

see if your device supports the modes.

source:
Technet.microsoft

command:

powercfg -devicequery query_flags

Returns a list of devices that meet the specified criteria.
Usage:

powercfg –devicequery query_flags

query_flags:

Specifies one of the following criteria:
wake_from_S1_supported – Returns all devices that support waking the computer from a light sleep state.
wake_from_S2_supported – Returns all devices that support waking the computer from a deeper sleep state.
wake_from_S3_supported – Returns all devices that support waking the computer from the deepest sleep state.
wake_from_any – Returns all devices that support waking the computer from any sleep state.
S1_supported – Lists devices supporting light sleep.
S2_supported – Lists devices supporting deeper sleep.
S3_supported – Lists devices supporting deepest sleep.
S4_supported – Lists devices supporting hibernation.
wake_programmable – Lists devices that are user-configurable to wake the computer from a sleep state.
wake_armed – Lists devices that are currently configured to wake the computer from any sleep state.
all_devices – Returns all devices present in the computer.
all_devices_verbose – Returns a verbose list of devices.

Example:
powercfg -devicequery wake_armed

mikepfly2 said:

I didn't see the link to the thread you're referring to, but interested. Not clear what it means to have Telnet access to your router; is that a router setting, a service provider setting, or a LAN NIC setting?

here's the link, forgot to paste it:
networking-forum.com - View topic - (SOLVED) Wake on Lan timeout problem.

And when I say I don't have telnet access to my router it means that the only way I can config my router is using the web interface, but I want to config it using a telnet connection (and I can't).

take a look at the link and u'll understand me

Great, thanks. I'll take a look.