• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Getting WOL to work

I have a static IP for my computer and I was wondering whether it is possible to remotely wake my computer up. I've enabled WOL, but I tried ticking "allow device to bring computer out of standby" and that just keeps rebooting the computer over and over again because any network traffic wakes my computer up. Is what I'm describing even possible?
 
Generally, there are two options.

1. Standby. The PC is actually On but after certain amount of time it blanks the screen, switch off the hard drive, and reduces CPU function.

In such a state, the energy consumption of the computer is reduced.

It can resume normal function by keyboard activity, LAN activity, Mouse Activity.

The setting is done in the BIOS for hardware, and in the Power Saving capacity of Windows, (there is an Icon in the Control Panel).

2. Wake On LAN (WOL). The PC is actually Off and it can be switched On remotely by the Network.

If your computer react to General Network Traffic then it is Not Off.
 
Well, I'm clearly not putting it into Standby. I shutdown the computer via hibernate and if "allow device to bring computer out of standby" is on, the computer shutdowns and immediately comes back up.
 
Are you talking about Laptop?

Regular Hibernation saves the Memory as a file on the Hard Drive, and switches off the computer, and thus as nothing to do with Standby, or WOL.

Some Laptops have a propriety system that is a combo of Hibernation/Standby, and the computer is Not really Off.

Might be that your computer does the same.

Try WOL straight. I.e. No Standby, No Hibernation, No gimmicks, just ask Windows to shut down the computer, and check that it is really Off.

When the computer is really Off but connected to the external power, the ATX PSU keeps live voltage line for the WOL, and few other boot functions.

WOL is a Hardware function involving the PSU, Motherboard, and Network Card, and has nothing to do with Windows, or any other OS.
 
No, I'm talking about a desktop.

My goal is to be able to hibernate so that when I boot up my computer is only locked and I can still remote desktop into the system.
 
Well if this is your goal you have to use Standby.

Both WOL, and Hibernation, means that the computer is Off and need to boot in order to start working.

 
JackMDS - if WOL is meant to bring a computer from a "power off" state, and Hibernation saves the contents of the computer's memory to the hard drive, and puts the computer into a "power off" state, then why wouldn't WOL work for the OP's case? As you say, WOL is a function of the motherboard and network card, not of the OS - the motherboard doesn't know that the OS shut down the system after saving the contents of the RAM to the hard drive.

neutralizer - is this on the rig that uses the NF4 SLI Infinity board listed in your sig, and are you using the on-board network card? I assume when you say you have WOL turned on, you enabled that setting in the BIOS?

How is your network set up past your internet connection? You say you have a static IP, but is the PC connected through a router, or is it connected directly to the internet? I use WOL for 2 PCs on my network without any problems. In fact, the DD-WRT firmware I'm using on my Linksys router has a WOL feature built into it that sends the magic packet. Works like a charm.

JW
 
Yes, I'm trying to set this up on the NF4 SLI Infinity board listed, using the on-board network card. When I mean I have turned WOL on, I do indeed mean, I have enabled it in BIOS. But that's what I'm asking, is that it? Or is there more to setting up WOL.

My computer is connected to Internet via a University connection. I don't know the exact details of how it is setup, but I know that my computer has a static IP, i.e. using RD on my IP would work or hosting IIS on my IP works as well.
 
Hmm... I suppose it's possible that there's something with your university's network that could be preventing the magic packet from getting to your computer. If you go into Device Manager, and open the properties window for the onboard network card, check the "Advanced" tab for the network card. See if there are any options there for setting up WOL. I have an Intel PRO series PCI network card in my desktop system, and Intel's drivers call it "Wake on LAN Options"; it might be named differently for your network card. Enable the wake on magic packet setting (if it's there, I'm not sure as I'm not familiar with the drivers for your network card).

Another thing to check for is to see if you have a link light on the back of the system when the computer is "off". If the light isn't lit, then the on-board network adapter isn't getting power when the system's "off" and thus WOL won't work.

Would it be possible for you to try it off the university's network? i.e. borrow a router from someone and plug your desktop computer and another computer into the router, without being on the university network. Leave your computer off and try sending the magic packet to the MAC address of your desktop computer's NIC. If it works there, then try it on the university network. If it doesn't work there, then it's not going to work on your university's network, and you need to double-check the settings.

JW
 
The technology is what it is; wishful thinking would Not change it.

WOL has nothing to do with the regular Network working of the computer.

If the computer is WOL ready and the Magic packet arrives, it uses the Internal Working of the Mobo and the ATX PSU to short the switch On header?s circuit and it switches On the computer. If the computer is already On, then shorting by an additional Magic Packet the On header?s circuit has No apparent effect.

If the computer is already in standby mode, and the standby is configured to resume via LAN, then any traffic at the "Gate" will get it out of standby. That includes the Magic Packet. However, in this instance it is Not the magic packet per-se that moves it out of StandBy but the mere fact that Magic Packet is traffic.

Why it is confusing.

Because many use the term Wake referring to get out of Standby.

Since LAN traffic is part of ?Wake? out of Standby, it leads people to believe that it is the same as Wake On LAN.
 
Originally posted by: JackMDS
The technology is what it is; wishful thinking would Not change it.

WOL has nothing to do with the regular Network working of the computer.

If the computer is WOL ready and the Magic packet arrives, it uses the Internal Working of the Mobo and the ATX PSU to short the switch On header?s circuit and it switches On the computer. If the computer is already On, then shorting by an additional Magic Packet the On header?s circuit has No apparent effect.

If the computer is already in standby mode, and the standby is configured to resume via LAN, then any traffic at the "Gate" will get it out of standby. That includes the Magic Packet. However, in this instance it is Not the magic packet per-se that moves it out of StandBy but the mere fact that Magic Packet is traffic.

Why it is confusing.

Because many use the term Wake referring to get out of Standby.

Since LAN traffic is part of ?Wake? out of Standby, it leads people to believe that it is the same as Wake On LAN.

Except I'm not putting the computer into standby, I'm putting it into hibernate.
 
If the computer is Off through Hibernation, and it boot up when there is general Network Traffic rather than just Magic Packet, then your Network Card,,or and Mobo are working incorrectly and need to be replaced.
 
Back
Top