• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Setting up Wake on Lan

P

Pinchy

Joined
Apr 29, 2006
Messages
5,105 (0.73/day)
Location
Sydney, Australia
System Specs
System Name UltraPC
Processor E8500 Core 2 Duo, 1333Mhz FSB, 3.16Ghz @ 4.5GHz (got into Windows @ 4.75GHz)
Motherboard ASUS P5Q-e
Cooling CPU Cooler - TT V14 Pro, 2x120mm CM Blue LED fans, 1x90mm CM Blue LED fan
Memory G.Skill Pi 4GB (2x2GB) Dual Channel DDR2 PC8000 (1000MHz), 5-5-5-15
Video Card(s) Sapphire HD4850 512mb with ASUS EAH4850 BIOS
Storage 2x 500GB Seagate 7200.12 Raid 0
Display(s) Acer AL1912, 19" LCD screen
Case Thermaltake Soprano Black ATX case
Audio Device(s) Onboard 7.1, Speakers - 5 + Sub + Monitor speakers
Power Supply Thermaltake 850W Toughpower Cable Management - Quad (2x18A and 2x30A) 12V rails
Software Win 7 Pro x64, MSN, CS:Source, etc etc
On my server (in sig), I want to set it up so it is in standby all the time until something wants to access it over the network (eg, someone chooses remote desktop to connect to it, someone goes to access a file on it over the network, someone goes to print (printer hooked up to server), someone connects to vent server on it (got a full time ventrilo server running on it) ....etc.)

Currently it is on full time. Its not a problem as it doesnt use much power...but for the little use the server gets (ie, gets sent back up once a day), its not worth staying on all day and all night.


Is this in any way possible?

The computer has a WOL jumper for a cable, but I dont know how that works. Also as shown I have a PCI gigabit card attached, to which I am not sure if there is a WOL jumper on it (and I dont use onboard LAN, only the gbit lan card).


Thx :)
 
WOL is a specific signal you send to the computer. Of course you could build something in between that sends the signal upon a certain event, though I wouldn't know of an easy solution for that.
Besides, upon receiving the signal your server has to start up, so the first few connection attempts will probably timeout. Not really handy.
Perhaps stuff like the killer NIC could due this, as they have their own OS on them.
I'd say either run it 24/7 and have it run passive/low power or have some remote option to turn the machine on. This could be another machine (ie small Linux device, NAS, router whatever) sending that WOL signal or some way to hit the on button remotely. For instance, connect your power button to the speaker wires of a cellular phone. Call the phone>computer goes on.
 
You must log in or register to reply here.
Back
Top