WOL Issues

[mrbios]

This one is driving me crazy, this is the scenario:

• One IT suite out of 5 won't wake on lan via imperos automated method
  
• ONE PC in that room turns on every day, yet the rest of the room doesn't
  
• If you connect to a PC on the same vlan and send the WOL signal via impero from it, they all turn on.
  
• They don't wake up if you manually send the WOL signal from impero from a different vlan.
  
• If i run wake on lan via the right click tools in SCCM, they all turn on (SCCM is on the same vlan as the impero server - although sccm stats port 12287 o_O)
  
• Another IT suite is on the same vlan and all turns on fine.
  
• The whole suite is the same spec, and matches the spec of one other IT sutie on another vlan that turns on fine
  

I can't work this one out, it annoys me that every morning that room has to be manually told to power up, even though one lonely PC in there turns on every day.

 

I've got the following enabled on the router:

ip udp-bcast-forward

ip directed broadcast

 

Then the following enabled on the vlan the impero server is on:

ip forward-protocol udp 172.18.xx.255 7

ip forward-protocol udp 172.18.xx.255 9

where xx is the vlan the WOL signal is directed at. This is correct isn't it? (granted it must be working as literally everything else in the school turns on fine!)

 

I've also restarted the switch they're connected to.

 

Any suggestions? The only thing i haven't checked is the bios version in that suite compared to the bios version in the suite that works fine., but I'm pretty sure this was working at some point with this hardware about 6-8 months ago.

Edited February 2, 2016 by mrbios

[Steve21]

When you say 1 machine wakes, is that the same switch as the others? or same VLAN but different switch?

 

Same question to the running WOL via same VLAN etc

 

Steve

[mrbios]

When you say 1 machine wakes, is that the same switch as the others? or same VLAN but different switch?

 

Same question to the running WOL via same VLAN etc

 

Steve

 

Same switch, same hardware, same vlan. No different to any of the other PCs in the room.

 

Then next door, a different IT suite, on different hardware and a different switch, but on the same vlan, wakes fine. Same model of switch and identical settings though. Both switches for the two rooms on that vlan feed back to the same central switch for that building, so no differences in connectivity either.

[pleach85]

Have you run something like wireshark on the affected computers to make sure they are actually receiving the WOL packet when sent from Impero?

[russdev]

Disclaimer obviously this based on info when use to work there maybe out of date.

 

Also a workaround. As one PC starts up in the ICT. Send another scheduled job ten mins after the first. As way Impero use to work was if couldn't wake the machine up it would try to find a machine in the the same VLAN running Impero. Then use that to send the WOL command.

 

Russ

[mrbios]

Have you run something like wireshark on the affected computers to make sure they are actually receiving the WOL packet when sent from Impero?

 

WOL packets definitely being received by the clients, tested with wireshark, wake on lan sniffer and magic packet.

 

When i sent a WOL packet to the machine using "WOL Magic packet sender" remotely from the server using port 9 or 7 both packets are received by the client. Which suggests there's no funny business going on with packets being blocked.

 

If i leave the machine running with wol packet sniffer and send a WOL signal using impero, nothing happens.

[Julian]

WOL and vlans are a challenge. WOL is only layer 2, so will not be routed between vlans, It is possible to get WOL to work, but the program sending the magic packet must include a suitable layer 3 ip address (either the old ip address of the computer, or the vlan broadcast address).

 

I used some PowerShell to query DHCP for both the ip address, and mac address, which was then used to generate the magic packet.

[mrbios]

WOL and vlans are a challenge. WOL is only layer 2, so will not be routed between vlans, It is possible to get WOL to work, but the program sending the magic packet must include a suitable layer 3 ip address (either the old ip address of the computer, or the vlan broadcast address).

 

I used some PowerShell to query DHCP for both the ip address, and mac address, which was then used to generate the magic packet.

 

The packets are being routed correctly, i can see them being sent and received from 172.18.66.0 where the server is sending the packet from, and being received on 172.18.72.0. That's using either SCCM or a magic packet sender utility, on both udp ports 7 or 9. Both work.

 

However when impero sends those packets, i see nothing on the receiving end.

[nelliott]

Hi All,

 

Did you find a solution to this issue?

I am in the same position, I've got 12 desktops which will WOL using Impero, but the rest won't.

From monitoring the packets through Wireshark, I can see the packets are getting to the relevant machines however, they just won't boot up.

 

Any ideas?

[mrbios]

Nope, even had impero support test a few things out....weird thing is, if i shutdown one machine in the day, it will WOL back on perfectly fine, but first thing in the morning when the whole room needs to be woken up, nothing happens.

 

WOL clearly works from both impero and other sources, but those specific machines just won't boot after a whole night of being off, and what's more frustrating is, it's an issue that started completely at random! the impero update to 5.1 is the only thing i can remember changing....

[free780]

Are you using 802.1x with a guest vlan? If so the packet needs to be from a wol server in that vlan rather than the one the PC usually is in.

[_techie_]

Have you checked driver versions on the non WOL PC's against the working one? Go through device manager and check out the driver versions and the advanced tab.

 

Enable PME if disabled

Disable green Ethernet and make sure wake on magic packet is enabled.

 

The BIOS also needs S5 Wake on LAN or remote wake up enabled depending on BIOS and hardware MFR.

 

Hope this helps :-)