Hello, I have a problem to make work the 'Wake on network access' feature. I try to host my personal web site on my MacBook. My config is the following. I have a modem/router connected to the internet.
An Airport Extreme is connected to my router. And my MacBook is connected to the AirPort Extreme. I have enabled the port forwarding for the port 80 from the router to the Airport Extreme. On the Airport Extreme, I have enabled to the port forwarding too to my MacBook for the port 80. Everything works fine when the MacBook does not sleep. I can access the built-in web site on the MacBook.
Wake for network access Select this option if you want your computer to automatically wake up when someone accesses its shared resources, such as shared printers or iTunes playlists. This setting applies to wired connections from other computers, such as Ethernet connections.
But when the MB goes to sleep, I cannot access anymore the MB built-in web site. What is weird, It used to work. The MB used to waking up when I accessed the web site from another computer. But since I have installed the last Mac OS X update, It does not wake up any more.
From the mac os x help pages: If you’re sharing your computer’s resources, such as a shared printer or iTunes playlist, you can set your computer to wake from sleep when other users access those resources. To use this feature, you need an Apple wireless device that supports 802.11n, with the latest firmware installed.
To share your computer’s resources when it’s in sleep: Choose Apple menu System Preferences and click Energy Saver. Open Energy Saver preferences Select “Wake for network access.” When this option is selected, your computer wakes at the following times: When a user at another computer accesses your computer’s shared resources.
At regular intervals so that your computer can notify other computers on the network that its resources are available.If you have a portable computer, selecting this option will wake your computer only if it’s plugged in and the display is open. First check to see if your Airport's firmware is up to date. If it is then you are going to need to register the second display with the sleep proxy server. Follow the directions. You can do it via a wireless mouse or keyboard.
You may also be able to do it via a USB keyboard, but I don't know for sure. Follow the directions as they are listed: Plug in and setup all needed devices and adapters (AC plug, external input, external monitor). Then close the lid and after it falls asleep then wake it via the external input (external keyboard and mouse). Now your computer should recognize the external display as a 'Primary'. If you have setup all other systems before hand you can put the laptop back to sleep and try waking via network. Something to keep in mind is that you should not be doing processor intensive tasks while it is in this setup.
Using the laptop while the lid is closed restricts airflow needed to cool the laptop down in the case of an intensive task. In the case of running a website this should not be a big deal, but I would not try doing some video encoding or playing games like this.
From the mac os x help pages: If you’re sharing your computer’s resources, such as a shared printer or iTunes playlist, you can set your computer to wake from sleep when other users access those resources. To use this feature, you need an Apple wireless device that supports 802.11n, with the latest firmware installed. To share your computer’s resources when it’s in sleep: Choose Apple menu System Preferences and click Energy Saver. Open Energy Saver preferences Select “Wake for network access.” When this option is selected, your computer wakes at the following times: When a user at another computer accesses your computer’s shared resources.
At regular intervals so that your computer can notify other computers on the network that its resources are available.If you have a portable computer, selecting this option will wake your computer only if it’s plugged in and the display is open. Hello, Thank you very much 'a Mac user' for your help and your quick answer. Sorry, I have miss some points on my last post. I have not yet tried when I let my lid open, as specified in mac os x help pages.
I would like to make it work with the lid of my MB closed, with an external monitor and with bluetooth keyboard and mouse, like explained in the following apple support doc: I have followed every steps of this doc and it does not work. Do you have an idea: - how I can check if the Bonjour proxy server in my Airport Extreme is working fine? - in which plist file on the MB, I can check that the 'Wake up on network access' is well defined? - which checks I can do, on the MB and on the AirPort Extreme, to verify that everything is well set? Message was edited by: seblux. First check to see if your Airport's firmware is up to date.
If it is then you are going to need to register the second display with the sleep proxy server. Follow the directions. You can do it via a wireless mouse or keyboard. You may also be able to do it via a USB keyboard, but I don't know for sure. Follow the directions as they are listed: Plug in and setup all needed devices and adapters (AC plug, external input, external monitor). Then close the lid and after it falls asleep then wake it via the external input (external keyboard and mouse). Now your computer should recognize the external display as a 'Primary'.
If you have setup all other systems before hand you can put the laptop back to sleep and try waking via network. Something to keep in mind is that you should not be doing processor intensive tasks while it is in this setup. Using the laptop while the lid is closed restricts airflow needed to cool the laptop down in the case of an intensive task. In the case of running a website this should not be a big deal, but I would not try doing some video encoding or playing games like this. Hello, Once again, thank you very much 'A Mac user' for your helps.
I have done exactly what you have indicated in your last post, and still, my MB does not wake up. I wonder if I do not have a problem of registering of the WebServer on Bonjour. I understand that when we unable the Personal Web Sharing on Mac OS X, it should be registered on Bonjour. But when I go on Safari, go to open-book and check all Bonjour registered services, I do not find the MB's WebServer. If the Airport Extreme does not find a registered MB's WebServer with Bonjour, we can understand that he has no reasons to wake up the MB, when it receives a HTTP request from the NET. If it is really the problem, why Mac OS X does not register the MB's built-in WebServer when I enable it in the Sharing pane? And how can I force the registering of the WebServer?
Message was edited by: seblux. Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site.
All postings and use of the content on this site are subject to the.
Macs have long had the ability to put some or all of their hardware to ‘sleep’, a state in which they are not exactly turned off, but which uses much less power. Waking a sleeping Mac is then far faster than starting up after a period shut down, and can impose less wear and tear on its components. Sleep and its resulting low power consumption are most important for laptops (and iOS devices), in optimising battery endurance – the period of use without mains power supply.
As with so many features of Macs and OS X, what started off as a relatively simple system has become much more sophisticated, and inevitably far more complex. It is quite possible now to configure the settings in the Energy Saver pane to permit hard drives, display, and system sleep, but for only one of those to actually happen. It is also sadly uncommon for Macs to crash or freeze when being woken up, and sometimes even when going to sleep. Understanding Power Management in OS X is important when you are puzzled by sleep behaviour, befuddled by the complexities of the Energy Saver pane, or are trying to prevent crashes and freezes which occur on waking or sleeping.
The only general-purpose tool which might help you understand what is going on or wrong is Console, with its log browser. However, your logs are likely to be full of many confusing messages, and using them to solve such problems is not easy. Tools Users are supposed to interact with Power Management through the Energy Saver pane, which has become simpler in design, but more confounding in its operation, over the years. Back in the Classic days of Mac OS 9, there were three separate slider controls to allow you to set the time delay before the system (CPU), display, and drives went to sleep, when not being used. Now, in El Capitan, the appearance of, and controls available in, the Energy Saver pane vary according to model, and in many cases offer just a single slider, to control the time to display sleep. Third-party tools such as MacPilot offer more controls, but may not have any different effect.
This is because the settings from Energy Saver are effectively implemented through the pmset command line tool. If you want to do anything more sophisticated than the gross controls in Energy Saver, you need to use pmset in Terminal. Power Management, and the Power Manager, work through what Apple terms the I/O Kit, part of OS X which is particularly important to those developing drivers and other support software for peripherals and other hardware devices. The Power Manager’s role is to manage the transition between different power states – awake and running, sleep, and off – so as to make the most efficient use of power.
There is another tool which used to be of vital importance to driver developers, IORegistryExplorer, which was supplied as part of Apple’s Xcode development environment. My copy from 2012 still seems to run fine despite its age, but it is no longer a part of Xcode. This allows you to browse the hierarchy of controllers, ports, and devices in what Apple terms the ‘power plane’. Its value for those not developing hardware drivers is probably very small indeed. Pmset pmset gives you full access to the Power Manager powerd, and can be used to inspect its settings, browse its logs, and to control Power Management in much greater detail than offered even by the full controls in MacPilot. It can, like many command line tools, get you into serious trouble requiring SMC and NVRAM resetting, so you must be cautious before making any changes to its settings. Full information is, as ever, available in its man page, viewed in Terminal by typing man pmset A good way to start understanding the Power Manager is to ask for a list of the current settings, using pmset -g Here is a typical response from my iMac, with intercalated comments: System-wide power settings: DestroyFVKeyOnStandby 0 This relates to behaviour when File Vault is configured; if set to 1, then the keys to File Vault will be destroyed when going to standby mode, requiring you to enter the password in order to wake up.
Active Profiles: UPS Power -1 AC Power -1. These refer to custom profiles as stored in the Energy Saver pane settings file. The asterisk marks the currently active profile, that to be used when running on mains power. Currently in use: The following are the current Power Manager settings, which should match those in the active profile.
Standby 0 Sleep On Power Button 0 Standby is disabled, as is forcing sleep using the Power Button. Womp 1 ‘womp’ is wake on ethernet magic packet. In other words, this Mac will wake up for network access (in the Energy Saver pane). Halfdim 1 Display sleep is set to use a half-bright setting.
I am not sure that this works on iMacs at present, as when this display sleeps, it goes fully black. Hibernatefile /private/var/vm/sleepimage When hibernating, a current system image will be saved to this location. Don’t change this. Powernap 0 Whether Power Nap will be used, on those Macs which support it. Gpuswitch 2 This is currently undocumented, but appears to refer to sleep state in the GPU of graphics cards which support this feature. Autorestart 0 This determines whether your Mac restarts automatically when power is restored, after an outage. Networkoversleep 0 This is platform-specific, and determines how shared network services are provided during sleep.
Don’t alter it. Disksleep 0 The time, in minutes, before hard drives are put to sleep, 0 meaning never sleep. Sleep 0 (sleep prevented by com.apple.serverd, xcsbuildd) The time, in minutes, to system sleep. Here, two services – OS X Server and the Xcode build service – are preventing system sleep, even though the Energy Saver pane may allow it. Autopoweroffdelay 0 Supported by certain models only, after this delay in seconds (not minutes), the system will hibernate by writing an image to the drive and powering down memory. Hibernatemode 0 On desktops, set to 0, and will not hibernate, but only sleep. On portables, normally set to 3, which stores a hibernation image but does not power down memory.
When set to 25, using pmset, will go into full hibernation, with memory powered down. Autopoweroff 0 After the period set in autopoweroffdelay, certain models will hibernate, when set. Ttyskeepawake 1 When set to 1, this prevents sleep when a remote login session remains active. Displaysleep 60 The delay, in minutes, before putting the display to sleep.
Standbydelay 10800 The delay, in seconds, before hibernating, when supported. So although my custom profile, as set in the Energy Saver pane, allows system sleep but not disk sleep, because OS X Server and Xcode’s build service are running, system sleep is prevented.
If you have been experiencing problems with the battery in a portable, then the command pmset -g pslog displays the power source log. This can be used to detect sudden discontinuities in battery power remaining which often occur with ageing batteries, for instance. Pmset -g log displays the full Power Management log, which can be quite long and hard to decipher. However, if you suspect there are problems with waking, sleeping, or other functions, this can be a valuable tool. You will then see timed entries like 2016-06-06 01:19:28 +0100 Notification Display is turned off when the display goes to sleep, and 2016-06-06 01:19:28 +0100 Assertions PID 80(com.apple.serverd) Summary PreventUserIdleSystemSleep 'com.apple.service.xcode' 183:50:21 id:0x0x10000013b System: PrevIdle when OS X Server and Xcode are preventing sleep. Conclusion With awake, Power Nap, asleep, semi-hibernating, and full hibernation, Power Management has become very complex – all the more so when you bear in mind that different models support quite different features. Getting to the bottom of problems can be tricky, but pmset is a valuable tool to help.
Unfortunately the settings shown in the Energy Saver pane, and in its settings file, often do not reflect the Power Management settings in force. That is bad interface design, and requires re-engineering to ensure that the user can understand what is going on, without having to resort to pmset.