|
|
 | ||||||||
|
||||||||
|
|
 |
|
Wake Up and Smell the Network More and more people want to take advantage of remote access, but your PCt has to be on to be accessible, right? Well, yes and no, because a technology called Wake on LAN. by Joseph Moran
In the ongoing discussion about the problem of climate change, much is made of our penchant for gas-guzzling vehicles. But another major culprit is our use of electricity — the desktop PCs found in a typical home or office can consume a lot of energy, especially if they're powered on 24/7. Of course, you can curtail the amount of power a system uses by setting it to automatically go into standby or hibernate mode, or even simply shutting it down during extended periods of disuse. You might also think that a disadvantage of doing this is that it precludes you from having remote access your system — after all, it has to be on to be accessible, right? Well, yes and no, because a technology called Wake on LAN can let you bring your PC back to life no matter what power-saving mode it's in — even if it's completely turned off. In order to take advantage of Wake-on-LAN, your system's BIOS, Ethernet adapter and network drivers must all support the feature, but as long as your system is less than about five years old, it should be compatible.
(Note that the steps outlined below assumes a system running Windows XP with a wired Ethernet connection — it doesn't work with Wi-Fi adapters — and that you use a broadband router.)
System Prep The next step is to make sure that Wake on LAN is enabled on your Ethernet adapter. Open up Device Manager, find the entry for your adapter, and double-click it. Then click the Advanced tab, look for any settings that begin with "Wake on," and set them all to Enable. Now click the Power Management tab, and make sure there are check marks next to Allow the computer to turn off this device to save power, Allow this device to bring the computer out of standby, and Only allow management stations to bring the computer out of standby. In order to activate Wake On LAN on a system, you'll need to know its MAC address, which you can look up by running IPCONFIG /ALL from a command prompt. Look for the entry marked Physical Address and copy down the six pairs of alphanumeric characters displayed — you'll need this information later.
Network Prep Now you need to create a port forwarding rule in your router so the Wake On LAN signal can be directed to the right system. Choose a high numbered port to avoid conflicting with any standard network traffic common on lower ports (like port 80 for HTTP, 53 for DNS and so on) and make sure the traffic on that port goes to the IP address you specified earlier. The exact steps for setting up this rule vary depending on your router, so check your documentation. Now comes the tricky part, because in order to access your system from outside your network you have to know the public IP address your ISP has assigned you. That's easy enough to look up (you'll find it listed within the Status page of your router), but if your ISP is like most that IP address probably changes every so often, which means the address you see will be valid only for a limited time. The simplest way around this problem is to set up an account with a Dynamic DNS provider, which will track your network's IP address changes and let you access it network using a consistent domain name. (For more details on Dynamic DNS and how to set it up, check out our recent article on the subject.
You Can Do Magic To send your system a magic packet, enter the MAC address you copied down earlier, your network's IP address (or Dynamic DNS domain name) and the port number you chose into the appropriate fields (you can leave the Subnet Mask field as is). Then click the Wake On Wan button, and within a second or too your system will begin to power up. There's no way to get an acknowledgment that it actually worked, but if you have another system you can test it right from home. A couple of final thoughts — when waking your system from on the road, remember that it can take several minutes for the system to fully power up and re-establish all its network connections, so it may be a little while before it responds to your attempts at remote access. Also keep in mind that in order for Wake on LAN to work, the system must obviously remain plugged into AC and your router. As you can see, setting up Wake on LAN takes some doing, but once it's done you can save some of electricity and money it takes to run your PC without sacrificing the capability to remotely access it when you need to.
Joe Moran is a regular contributor to PracticallyNetworked. For more help, don't forget to try one of our PracticallyNetworked Forums.
|
| Home | Networking | Backgrounders | Internet Sharing | Security | HowTo | Troubleshooting | Reviews | News | About | Jobs | Tools | Forums |
