This is interesting - I've just dug one of our old XP computers out, and WOL doesn't work on that now either, which points the finger back towards S2008 rather than Win7 as being the culprit.
What are you using to send the WOL? wolcmd used to work iirc in 2008R2.
Here's a good guide which is correct in its explanations.
Depicus Wake on Lan Monitor/Sniffer Or just install a packet capturing utility of your choice and sift through the results. If it isn't working with machines that worked before though I would be questioning whether or not it's even making it through.
Did the IP of the server change that you're using to send WOL out from, or were there any changes in the switching configuration? For WOL to jump subnets it requires configuration on the switches.
The server's firewall & Simple TCP settings could affect it though. I'll try the packet sniffer to see if these are actually going anywhere...
I've just tried the WOL command from a client PC, and it worked fine, so it is something on the server blocking it from going out.
Re your Stone PC's Nick, check to see if there is an update for the NIC drivers.
When we put in some Lenovo's earlier in the year, we found that the WOL wasn't working once Windows 7 was installed via WDS (was fine straight out the box)
Found newer drivers for our Marvell Net yk62x86 and it started working correctly again.
I have tried the latest drivers on both the Intel and Realtek sites (they have different "latest" versions), but neither work. As I said just now (you might not have seen it before posting), it looks like the server is blocking the signal - even though it reports 'success' in the CMD window - as the command runs just fine from a client.
The batch files run just fine off our Member Server. Wish I'd thought to try that in September!
Spoke too soon - the batch files run fine if executed by double-clicking on them, but not when set as scheduled tasks. Any ideas?
Sorted now. I've had this issue with scheduled tasks before, with it being very fussy about how it is set up in terms of whether it runs only when logged in, with highest credentials, etc. so I went through each possible permutation until I found one which worked!