I have some more information since the last post but still have not figured out the problem. Nothing solved yet.
If anyone still has advice on how to debug this I'd appreciate suggestions. When I wrote the original post the issue was reproducible. A dozen times I put the computer to sleep or hibernated and each time it woke up a few minutes later, I'd check last wake cause and it reported "network connection". But at this moment that is not reproducible.
P.S. One fun piece of info I discovered now is when I enter in Windows File Explorer...
\\TheNewComputerName
the new computer will wake up. This is great because it is intentional... what you would want. So when the machine is in another part of my house I can ask it to wake up, access data, then later it will hibernate again according to my power settings. Cool!
Thanks,
MC
Calling the posted solution "lame" isn't very nice. It solved my problem as I didn't need finer grained functionality.
It is possible to wake a computer up my creating a scheduled task and enabling" Wake the computer to run this task". You may want to enable the task schedule history and also looking into the event log.
You may also want to disconnect the computer from the LAN prior to sleeping the computer to see if the wake up trigger is external or internal.
rsnelson,
You're right... it wasn't nice. I got frustrated that I kept reading post after post elsewhere where the answer was turning off WOL. I'm going to try your suggestions. Thanks.
Edit 1: I found how to "Enable All Tasks History" (Computer => Manage => Task Scheduler). I'll follow that for a while.
I look upon turning off a feature such as WOL as a work-around rather than a solution. The problem is that it's often very difficult to work out precisely what is actually causing the LAN activity that results in the PC waking. If you had the time you could re-enable WOL, reinstall the OS from scratch with just it's relevant drivers and then progressively install your apps, testing after each install to make sure the PC stayed asleep. Somewhere in there, one or more apps (or parts of your software) are responsible.
I just started noticing the same problem, and I do have a few other computers on the same network, along with the homegroup feature enabled. I am curious to hear how to control this.
This thread covers what I think is every single possibility:
With Intel, disabling WoL in one part of the BIOS isn't enough. You also have to do it in an entirely separate place, if you have it, called Intel ME. See the last post in May from ironcito for details.
Be careful before updating your BIOS -- unless they just released another one, the newest version contains a bug that makes overclocking a problem somehow. On the overclocking threads everyone is advising against updating.
As I already mentioned in the thread above, I have 5 Intel mobos in my network, all of them wol enabled and running win7. At least 3 of them have the latest NIC driver (17.1). They never had problems with sleep, they never had problems with WOL. The current Network is running > 3years, the boards are as old as a DG45ID and as new as the otherwise infamous DZ68DB and an ASUS 77 (replacement for the dz68db) series also with an Intel NIC.
If your system is waking up from sleep with last_wake pointing to the NIC, then most likely something in your network IS waking it up with a WOL.
I don't use home_network sharing though, my network is a normal 'workplace' network with sharing/discovery enabled.
He's referring to the fixed one, but in either case, a BIOS update is irrelevant to this issue.
On the download page for 0042, it states:
Known issue: Intel has identified an issue with this BIOS version, where the ability to overclock the system is not working after the BIOS update. Intel regrets any inconvenience caused by this issue and is working to provide corrected BIOS version as soon as possible.
