Q: Can't wake Lion over wifi (or ethernet) using iPad and home sharing.

Here is the next thing I tried:

1. Wake up the mac with VNC

2. Access it via TeamViewer

Result:  Black screen

Apparently after a wake the screen is asleep and TeamViewer does not work with screen asleep.  After the screen wakes up I can use my mac with TeamViewer but not with VNC.  And I tried disabling screen sleep in the energy saving section but that was a no-go.

Bummer.  I can't put the mac OR the screen to sleep or I can't access it again.

..OR put a password on screen saver or I can't access it remotely.

Just upgraded to Mountain Lion and this is the first thing I checked. The new OS has borken this again and the prior solution of changing the PLIST is not available.

When I opened the PowerManagement.plist the Prioritize bit was not there.

Any thoughts?

I also just upgraded my system and have the wake over wifi working now.   Here's what I did.

1.  The PowerManagement.plist is in fact there and I changed the 0 to 1.  The easiest way is open up a terminal (in the utilites folder which is in the Applications folder).  I use the editor vi, but pico is probably easier for people who don't know vi, so this example will use pico.  

sudo pico /Library/Preferences/SystemConfiguration/com.apple.PowerManagement.plist

It will ask for your account password

Once in, change the 0 to 1 in the PrioritizeNetworkReachabilityOverSleep key

press ctrl x  to exit the program.  It will ask you if you want to save.  Press y for yes, then enter, and you are done.

2.  I also had to change the com.apple.airport.opproam.plist file, by enabling bonjour services.

sudo pico /Library/Preferences/com.apple.airport.opproam.plist

change the UseBonjour key from false to true

save by pressing ctrl x   then y to save, then return.

After doing this, I went up to the top of the screen and turned wifi off, then on again.  I don't know if that is needed or not.

It works for me.  Good luck.

I went into PowerManagement.plist but the Key is still not present.

I did, however, find the UseBonjour key and changed it to TRUE. This worked! I am able to wake my iMac using a WAKE ON LAN Packet from an app on my iPad .

I also tried going back to PowerManagement to see if the key had appeared after changing UseBonjour, but it did not.

On a side note, the app I use to connect to my iMac is Remoter VNC. It is configured to connect via the Internet through a DYNDNS account as well as over Local WiFi using Bonjour. The Wake on Lan packet only works when coming form the Internet and not from the local setup. Is this normal? I don't remember if it was always like this.

Thank you Namuh! You are awesome

I don't know about Remoter VNC, but I connected by VNC from the local network (using iSSH from the ipad) and it woke up the IMac.

Are you using PropertyListEditor to change the keys?  If so, the PrioritizeNetworkReachabilty... should be under   Custom Profile/AC Power. 

If you bring up the /Library/Preferences folder in Finder (open a window, hold down the option key and select the GO menu to get to the /Library folder), you can double click on a plist and it should bring up the Property List Editor.  Make sure you go to Preferences/SystemConfiguration folder.  If your plist file doesn't have the option, maybe you want to add it.  Here's how the line looks in mine (I didn't add the line, just changed the key value). I've included the lines before and after just for reference.  They are all under AC Power.

<key>Hibernate Mode</key>

<integer>0</integer>

<key>PrioritizeNetworkReachabilityOverSleep</key>

<integer>1</integer>

<key>Sleep On Power Button</key>

<integer>1</integer>

I found the issue. I was comparing the settings on the DynDns protocol and the Bonjour protocol in the Remoter App and noticed that the WoL Mac Address' were different. Once I fixed that I was able to Wake from the Bonjour protocol.

All is good now . I also plugged the PrioritizeNetworkReachability Key into the PLIST just in case. Thanks for your help.

You really know your stuff!

Is there a way to give Forumers a thumbs up or something? I 'liked' your posts but there has to be a way to give more kudos.

After months, I think I found the solution... I made a reset of both my Time Capsule and Airport Express (to start with a network without issue).

Next, I set all my home devices with a static IP, I made that from the devices themselves in the network settings. So I made a static IP for my Time Capsule, Airport Express, Apple TV and iMac. I leaved the iPhone, iPad, etc in DHCP mode.

I restarted everything: router, airports, computers, etc

Now everything seems to work just fine. The iMac is always visible in the MacBook Pro's finder, and I can wake it up from it. I can also wake the iMac from my iPhone while on the go over 3G network.

Before, I had the same issue as you have. When the iMac was asleep, after a few hours, it dissapeared from the network, without any way to wake it up over lan.

I hope this helps

Hi,

same problem for me here on an iMac mid 2010, 10.8 and a TC for internal network.

-j

Been trying to find a solution to waking Mountain Lion from sleep via wifi for a few days now, tried altering the library files with no real success, one minute everything is OK and the Mac will wake and then it disappears off the network again.

Spent 2 hours on the phone to senior support at apple in Ireland with no solution, he is testing it to see if there is a work around but it would appear that this is a bug in Mountain Lion, he did suggest to report the problem to Apple via the feedback page www.apple.com/feedback and hopefully there will be a fix.  He also mentioned that there is an update coming through very shortly 10.8.1 which may address the issue but he was not 100% sure.  If I find anything else I will post it.

Hi,

thanks for sharing the information. I filed a bug report. Let's hope 10.8.1 fixes this issue.

-j

To solve the problem (at least, it worked with me), simply turn off "Find my Mac" in iCloud preferences. Restart and it should be fine.

I don't know why it works, but it works...

Hi, I'm jonathan216; the original poster.  I've changed to a new apple ID which is why I'm not being framed in a blue box.  I downgraded to snow leopard because of this WOL problem but I upgraded to mountain lion a few weeks back, figuring that this must have been fixed by now.  After the upgrade WOL seemed to be working but I was horrified a couple of days later (when I fancied watching a film on my iPad) to find that I couldn't wake my mac using itunes home sharing - aaaargh, not again!

This time, I resolved to get it fixed any way I could, including terminal 'hacks' i don't completely understand if necessary.  To cut a long story short, it's working now.  Here's what worked for me in mountain lion (it involves editing one system file, make sure you do a TM backup first)

1. Open a terminal

2.  Type sudo nano /Library/Preferences/com.apple.boot.plist

3. Enter your system password

4. use the arrow keys to move the cursor and find the KernalFlags key; change it FROM

<key>Kernal Flags</key>

<string></string>

        TO

<key>Kernal Flags</key>

<string>darkwake=o</string>

5. Press [CTRL] + O (for Oscar) to save

6. Press [CTRL] + X to exit the nano editor

7. Reboot.

Wake on LAN should now work.  Things to note

A) your iMac screen will now light up when you access the home share.  It dims again according to your power settings.

B) the iMac (well, mine anyway) takes about ten seconds to acquire an Internet address when it wakes, during which time the iOS home share access attempt might fail.  Just close the iTunes or video app (make the icons wiggle and click red x), then try again.

C) I give credit to the people at iTeleport for this.  See http://www.iteleportmobile.com/support/wake

If you cannot wake mountain lion from sleep using your iPad to use iTunes home sharing, then give this a go.  It finally fixed the problem for me.

Jon.

....Ignore me, it broke again overnight.  WOL is just plain broken on Lion and Mountain Lion.  Given the length of time elapsed since the problem first appeared, and the number of views this thread has had, I can only assume that Apple has no intention of fixing this bug.  Perhaps they can't?