LogMeIn + Wake-On-LAN

Marky

Marky

Marky

Soldato
Joined
16 Apr 2007
Posts
23,440
Location
UK
Hey all,

I've read that LogMeIn has the "Wake-On-LAN" feature, which allows (dependant on your motherboard/BIOS) you to turn on your computer when it is currently off... remotely...

I currently have a...
Asus Maximus Formula Intel X38 (Socket 775) PCI-Express DDR2 Motherboard

Is this feature possible on this board? If so, how can I enable it? AND, is it safe to enable this?

Thanks,

Marky
 
I went into the BIOS and enabled "Power On Ethernet Ports" (Or something like that), for both ports.

Still hasn't enabled Wake-On-LAN... Any other ideas?

I have a Netgear DG834G - incase that makes a difference...
 
Your motherboard does support WOL by PME.

Have you got APM / ACPI enabled?

If you do i think theres a "Suspend to RAM" setting which you have to turn on.

Because you can't power it on from complete shutdown.
 
You will probably need to forward UDP port 9 (using port forwarding on your router) on to the broadcast address on your internal IP range. If your internal ip range is 192.168.0.1 for example the broadcast address would be 192.168.0.255. Because WoL packets are designed to be broadcast and activate the device whose mac address is contained within them, you dont need to direct them to a specific device you just need the packet to be broadcast to all devices on your lan. You could also forward the port on to the specific ip of your machine which would work but would prevent you from waking any other machines on the lan over the internet if you decide to in the future.

If im not being clear what this causes to happen is: The wake on lan packet is sent from Log Me In to your routers IP address, the packet contains the mac address of the machine you are trying to turn on's network card. Your router broadcasts that packet to all machines on your internal network. Only the machine whose mac address is contained in the packet takes any action, the machine powers up.

Sorry if im teaching you to suck eggs

Edit:

This Tool is great for checking if it is working without turning your machine off. Because the packets are being broadcast it doesnt even have to be running on the machine you are trying to turn on, you can monitor wake on lan traffic for all computers from any PC.
 
Last edited:
WILD9 said:
You will probably need to forward UDP port 9 (using port forwarding on your router) on to the broadcast address on your internal IP range. If your internal ip range is 192.168.0.1 for example the broadcast address would be 192.168.0.255. Because WoL packets are designed to be broadcast and activate the device whose mac address is contained within them, you dont need to direct them to a specific device you just need the packet to be broadcast to all devices on your lan. You could also forward the port on to the specific ip of your machine which would work but would prevent you from waking any other machines on the lan over the internet if you decide to in the future.

If im not being clear what this causes to happen is: The wake on lan packet is sent from Log Me In to your routers IP address, the packet contains the mac address of the machine you are trying to turn on's network card. Your router broadcasts that packet to all machines on your internal network. Only the machine whose mac address is contained in the packet takes any action, the machine powers up.

Sorry if im teaching you to suck eggs

Edit:

This Tool is great for checking if it is working without turning your machine off. Because the packets are being broadcast it doesnt even have to be running on the machine you are trying to turn on, you can monitor wake on lan traffic for all computers from any PC.
Click to expand...

The subnet depicts the broadcast and nothing else, without knowing the subnet mask guessing the broadcast is nothing but guess work.
 
Doesnt work with wireless should you be attempting to use that.

I know it sounds silly but I figured I would rule out one question atleast.


Andy
 
ecksmen said:
The subnet depicts the broadcast and nothing else, without knowing the subnet mask guessing the broadcast is nothing but guess work.
Click to expand...

I'd wager 99.9% of home networks run with that subnet so it's a pretty safe guess isn't it.
 
Having thought about the potential issues more I had a quick read and it seems LogMeIn only support WoL when there is another remotable system already on, within the LAN. This means that you don't need to worry about port forwarding through the router and finding your current dynamic IP, but of course makes the service a lot less useful for most people.
 
You must log in or register to reply here.
Back
Top Bottom