No Wake-on-LAN possible since updating to ML

loïcfernandezcastrillon wrote:

I'm happy to help ;)

Let me know, if you let the Mac mini asleep for an entire night or weekend, if you can access it and if it wakes on lan. Because it was my problem with hibernate set to 0. It worked fine exception after 6 hours of sleep, it disconnected. Now it keeps connected!

I did some more testing.
It is not possible to wake it using Finders "Connect to Server" (or Plex for that cause) but you can wake the machine using SSH (extremely strange). So, if I let the MacMini sleep for a longer period of time (might be 6hours or more) is gets into a cryo-sleep state which makes it harder to wake. So, my enthusiasm is now a bit curbed and I have decided to change energy settings back to "never go to sleep". :-(

So, Apple: You need to do something about this!

Are you using an ethernet cable, cause I know it solve the issue for quite all the desktop Mac, maybe I've solved something. I noticed that my MacBook Pro appeared always connected to my Time Capsule when I was checking AirPort Utility.

I made a repair disc permissions on both my Macs (iMac and MacBook Pro) and now the iMac seems to keep the connection. I tried to turned it off and it appeared still connected.

I guess, maybe it will solve it for the Wi-Fi wake-on-lan.

I'll let you know if tomorrow everything's fine.

What you can do is to program in terminal or with a software a kind of script, that wakes up your computer every 4 or 6 hours. That way it will keep the connexion anytime you want to access it.

I think I'll have to do that if I want it to work without issue.

Yep, we are only talking about ethernet connection where, wireless is compeltely shut off on both my Imac and the MacMini.

I'll check out repair disc permissions and continue the tests.

Regards.

Oh ok... Because in my case, if I plug an ethernet cable from my Time Capsule to my iMac, it solves the problem. I can let the iMac asleep for 2 or 3 days and it wakes without issue.

My problem is with iMac on Wi-Fi without ethernet cable.

Guess what I've found?

https://edovia.tenderapp.com/kb/screens/connection-timeout-while-authenticating

So problem is only half solved! I left my iMac to go to sleep of its own accord last night and was able to connect with the remote app on my iphone this morning. BUT if I sleep the imac from the apple button in the top left hand corner I cannot reconnect with the remote app. Steps I have done so far;

- newtorkoversleep

- hibernate mode 3

- change router to WAP encrytion

So Im wondering now if newtorkoversleep has stopped my imac sleeping on its own, and thats the only reason wake for network access is working when the imac is left to sleep on its own?! Do you know how to reverse the networkoversleep comman so I can test the theory?

I think it's

sudo pmset -a networoversleep 0

We have to wait 10.8.3!

That doesnt seem to have worked, imac is not automatically sleeping, will only sleep properly when done manually with the apple button. How can I check if its reversed the setting?

Go to Computer, Macintosh HD, Library, Preferences, SystemConfiguration, then choose "com.apple.PowerManagement". Type on the space bar to show preview of the file and check the settings.

I think the problem is how desktop Macs handle the connection with AirPort. Cause I don't have problem with my MacBook Pro. But I think we should wait for 10.8.3, which will be realease quite soon I guess. They say that this version will correct some AirPort and AirPlay issues. If this version does't solve the issue, I'll have no choice but use an ethernet cable.

Thanks. I guess we are going to have to wait to 10.8.3......

This afternoon, I let both my Macs (iMac and MacBook Pro) asleep, and while I was working, I checked how the Macs behave during their sleep. I wasn't playing around with iPad or iPhone, so I didn't change anything on iCloud or whatever that could make them awake.

Every 2 hours the Macs wake from sleep (with black screen) and come back to sleep within 10 or 30 sec. The MacBook Pro wake itself every 2 hours during its sleep, the iMac does the same only twice. So after 4 hours of sleep, something tells it to disconnect. (maybe the driver of the wireless card, I don't know).

So the only workaround is to use terminal to plan mutliple wakes during the day (that repeats everyday). That way the iMac will wake every 2 hours or 4 (depending to your settings) and if you don't use it it will come back to sleep within 30 sec. Exaclty like MacBook Pro does with default settings.

So I'll set the iMac to wake at 12am, 4am, 8am, 12pm and so on...

Thats the best turnaround I know in order to use your Mac on Wi-Fi without having to set it to never go to sleep.

Regards,

After trying a few things suggested on this topic I can wake my ethernet connected iMac (mid 2010) by initiating filesharing or screen sharing from my MacBook Pro under most circumstances, but I have noticed a few things:

If I sleep the iMac from the Apple menu, I cannot wake it from my MacBook, ever.

When the iMac is connected via wifi only, sleeping from the Apple menu causes the iMac icon under sharing on the finder sidebar on my MacBook to dissapear immediatedly. When it's connected via ethernet the iMac remains listed under sharing, but I cannot wake it.

If the iMac sleeps after the specified time in Energy Saver settings, I have been able to wake it after making the following changes:

Changed hibernate mode to 3

Changed networkoversleep in com.apple.PowerManagement to 1

What I'm questioning is, if the iMac is ever actually going to sleep after the set time, or if it's only truly sleeping after clicking sleep from the Apple menu.

I hear it become active while "sleeping" every few hours which I believe is supposed to happen. Haven't checked if it does this when sleeping from Apple menu.

It sleeps as soon as the fans aren't functionning. It's normal that sometimes you hear them reactivate along with the hard drive, the Mac keeps the connection to the AirPort and also fetch your email, notes, etc

My MacBook Pro that does not have issue, has networkoversleep to 0, so I don't think it's the solution, and hibernate mode 3... the same.

To be sure it works, let your Mac asleep for 8 hours, and try to wake it up. The first times I was trying some fixes, I thought it was working, cause I was always trying to connect to my Mac with my iPhone or Mac and it worked, because I was accessing it quite often.

But when it sleeps for 8 hours or so, you'll see if hibernate mode 3 and powermanagement 1 work. If it wakes then it works 🙂

I can definately wake it after at least 8 hours, unless I have used the sleep command from the Apple menu as stated.

I've had the same problem for several months with Lion. I've just figured out that the yearly cost of electricity to keep my two iMacs awake so they can talk to each other (without even using them) is $164 (9 cents/kwh). Geez, running my fridge only costs $29/yr.