Wake-On-Lan not working

[RightRozz]

I was trying to set up wake on lan for my pc before I go on vacation. I am having some issues. I went into device manager and enabled wake on lan and wake from magic packet and all that. I also enable wake from PCI and PCIE devices in my bios ( I have an Asus board). I port forwarded port 9 on UDP but when I start the WOL sniffer and send the packet it wont detect it. I dont know if this also matters but when I turn off my pc the ethernet light is off. Please help!

 

[kanewolf]

If the ethernet light on the router is OFF, then it won't work. You need to have a link light for WOL to work.

 

[RightRozz]

If the ethernet light on the router is OFF, then it won't work. You need to have a link light for WOL to work.

No the router light is on. The status light for my ethernet port on my pc is off.

 

[kanewolf]

If the ethernet light on the router is OFF, then it won't work. You need to have a link light for WOL to work.

No the router light is on. The status light for my ethernet port on my pc is off.

The Wikipedia article on WOL has an interesting troubleshooting technique. Use a packet capture tool like wireshark with the computer ON to determine if the packet is making it to the desired host. If so, then you can concentrate on problems on the host end.

 

[RightRozz]

If the ethernet light on the router is OFF, then it won't work. You need to have a link light for WOL to work.

No the router light is on. The status light for my ethernet port on my pc is off.

The Wikipedia article on WOL has an interesting troubleshooting technique. Use a packet capture tool like wireshark with the computer ON to determine if the packet is making it to the desired host. If so, then you can concentrate on problems on the host end.

I already was using a sniffer. It is made for WOL. Can be found here Sniffer. After using this I still never got the packet.

 

[bill001g]

Your main problem is WoL is not designed to be used the way you are.

The key mistake is to assume that the device has a IP address. It is not running any form of OS it only has a mac address. In theory it could be sleeping for a year and get a different IP every time it wakes up and still work.

Even if you used a mac address technically it should not work.

The reason it does is some pc accept WoL packets that do not strictly follow the standard so for periods of time until ARP and MAC entries in the router exist you can make it work with port forwarding when the entries time out it no longer works.

a WoL packet is suppose to be sent to the broadcast mac address and within the packet contain the actual mac to be woken. To do this remotely you need a special feature called directed broadcast that even if the router has is generally disabled because it is a security exposure where someone can easily DoS your network.

There are hacks people use that work on some routers to place static ARP entries in the router set to the broadcast mac and then port forward to those static arp entries to make this work.

Generally the way this is done securely in a commercial network is a special server is placed on the network you have other machines you wish to wake and you ask that machine to send the special packet. Of course in a home environment generally if you are going to have to leave a machine up then you might as well leave the machine that you are trying to wake in the first place.