How to turn on pc remotely (Wake On Lan)

[speedy_s]

Hello,
I have a:

AMD 64 3000 (Newcastle)
ANTEC Sonata I (380 watt psu atx 1.0 ?)
ABIT KV8 Pro motherboard
Windows XP Pro
Onboard network card

Now how would i go about turning on pc remotely. I have had a look in the bios>power management but couldn't find an option for WOL, the closest i could i find was wake on pci (as onbard is pci based). Does this mean i can't use WOL? I thought all modern motherboards supported WOL?!

If motherboard does support WOL, how do i set my computer up to turn on by the web (i found a website which lets u ping/send magic packet but forgot the name!). Also, i am behind a router (Draytek Vigor 2600), how do i set that up for allowing pings/magic packets form the net?

Thanks a lot.

[herulach]

you just need to forward any port you fancy to your pc, then either use a little app called wol command(what i use) or whatever website you like to send the magic packet, ensuring you have your MAC address to hand. I would have thought the board would support WOL but it may not, does it say anything in the manual?

[explicitlyrics]

Yes, I would have thought it would support WOL aswell, however, you are looking in the right place and it does seem that it isnt there... To be fair you can pick up a LAN card for £4 online nowadays and that would be a possible solution to the problem....

[ajbrun]

you just need to forward any port you fancy to your pc, then either use a little app called wol command(what i use) or whatever website you like to send the magic packet, ensuring you have your MAC address to hand. I would have thought the board would support WOL but it may not, does it say anything in the manual?

I tried that, and have tried using both a downloadable program, and a website thingey to send the packet, but it never works. My router seems to clear it mac table, or something after a length of time, so that it works only shortly after I turned my PC off, but if I wait overnight, it just ignores it.

Does anyone know a remedy?

[speedy_s]

Do u think a BIOS update would enabe WOL support?

[herulach]

I tried that, and have tried using both a downloadable program, and a website thingey to send the packet, but it never works. My router seems to clear it mac table, or something after a length of time, so that it works only shortly after I turned my PC off, but if I wait overnight, it just ignores it.

Does anyone know a remedy?

Port triggering rather than forwarding might work, as IIRC it sends it round the whole network, not just to a specific address.

[Ross Stone]

Does anyone know if Wake on Lan will work across the internet?

I use VNC to remotly operate the computer, but sometimes I forget to turn the computer on before I leave so a way of remotly turning it on, say from the office would be useful.

[herulach]

yes it does, but you need to set up port forwarding on your router.

[Ross Stone]

Thanks, I am presuming herulach that the port I need to forward is different from one app that sends the wol command to another app?

Oh darn, don't think my onboard card has wol. Guess I am in the same boat as speedy s.

The only way round that is to get a cheap ethernet card I guess.

[latrosicarius]

Hey guys, it's none of those things... Wake on LAN is controlled by your NIC adapter's driver, not third party software.

Just do the following:

1.) START
2.) CONTROL PANEL
3.) NETWORK CONNETIONS
4.) Right click on LOCAL AREA CONNECTION and select PROPERTIES
5.) Click on CONFIGURE at the top
6.) Go to the POWER MANAGEMENT tab
7.) Check the box that says "Allow this device to bring the computer out of standby"

BTW, this won't work if the computer is OFF, only sleeping. This also has nothing to do with ports on your router... the NIC adapter will detect that an incomming transmission has been sent, and instead of ignoring it, it will bring the computer out of standby to accept it or block it, depending on your software firewall settings. It should be transparent to your router and applications, and remote desktop should be able to connect to it the same way it would if it was awake to begin with.

I hope I helped with your question and didn't miss the topic completely...
cheers

[herulach]

Hey guys, it's none of those things... Wake on LAN is controlled by your NIC adapter's driver, not third party software.

Just do the following:

1.) START
2.) CONTROL PANEL
3.) NETWORK CONNETIONS
4.) Right click on LOCAL AREA CONNECTION and select PROPERTIES
5.) Click on CONFIGURE at the top
6.) Go to the POWER MANAGEMENT tab
7.) Check the box that says "Allow this device to bring the computer out of standby"

Thats only for standby, not wol

BTW, this won't work if the computer is OFF, only sleeping. This also has nothing to do with ports on your router... the NIC adapter will detect that an incomming transmission has been sent, and instead of ignoring it, it will bring the computer out of standby to accept it or block it, depending on your software firewall settings.

The router needs to know to forward the magic packet

It should be transparent to your router and applications, and remote desktop should be able to connect to it the same way it would if it was awake to begin with.

WOL is from off, what youve described is resume from standby.

[latrosicarius]

I'm sorry, I didn't think there was a difference between Wake from Standby and Wake on LAN. I guess I wasn't that helpful after all

Thanks for the info though

[herulach]

np man, that was an unnecessarily harsh reply tbh, aj, if you check this again, ive looked in my router set up, and it is port triggering not forwarding i use, it happily broadcastsit everywhere then.

[badass]

Port triggering rather than forwarding might work, as IIRC it sends it round the whole network, not just to a specific address.

I cant see port triggering working for this full stop. Port triggering is something that is initiated from behind the router by the client doing something. In this case, the client is switched off.
Also, clearing the MAC table should not be a problem. If the router does not know a MAC address, it broadcasts the packet to all ports.

[herulach]

I cant see port triggering working for this full stop. Port triggering is something that is initiated from behind the router by the client doing something. In this case, the client is switched off.
Also, clearing the MAC table should not be a problem. If the router does not know a MAC address, it broadcasts the packet to all ports.

/goes back to look at his settings

there is a forwarding rule setup too that'll be the one labeled wol, doh.

[drbob]

Also, clearing the MAC table should not be a problem. If the router does not know a MAC address, it broadcasts the packet to all ports.

Are you sure about that? I think most NAT routers just drop the packet if they don't know where to send it. On my old router (a linksys befsr41) I had to forward an external port to the an internal broadcast address (192.168.1.255) to get a packet sent to all ports. My new router (a linksys WRT54G) doesn't support forwarding to a broadcast address and I've been unable to get WOL working from outside the LAN.