Категория: Windows: Администрирование
Запрошенная страница удалена, переименована или временно недоступна.
Попробуйте выполнить следующее.
Internet Information Services (IIS)
Технические сведения (для сотрудников службы поддержки)
Wake-on-LAN (WOL) is a great feature of PCs which allows you to wake them up from sleep or shutdown over your local area network or over the Internet. It is like a remote power on button. If your hardware has WOL support, you can power on the computer remotely using any of the dozens of freeware tools available on the web to initiate the wake up event. In this article, I will cover the basic steps which are required to configure WOL under Windows 8 and Windows 8.1.
Tip: see the most comprehensive list of shell locations in Windows 8Tick the 'Simple TCPIP Services' option:
That's it. Now you need to write down the MAC address of your network adapter somewhere. To see it, press Win + R shortcut on the keyboard and type msinfo32 into the Run box. The System Information application will be displayed on the screen. Navigate to the Components -> Network -> Adapter and look for the MAC address line of your adapter:
Tip: Select the line on the right and press Ctrl+C on the keyboard. It will copy the MAC address to the clipboard in the following format:
MAC Address ?D4:3D:38:A6:A1:80?
On another PC, download this little freeware app called WolCmd. It is my recommended command line utility which must be used according to the following syntax:
So in my case, to wake up my own PC, I have to run it as follows:
While typing the syntax, just delete the ":" char from the MAC address and use your actual network parameters.
In case you don't know what is subnet mask and your IP address, the Network -> Adapter section of System Information also shows that. Look for the values: IP Address and IP Subnet. You can copy them using Ctrl+C.
That's it. Now you can create a shortcut to run wolcmd and wake up your PC via the network with one click.
Recently I bought myself a new computer at home and I wanted to access it from remote. LogMeIn (Free) is my preferred choice! You can also do it by using TeamViewer. Another option is tunneling. but that seems a bit overkill.
In order to properly configure your system to wake up when a Magic Packet is received, a set of different configurations changes is required.
Why is it so important to hibernate your computer when you are willing to wake it up?
To be honest, I had the same question when my device did not start. Eventually I stumbled across the following Microsoft Knowledge Base article .
A snippet from the KB:
In Windows 7. the default shutdown operation puts the system into the classic shutdown state (S5), and all devices are put into the lowest power state (D3). WOL from S5 is not officially supported in Windows 7. However, some network adapters can be left armed for waking if enough residual power is available. Therefore, waking from S5 is possible on some systems if enough residual power is supplied to the network adapter even though the system is in the S5 state and devices are in D3.
In Windows 8 and Windows 8.1. the default shutdown behavior puts the system into the hybrid shutdown state (S4), and all devices are put into D3. WOL from S4 or S5 is unsupported. Network adapters are explicitly not armed for WOL in either S5 or S4 cases because users expect zero power consumption and battery drain in the shutdown state. This behavior removes the possibility of invalid wake-ups when an explicit shutdown is requested. Therefore, WOL is supported only from sleep (S3) or hibernation (S4) states in Windows 8 and 8.1. .
It’s necessary to trigger the magical packet within the same lan segment as it is broadcasted to all devices within the network segment. Packets will not be routed to other network segments, as these are not recognised on layer 3! I configured my routers firewall (port forwarding) to redirect all data received on the public IP port 5001 to my NAS on port 5001. On the NAS I use a DynDNS solution, such as synology.me or dyndns.org to easily access it from everywhere. Once logged in, I can start a little application to send the magic packet. The application needs to be downloaded from the developers website and requires a manual installation. The only remark I can add is. when the software is installed reboot the NAS to properly start the services (in my case these were stuck after installation).
I've tried to reproduce the issue here on our premises. Here's the configuration:
Desktop computer with Windows 8.1 installed, including recent updates.
Motherboard: Asus P5QSEPlus with "Power on by PCI devices" enabled in Bios Settings.
Network card: integrated, with "Shut down WoL", "Wake on magic packet" and "Allow this device to wake the computer" enabled in the properties.
yes the issue is with 8.1 only, this pc used to have windows 7 and worked fine. it have since installed windows 8 and 8.1 (performed fresh installs not upgrade). I can wake up all my other windows 7 pc's without a problem.
when I send wake on lan to 8.1 pc the system wakes, yes monitor and login screen are fully working. the system is on dhcp but the ip doesn't change. I use hostname to connect not ip (name resolution is ok) the service is started after waking up but if I restart the service and then try to connect it works, but I need to restart the service first even though its already started.
unfortunately I decided to go back to windows 7 and reinstall windows 7 on that pc. to be honest if you say you don't have issues and/or cant reproduce this specific issue, I believe you. its probably something with the operating system. there are lots of issues I see with windows 8 and 8.1 not related to remote utilites so its most likely a Microsoft issue or some other OS related issue. I have issues with some drivers, built in video app, homegroup anomalies, skydrive integration etc. windows 8 and 8.1 in my opinion is a POS.
but I do love remote utilites. works great on all my other pc's
It is powerful and convenient feature that enables users to remotely power up their computer over a network, saving energy while also allowing remote access to the computer when needed.Windows 10 Wake-on-LAN Problem
Wake-on-LAN (WOL) does not work or stopped working in Windows 10 after upgrade from Windows 8.1 or Windows 7. In my case, I use Realtek PCIe GBE Family Controller.
Even though I did all settings for Wake-on-LAN such as disabling turn on fast startup, configuring adapter options related to WOL, and etc, WOL is not working.
Previous OS: Windows 8.1 Pro x64
Current OS: Windows 10 Pro x64
Mainboard: Asus H87-Plus
NIC: Onboard Realtek PCIe GBE Family Controller
NIC driver version: 9.1.401.2015 released on April 1, 2015
Realtek Ethernet Card driver that comes with Windows update causes the problem.Solution to Wake-on-LAN Problem After Upgrade to Windows 10
Install Realtek Ethernet Card driver ( Even though it is older than Microsoft driver) from Realtek Website.
Related Article How to Configure Wake-on-LAN in Windows 10 and Windows 8.1
Note: Make sure you enabled WOL feature for your NIC.
I hope this article is helpful for you. If you liked it or found useful, feel free to like or share it.
Your Windows 8 device can be used in different ways and for different tasks since Microsoft added useful in-built features that can ease your daily schedule. But, maybe the most popular feature that can be used on Windows 8 and Windows 8.1 is Wake-On-Lan. Unfortunately, more and more users are complaining about WOL issues, which mean that we must find a way to fix these problems.
So, due to same reasons, if your wake on lan feature isn’t working on your Windows 8 or Windows 8.1 device try to use the guidelines from below in order to easily fix your problems. Wake-on-lan is a Windows default feature that basically allows a computer to be turned on by a network message. This awakening message will be send from a program that is running on another computer, laptop, tablet or desktop, which is located on the same local area network. Also learn how to prevent Windows 8 from automatically rebooting after updates or how to emergency restart Windows 8 .
Wake on lan can be easily and safely used on any Windows 8 and Windows 8.1 based devices, though in rare cases you might notice that you can’t use this protocol. If that happens, don’t panic and just try the steps which are being detailed below.How To Fix Windows 8 Wake-On-Lan Not Working Disable Fast Startup feature on your device
Fast startup is a feature that can be activate or disabled from your Windows 8 settings. With fast startup enabled you will be able to power off your device faster than usually. But, in some cases the WOL protocol will not work when the mentioned feature is activated. Therefore, try to disable it for fixing your problem:
Now, the Wake-on-Lan feature should be working just fine on your Windows 8 or Windows 8.1 device. If these steps aren’t useful for you, try to put your computer to hibernate instead of shutting it off – usually this is resolving all the problems. Also, use the comments filed from below if you have questions or if you need our assistance.
Over the years, I’ve accumulated a number of computers, mobile devices and streaming boxes in my household. But I still like to keep my photos, music, movies and documents centralized on my main computer. Thanks to Windows HomeGroup sharing and iTunes Home Sharing, I don’t have to walk all the way up to my office every time I want to access those files. However, I do have to ensure that my main computer is powered on. Now, I could leave my PC on 24/7, or even schedule my computer to sleep and wake automatically at a certain time of day. But the method that’s easiest on my electricity bill is to only turn my computer on when I need it. Thanks to wake-on-LAN, I can do that without getting up off the couch.
The wake-on-LAN (WOL) protocol has long been used in IT settings to remotely manage computers, and it’s just as handy at home. With wake-on-LAN enabled, your computer will “listen” for a “magic packet” containing its MAC address while it is in sleep mode. The computer can be woken up by sending it a magic packet from another device on the network.
There are some caveats to this: First, wake-on-LAN only works with a wired Ethernet connection. There is such a thing as “wake on wireless LAN” (WoWLAN) but it’s much more complicated, and depending on your hardware, perhaps not even possible. Secondly, wake-on-LAN typically only works on your local area network. There are ways to configure wake-on-LAN to work via a magic packet sent from outside your home network via the Internet, but there are additional security considerations to factor in.
That all being said, WOL can be very useful for a house with many computers. Read on to learn how to set it up in Windows 8.Enable Wake-on-LAN in Windows 8
Open Device Manager by pressing Win + X and clicking Device Manager.
You can also find it by right-clicking on the Start screen, choosing All Apps –> Control Panel –> Windows System –> Device Manger.
Expand Network Adapters. Look for your wired Ethernet network adapter (not to be confused with your wireless LAN adapter), right-click it and choose Properties.
Click the Power Management tab and check the boxes Allow this device to wake the computer and Only allow a magic packet to wake the computer. Click OK.Find Out Your System’s MAC Address and IP Address
Next, you’ll need to know your computer’s MAC address (physical address) and IP address. To find the MAC address, make sure your computer is connected to your router via a wired Ethernet connection. Disconnect any wireless connections you may have been using.
Now, open the Network and Sharing Center from the Settings menu. In the upper-right pane, click on the Ethernet connection.
In the Ethernet Status window, click Details…
Your MAC address is listed next to Physical Address.
Your IP address will be the IPv4 address or IPv6 address, whichever is applicable. Note that this is the local IP address assigned to your machine by your router—it’s not the IP address that your computer will show up with on the Internet.
Write both your MAC address and IP address down and use them in the next section.Send a Magic Packet
Any device connected to your local area network can send a magic packet. My favorite way to wake my computer remotely is from my iPhone. I use Mocha VNC Lite. which is free. I also use Mocha VNC to remotely control my computer once it wakes up (note: I run TightVNC Server on my computer to allow that to work).
To send the magic packet from Mocha VNC Lite, simply configure a new VNC host by plugging in your computer’s IP address (or computer name) and the MAC address.
Once you’ve given the program the correct IP and MAC address, you can send a magic packet using the Wake feature.
You may not get any confirmation that the WOL magic packet was received successfully, but if you try to initiate a VNC session, you’ll be able to tell if your computer is on or not.
If you want to wake a computer from another computer, you can use WOL Magic Packet Sender. a free Windows-based program.Notes and Troubleshooting
Wake-on-LAN can be a little bit finicky, depending on how your system is built and configured. If you are having trouble with this tutorial, try some of these fixes:
Disable Fast Startup
One of Windows 8’s claims to fame is its fast startup, which uses a “hybrid shutdown” similar to hibernation whenever you “turn off” your computer. This hybrid shutdown / fast startup does speed up your boot times, but it has been known to interfere with wake-on-LAN. Personally, I didn’t have to do this step to get wake-on-LAN to work on my Windows 8 laptop. But if you have trouble, you might want to try this.
To do it, go to Control Panel –> Hardware and Sound –> Power Options and select Choose what the power buttons do .
Uncheck the option Turn on fast startup (recommended ). Note you may have to click Change settings that are unavailable at the top. Otherwise, the option will be grayed out.
Enable Wake-on-LAN in the BIOS Setup
If you are running Windows 7 or earlier, you may need to tweak your BIOS settings to allow wake-on-LAN. Windows 8’s boot loader precludes any tinkering in the BIOS, but for earlier versions of Windows, you can press F2, DEL, F10 or whatever key is displayed when your PC first boots up to enter the BIOS setup. In the BIOS setup screen, look for an option such as “Wake from PCI device” or “Allow wake from Ethernet” or “Enable wake-on-LAN.”
IP Address vs. Computer Name
The easiest way to send a WOL magic packet to the right destination is to reference the computer name (“JACK-LAPTOP”). But if that doesn’t work, try typing in the IP address assigned by your router. You can use the method from above for getting your computer’s IP address, or you can check your router’s status page. Just make sure you are getting the IP address for the active wired Ethernet connection, and not a cached wireless LAN connection.
Still having trouble? Let me know in the comments and I’ll try to help you out.
Joined: Jul 6, 2015 Messages: 1 Likes Received: 0
Running build 10130 I'm unable to get wake on LAN working under Windows 10. All settings appear to be identical to what they were in Windows 7 (everywhere I know to look), but while it worked fine under 7 the PC simply will not boot from a magic packet on 10.
I've checked WOL settings in BIOS. Still enabled.
I've checked magic packet settings in NIC properties. They're still enabled.Trouble Noob Whisperer Moderator
TheAmorphous said: ↑
Is there a setting somewhere I'm missing?
Click to expand.
Nope, it sounds like you've hit all the usual suspects.
I suspect it is more an issue with the Preview Build and would suggest that you perhaps consider upgrading to the most current build 10162.
I'm not sure that, that will help with your issue but it is certainly worth trying and I understand that it is Microsoft's intention to release 10162 to the Slow Ring sometime early this week anyway.
There may still be some niggling issues with this latest build but from what I can tell everything about the OS is improving with each subsequent build.