TMODAlpha (2nd May 2012)
If they were working on CC3 and not on Windows 7, it has to be a software issue. The drivers could affect it as a dodgy driver might not be applying the relevant tickbox settings (above) to the actual hardware before it enters sleep. Can you post the exact name of the card as it appears in device manager?
TMODAlpha (2nd May 2012)
Yeh, true. I didnt think about the driver changing something on the card, but that makes sense.
The thing that doesnt make sense is that a room with the same machines, but with Intel E1000 cards in, doesnt wake on those cards either. Will all the relevent bits enabled.
The onboard cards in the ones im really having problems with is a Marvell Yukon 88E8053.
Guys, you are amazing. It was the driver. Grabbed the one from the Yukon site, and all is well in computer land. The new driver gives an extra wake from shutdown option. Never thought a driver could effect it while it was switched off. Crazy.
Thanks for your help.
Good to hear. Could you post the link to the driver you used for the next person who has the same problem?
AngryTechnician (2nd May 2012)
Having the exact same problem here since moving to Windows 7, Intel and Realtek cards affected - I'll go check for updated drivers...
Having the exact same problem here since moving to Windows 7, Intel and Realtek cards affected, but new drivers hasn't helped. The LAN link lights are still on with the Intel ones, but off with the Realtek one.
I could be onto a loser with the Intel ones (RM PCs with Intel DG845 boards, as there aren't Win7 drivers for those), however the Realtek ones (on an Intel DG41AN board) do have Windows drivers.
Annoyed by this, as it is definitely a driver question, since all these PCs WOLed under XP.
update the NIC Drivers, if their older RM Ones you will find most prowin32 intel drivers work, doesnt have to be specific ones, as long as their PRO chipset ones we found a generic one works fine, (obviously check which ones are installed first), it gives you a better options screen than the default windows properties for the NIC, we found here that unless we installed them getting them to WOL wouldnt happen.
XP drivers wouldn't install, which doesn't entirely surprise me.
@rich_tech Thanks. Can I ask which drivers you're using, or where you got older ones from? I can only find the latest ones online.
As an aside, my PCs aren't RM Ones, by the way (some of them aren't even RM).
I just downloaded generic intel PRO network card drivers from the website, ours show up as intel 82566 cards in the machines, the drivers will work on a multitude of intel network ports and cards, if your still stuck I can sort out getting the ones I use onto a website when im back in work if needs be.
Right, it is definitely something server-side as the Magic Packet commands work when sent from a desktop. The Windows Firewall on the server is off already - what else could be blocking the signals?
One, turn the firewall back on for the server.
Two, check to make sure that your switches are not configured to block broadcasts, if the workstations are on a different VLAN/subnet you may need to configure them to allow subnet broadcasts and use something like PowerOff which can specify a layer 3 subnet IP address to broadcast to so that it will make it across the VLANs to the segment your workstations are on.
There are currently 1 users browsing this thread. (0 members and 1 guests)