Richard Setterberg

Q: "Wake for network access" doesn't seem to work

I have several Yosemite Macs.  My main Mac Energy Saver setting is set to wake for network access.  That's the only box checked (Display set to turn off after an hour). 

 

I can't seem to get access to this computer on my network (get a "connection failed") after the display turns off.

 

Any other settings I need to set to cure this?

iMac, OS X Yosemite (10.10), Retina 5K

Posted on Apr 11, 2015 5:57 AM

Close

Q: "Wake for network access" doesn't seem to work

  • All replies
  • Helpful answers

Previous Page 2
  • by SuperSizeIt,

    SuperSizeIt SuperSizeIt May 8, 2015 10:26 AM in response to BobHarris
    Level 3 (579 points)
    May 8, 2015 10:26 AM in response to BobHarris

    Yes I have provided feedback at the Apple Product Feedback page. This probably explains this glaring issues with Yosemite Wake On Demand Fail.

     

    http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

  • by BobHarris,

    BobHarris BobHarris May 8, 2015 1:03 PM in response to SuperSizeIt
    Level 6 (19,628 points)
    Mac OS X
    May 8, 2015 1:03 PM in response to SuperSizeIt

    Yes I have provided feedback at the Apple Product Feedback page

    Good, but the Feedback page is not as "In Your Face" as a bug report, but any information send back to Apple is better than nothing.

  • by WZZZ,

    WZZZ WZZZ Jul 8, 2015 8:31 AM in response to BobHarris
    Level 6 (13,112 points)
    Mac OS X
    Jul 8, 2015 8:31 AM in response to BobHarris

    Bob, maybe you can help with this one. I only recently started using screen and file sharing, and what I discovered was with Wake on Network allowed, the Mini on this network was getting woken up every two hours with "Wake reason: RTC (Alarm)".  Only for 20 seconds or so, but that adds up to over 4,000 unnecessary drive spinups and spindowns over the course of a year--not too great to do that to the drive. At Insanely Mac there's a huge thread about this issue, which, at least for them was solved by adding


    <string>-DisableSleepProxyClient</string> to the mdnsresponder.plist at ProgramArguments.

     

    On my 10.8, where I did the edit, it shows this way:

     

    <key>ProgramArguments</key>
    <array>
    <string>/usr/sbin/mDNSResponder</string>
    <string>-DisableSleepProxyClient</string>
    <string>-launchd</string>
    </array>

     

    Ok, that worked just fine, no more waking up every two hours, but I just discovered that Wake for Network got disabled along with these RTC wakeups, so can't screen or file share to a sleeping machine, only to one that is already awake. Have tried the Go>Connect to Server, WOL.app, WOL in Tomato at the router, and WakeMe.app. All no dice.

     

    Curiously, at Insanely Mac, no one has reported this problem. Is it as simple as Wake for Network won't work if Sleep Proxy is disabled? Or could there be some kind of workaround, even with it disabled. As already mentioned, magic packets from various programs are not doling the job, so that's not a possible workaround.

  • by BobHarris,

    BobHarris BobHarris Jul 8, 2015 4:45 PM in response to WZZZ
    Level 6 (19,628 points)
    Mac OS X
    Jul 8, 2015 4:45 PM in response to WZZZ

    Re: and <string>-DisableSleepProxyClient</string> to the mdnsresponder.plist at ProgramArguments.

     

    Look at <http://hints.macworld.com/article.php?story=20100401103451497>

    Not sure if this will help, but it does appear to explain the wake up every 2 hours reason.

  • by WZZZ,

    WZZZ WZZZ Jul 9, 2015 5:46 AM in response to BobHarris
    Level 6 (13,112 points)
    Mac OS X
    Jul 9, 2015 5:46 AM in response to BobHarris

    I have installed sleepwatcher, but know nothing about writing a script that will prevent these damned RTC Wakeups (which I do understand) and still allow Wake for network, which would appear to be the solution. I've seen several suggestions for that in a few places, but I'm more confused than ever.

Previous Page 2