Previous 1 2 3 Next 32 Replies Latest reply: Aug 1, 2014 10:13 PM by smashingly Go to original post
  • JDMcCADD Level 1 (0 points)

    I like your solution of modifying the file to disable darkwake.  I decided to pursue an alternate solution though, since the Macbook I'm trying to wake belongs to a customer and I didn't want to modify it's sleep behavior.


    I was trying to wake a Macbook Pro to have a Retrospect Backup Client on that Macbook respond to the Retrospect Pro software running on a WinXP PC.  I noticed that even though the Macbook would respond to ping from the XP machine, Retrospect Pro reported no response from the Retrospect Client on the Macbook.  The post from Quelqu Un explains the situation well.  I was not aware of the darkwake mode.


    I've been using a batch file to wake the other PC clients on the network using wolcmd (from - great source of info on WOL).  The batch file tests for ping response from the desired PC and if there's no response sends a WOL magic packet to that PC.  I noticed that after modifying the batch file to wake the macbook pro that the ping response was good so the WOL magic packet was never sent.  Even after defeating the test for ping response the magic packet was not waking the Macbook Pro to a state that allowed response from the Retrospect Client.


    Since the WOL magic packet needs to be followed by a request for a serivce running on the Mac (thanks Quelqu Un!), I tried using telnet to send a request to the IP address of the Macbook Pro on port 5900 (VNC), since I had remote mangement & vnc enabled.  This seems to work, since the batch file now wakes the Macbook sufficiently for the Retrospect Client to respond and the backup proceeds.


    On a windows PC the batch file is as follows.  I'm sure it could be implemented from OS X as well, but I'm not as familiar with scripting in OS X.  Anybody want to provide the OS X (unix) equivalent?


    wolcmd 406c8f1b5fa4 7

    start telnet -a 5900

    sleep 45

    \SysinternalsSuite\pslist telnet

    if %errorlevel%==1 goto NO_TELNET

    \SysinternalsSuite\pskill telnet



    A) wolcmd parameters are: MAC addr, IP addr., SNM, port (see for more complete explanation)

    B) start telnet opens telnet in a separate window so the batch file can continue

    C) sleep.exe (available in the Windows Server 2003 Resource Kit) - pauses 45 seconds

    D) pslist (from tests for active telnet process

    E) pskill (also from kills the telnet process, which hangs forever if not killed


    That's the core of my batch file.  Be glad to submit the rest if anybody's interested.  Gotta run...

  • Charles Houghton-Webb Level 1 (25 points)

    @ Quelqu Un

    I came across this thread by chance looking for an answer to a similar problem and couldn't help but see your very detailed answer and your rather condescending reply to a brody. It reminds me of the old joke about how many computer geeks it takes to screw in a lightbulb

    A brody's suggestion of a Remote Desktop program, which is probably more accessible to most than foraging around in the system using the terminal, seems perfectly valid to me. On top of that, your solution supposes that you have prepared the machine that your going to want to wake up, in advance, which may not be practical or feasible, according to circumstances.

    Apple Remote Desktop is perfectly capable of waking sleeping Macs under Lion (10.7), without any particular modifications to the system - I know this for a fact, as I do it all the time ! I'm certainly not against doing system mods if there's no way round it, but it's definitely not the case here

  • Fault to upgrade iOS 4.3.1 Level 1 (0 points)

    may i get links with screenshuts or exact "step by step" root?? Im not familiar with terminal ... etc at all!





  • ttringle Level 1 (0 points)

    Why would you answer a question and start off with, I don't know what {subject} is but blah blah blah??


    People who could help him are the ones that already know what WOL stands for. Rather that ask him to teach you the bare minimum about the subject he needs help with, how about you NOT answer subjects on which you know nothing about.

  • Gerry Brown Level 3 (795 points)

    May I suggest WakeyWakey.

    I may receive some form of compensation, financial or otherwise, from my recommendation or link


    <Edited by Host>

  • Charles Houghton-Webb Level 1 (25 points)

    I think you probably may not !!

    Using apple discussions as a spam site for selling your own commercial software is more than a bit cheeky, isn't it ?

    On top of that, your software is a bit of a sledgehammer to crack a nut. Simple, free solutions exist for WOL, with the addition of Quelqu Un's informed suggestions for Lion, if need be. Having to install and leave software running on all the machines that you want to wake up… heavy to say the least

    It's not even rocket science to program your own. I set up a PHP page to send WOL packets to any of the computers on my school network. There's loads of info about this on the Net.

  • Gerry Brown Level 3 (795 points)

    Well, I am sorry you feel that way.  Not everyone wants to learn PHP or setup their own web page.  For the cost of a latte, WakeyWakey solves the problem.  PLUS, one doesn't need to know about IP addresses and it works over WiFi, if the router is an Airport type device.  As for using a sledge hammer, Apple Remote Desktop is a sherman tank to solve this issue and costs more.

  • Charles Houghton-Webb Level 1 (25 points)

    Hey Gerry… I'm not looking for a fight


    I don't feel any way in particular, apart from the fact that I don't think Apple forums are the place to be flogging your software. If everyone's OK with that, then I'm wrong… say no more


    I do not particularly advocate Remote Desktop either… I just pointed out to Quelqu Un that it was not such a ridiculous suggestion on Brody's part, as it actually works, without hacking your system, for those who want to go that way. Many places with a network full of Macs also have Remote Desktop… schools for instance… if you have it… it does WOL.


    A quick look on MacUpdate (or suchlike…), will turn up a few completely free WOL programs that will do the job directly or, according to the system you're using, with Quelqu Un's hack… zero cost… minimum… overload… minimum effort…


    After that, people do as they like. It's a free world (supposedly, but we won't go into that now )




  • Mathias Luther Level 1 (65 points)

    Some of the solutions suggested in this thread are a little far-fetched. All you have to do is to enable Remote management instead of Screen sharing (they mutually exclude each other) on the Sharings panel (remember to add a user, instead of All) of your target computer and then figure out the IP, the Mac Address, the subnet and the port of the interface you want to use for waking it up. Use a WOL utility (I used Depicus Wake on Lan, free from the App store) to send the packet from your client.

    At least when using a Macbook Air with a suitable Wifi card you can even wake your computer up wirelessly if you are on the same local network.

    The only hard part is figuring out the correct addresses and ports, and remember they are different for Ethernet and Wifi.

    And you don't need to buy any extra software to access a Mac from another using Remote desktop, the client is built-in at least since 10.5.

  • nbar Level 5 (6,980 points)
  • Mathias Luther Level 1 (65 points)

    Embarrassing but I think I have to correct myself – in the right direction, though.


    You don't have to figure out the addresses and ports. If you can see the machine in your Finder, and it has Remote management enabled, and you know the user and password - you will wake your machine up, even wirelessly, even a macbook from 2011.

    If things seem more complicated than this, I suspect you should examine how the router(s) are set up.

  • pjhunt Level 1 (0 points)

    Remote management in no way replaces or even works the same as WoL. 


    Remote Management will not turn on a computer that is powered off.  WoL will.


    WoL will not allow you to remotely manage that computer.  Remote Access will.


    They each do completely diferent things.


    But don't feel bad, you're not the only one responding who has no idea what the OP is asking.


    As far as I can tell WoL is dead on newer versions of OSx.  Maybe someone knows a way around it but I've not found one yet.


    Odly enough, it does work in FreeBSD... 



  • Mathias Luther Level 1 (65 points)

    Of course I know what the OP meant, it's stated clearly enough. And I know that Remote management uses some kind of WOL to wake the target machine up (in order for it to be managed). Once your target is awake you can use either screen sharing or file sharing for your work, depending on what you want and what you have enabled on your target.


    Just woke my MBair up remotely to write these lines.

  • Charles Houghton-Webb Level 1 (25 points)

    It looks like you're not too clear on what's what yourself, so before reproaching people of having "no idea what the OP is asking", perhaps you should check out your own knowledge

    No one ever said that Remote management would replace WOL, only that Apples' Remote management does WOL.

    As for WOL being able to turn computers on, that are powered off… you do know that you're on a Mac forum here, right AFAIK, apart from the now obsolete xServe, Macs do not have the necessary hardware to cold start from a WOL packet. WOL is however NOT dead on any Macs.


    The OP does not clearly state whether he's trying to cold start his machine, but he talks of WOL… WAKE on Lan not BOL… BOOT on lan… and before you say anything… I know… I just invented the last one

  • zerkbern Level 1 (0 points)

    Thank you for your KNOWLEDGEABLE response.  I really didn't need a lecture about "lighning strikes" and Data Recovery when my question was about WOL.


    I'm glad I was patient enough to scroll down and see your response.