WOL takes a three day weekend

Are you doing WOL by ip address or by mac address?  If its by ip, the lease may have expired on the DHCP server and the WOL packet went to limbo.....

Up is the same thanks.

WOL worked all week long but not after weekend. So, I understand about layer 2 but this was working before, is working now, just did not work after weekend off.

IP is the same, not sure about up! Lol.

The computer in question is behind the same switch as my box. I use the nirsoft wake on LAN program when I'm doing it from my computer.

I also need the LANDesk a minute straighter from our domain and I can do wake on LAN across the WAN via machine domain representatives (mdRs) located on each subnet that have the Linn desk agent package.

In this case the machine would respond to magic packet request from the nirsoft program on from my box on the same subnet, and also a response from the LANDesk console. Everything works all week long.

But it seems when the machine is powered off more then a single overnight the machine refuses to wake up. when I couldn't wake it up from the LANDesk console which is located in the city from the server I remote into I check to see if I could wake it up via the magic packet program on my local net.

In both cases everything works fine during the week and then after 4850 our time of the machine being off it would no longer wake up. Once I turn machine on and back off again it resumes The ability to wake up on land either locally or feel LANDesk consul. I don't think it has anything to do with the network I don't think it has anything to do with anything other then something on that box that possibly needs to be changed in bios. But I don't know what

Davis I will look at that bios update. I'm not trying to do a network however just a simple wake on LAN but I can see how something would be related.

Timot.  I wondered that too.  the machine is set not to sleep or hibernate at the OS levelbut of course that's the OS level!

Physically inspecting the box that won't leak wake up, not indicate any type of hibernation or sleep. It just peers to be turned off and nic lights are still lit.

Unfortunately, this box is used during the week and I can't really test prolong off time except over the weekend. So even if the February bios update fixes it I won't know for sometime. But it still enough of a question for me to hold off on pushing out the Dell CCTK making the same changes regarding wake on LAN and S4 S5 sleep off to the entire domain, entire wan. 7010s are our most deployed models.

Davis,

I looked deeper into Feb Bios Update.  Not sure that would help per se. Will try but I am still trying to verify the problem.

The NIC is an intel NIC. by "automatic MAC address" feature are you saying the MAC is now changing??? More on this?

Actually, it looks like the problem doesn't take 2 full days.  When I was initially testing, I would power off and tend of day and WOL the next day.  Now it looks like it may stop working in less than a weekend power off.  Maybe 18 hours.  

And I have confirmed it is also happening on a Dell GX 790.  Like the 7010, it will wake up all day long and after off over night, but at some point, off too long it just wont WOL.

Tamas, back to your hybrid sleep comment. It does appear that it is somehow going into a deeper state.  but S4/S5 sleep is disabed, and I am sure the box is not doing an OS sleep. It was off when I left. I am not sure what else to check.

I am going to dry disabling S3 sleep in BIOS as well.  I was thinking that was a bios setting to not allow user to set in OS, but I am sure that was erroneus.  I know S4/S5 needs to be disabled to WOL - at lease in the 7010.  But lets see if it is indeed going into a  basic sleep (Tamas, I guess I WAS thinking more about OS level.).  It will take a couple days to verify.

When I originally tested, I HAD disabled S3 sleep, but I re-enabled when I saw it was not needed for WOL. But maybe it IS for a WOL after so much time - - - although I haven't seen this documented anywhere.

Crap. Actually, wording in BIOS re S3 sleep indicates it IS related to OS level sleep control.  But I am going to try it anyway.

Good call on hybrid sleep. But isn't that a Windows 10 feature and not on Windows 7? I'll check and if so I will take that into account as well.

But I only want to do one thing at a time so I don't get muddled up on where the solution was.

And I know there's all different kinds of settings for different Dell OptiPlex is some of the older ones have a low-power mode which states just out right it turned off power. When I referenced wake on LAN being on an S4 S fives sleep being disabled, I am for referring specifically to the 7010

Nah, hybrid sleep is available in Win7, too.
Did you read that article at Intel?

After further research, I think hybrid sleep is in regards to sleep state the OS is put in by user.   Yes, that might be a problem if user puts computer to sleep, but in my situation, I know the computer is turned OFF and not in some sort of SLEEP state.  So, I think I need to stick with bios settings or something in nic that needs adjusting.  

For now anyway. Don't have enough test boxes and its hard to set up real world boxes for testing because I want to be able to verify what I can see.  But I will keep hybrid sleep in mind

getting to the intel article now.  Thanks.  Not going to mess with hybrid sleep at this point.

David, yest I looked at the article.  Just doesn't seem to fit what I have in Bios for 7010.  But it does a good job in actually defining the the S4 and S5 sleep.  Right now, on the 7010 I have both disabled. If I enable both NIC LIGHTS will not come on/ If I disable S5 but not S4 Nic lights will not come on.  I must disable  S4/S5 - - and I have found other user comments verifying this in other places.

But its almost like . . . "Turn on WOL and disable S4/5 - that will do it. Problem solved!"   But I am thinking in reality, that will do it maybe over night or during a day when someone leaves early and shuts their box down and you need in later that day - - - - but not, turn back on after it's off for 18 + hours! Like me, I don't think others who have found this answer gave thought too much about different rule sets in play when the box is off for an extended period of time.

And I never answered question about DHCP - - - Yes, lease is pretty long and IP address has not changed anywhere in this scenario.

The IP Address is irrelevant for WOL to work. Just the HARDWARE MAC address is used.

Noci yes I know that. But maybe the person that originally asked but maybe I was verifying status of the box via ping. So I figured I'd answered anyway.

A better check for on time would be: ping  255.255.255.255  followed by an arp -an | grep MA:CD:DR:ES:S0:00
(Assuming it will get an IP sometime).

Is this set?
Enable wake from shutdown by Magic Packet ->Set Enable PME in the adapter's advanced tab

Thanks everyone for sticking with me on this. Only Update so far:


1. No Hybrid Sleep shows up In "My" Windows 7 Enterprise.  All I currently see under Sleep in Power Options is Hibernate and Allow Wake timers. This is on a 7010 where S4/S5 deep sleep is disabledin BIOS and S3 sleep also turned offin BIOS.  S3 Off is not needed to get WOL to work, but I tried it to see of it would help in WOL after extended outage.  No dice. So, maybe Hybrid sleep not being available in OS is because I turned something off in BIOS?  Anyway, since it;s not available, then I guess I dont need to test turning it off.

2. Turning off S3 sleep in bios, in addition to WOL and S4/S5 sleep, does not help anything either.

Machine will still WOL all day long but it now looks like 12+ hours off and its a no go.  Maybe it needs coffee the next morning.

Started an e-mail with Dell Rep. Hopefully he has an engineer in his back pocket.  Waiting.

I hear you David. But , WOL in bios alone does not allow WOL to work, WOL with S4/S5 does. But then, after prolonged off, it fails until box has been powered up and shut down. Then it works again fine.

So maybe I am "sort of" getting it to work by doing what I'm doing.

I have a dialogue opened with Dell rep. We have over 500 7010s alone.

Thanks David. I had read that article. In the advanced tab all I have that is relevant to this is week on magic packet and wake on pattern match. These are both enabled by default. And of course in the power management tab there are three checkboxes, and they are all checked.

The first check box in power management is allow the computer to turn off device to save power. It would seem like THIS is MAYBE someplace I should focus.  But I've tried different settings here as well. They are currently back to all three being checked by default.

PME isn't  even listed. I think that's just another way of saying wake on LAN.

In this default state, with nothing in the adapter settings being adjusted and only wake on LAN enabled and S4 S5 power disabled in BIOS wake on LAN works. But not overnight.

Thanks

Summary. S4/S5 sleep diable and WOL on are the two things that will work on a 7010. So, Savid, your comment about S3/4/5 sleep having nothing to do with it is wrong, in regards to the 7010. But that was with a16 Bios.   But I still plan on testing with latest A21 bios. Maybe that will allow me to leave extended sleep alone in BIOS.  Gave you credit anyway because you were so persistent in helping and, you may still be right in the long run!

S3 sleep in Bios has nothing to do with it.  Left that alone.  

I also could leave everything in Windows 7 alone and not have to change any settings.  

Note:  I'm not saying a machine that went to sleep/hibernate by user would WoL at this point, I didn't really test that.  We can put a power scheme in play for that if we need to, and I will test that further. But I am referring to a machine that is powered off.

Part of this was also muddled by me because I was confusing WoL and WoW (as defined by LANDesk, the management program we use to issue patches - using a local machine representative on the particular subnet to wake up other machine - - or not).  This backwards thinking really messed with me and caused me to question some of the basics.

Thanks to your help, I can configure 7020s, 7010s, 790s, (Yes and even a 745) on Windows 7 Enterprise to behave as expected, both on the local Lan and from the Landesk server on our Wan, via a local machine rep.

We can and have pushed 7010/7020 BIOS updates out if necessary - but I wouldn't trust remote deployment of a bios on a slower machine.  Would you trust a user sitting in front of a computer with a dos screen that says,basically,  "Firmware is being updated and could take 10 minutes. Please don't do something stupid?"

Thanks everyone.

I have a 7010 where WOL works for days/week then just stops working; did you have a clear solution to your problem? Reading through I didn't see that you pin pointed an issue/resolution besides stating it's working now.