RM One PCs WOL

[rich_tech]

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.

[enjay]

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).

[rich_tech]

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.

[enjay]

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?

[SYNACK]

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.

[enjay]

One, turn the firewall back on for the server

You're thinking turn it on and then specifically allow the magic packets through? Is that different to having it turned off?

 

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.

Everything is on the same VLAN and subnet.

[SYNACK]

You're thinking turn it on and then specifically allow the magic packets through? Is that different to having it turned off?

 

 

Everything is on the same VLAN and subnet.

 

Just a much better idea having it on and besides there may be another firewall active, do you have AV on there, these often ome with firewalls that impose themselves on top of the Windows firewall that could quite easily be blocking it. I'd create a rule allowing that application as it produces a UDP packet on one of several ports and it can get tricky pinning down which way it is using without a packet sniffer. That kind of traffic may even be filtered if the firewall is off due to its nature (connectionless) hence the success in generating the packet but no idea of failure.

 

Have you tried a different application like poweroff ?

[enjay]

The server does (of course) have AV on it, however it is the same AV which is present on the client PC which I've just successfully used to execute the WOL command.

 

Yes, I've tried 4 different WOL applications; the native one in Windows, mc-wol.exe, WOL2 (Wake On Lan Tool 2 .NET | Free System Administration software downloads at SourceForge.net) and SpecOps GPUpdate.

Edited May 8, 2012 by enjay