Previous 1 3 4 5 6 7 Next 293 Replies Latest reply: Apr 28, 2015 2:25 PM by Romiks Go to original post Branched to a new discussion.
  • joda1956 Level 1 Level 1 (10 points)

    Hi D.Rue,

    this work better than other workarounds, but there are still problems remaining with already connected shares and with network traffic during the Mach goes to sleep. Examples:

    a) a share is connected via alias, the server went to sleep. Using the share makes the mac freezing.

    b) a large download is in progress, the Mac ignores the traffic and goes to sleep.

     

    that didn't happen with 10.7.

     

    A proper final solution should keep all Macs alive, as long there is any acess or traffic regarding the Macs.

  • Inked apple Level 1 Level 1 (0 points)

    Still not working for me, even with the altered darkwake setting. This bug is not limited to ML though as some people are stating, it was present for a lot of people under Lion too unfortunately.

  • joda1956 Level 1 Level 1 (10 points)

    Hi Inked apple,

     

    I don't agree, I was on Lion with my two Macs without any problems concerning WOL or sleepmode during web acesses. The reason on my opinion will be found as ML bug. Lion users may have similar problems but the for sure have similar reasons for them.

    btw: the only difference I can see is, that I never made a clean install of Lion. I always upgrades from Snow Leopard. Perhaps some of the system files and params where kept in the right way.

  • Inked apple Level 1 Level 1 (0 points)

    I have had this problem for the past year with Lion and now have the same in Mountain Lion, whatever the reason for it not working is likely to be the same. Under snow leopard WOL worked perfectly, none of the "fixes" worked for me under Lion, none are working under ML.

     

    I have resorted to just setting my iMac and Mac Mini to never sleep.

  • PersTechLife Level 1 Level 1 (0 points)

    I can't comment on WOL problems with pre-Mountain Lion OSX versions as for the first time ever with ML my Mac Mini is now going to sleep.

     

    I however notice, that some apps are working with WOL, while others are not.

     

    Currently wakeonlan.py (and others) from another OSX machine don't work, while waking up using my AVM Fritzbox and Mocha WOL on iOS does the job.

     

    I'm currently struggling in understanding that.

     

    Possible reasons:

    • OSX to OSX wakeup seems to be the problem while WOL from other devices works fine, so OSX has problems in sending out WOL requests
    • There is some special "code" in the WOL packet required, which has changed from Lion to ML and some apps get it right, while others don't

    PTL

  • David Munch Level 1 Level 1 (5 points)

    Indeed. I see that Plex can activate WOL just fine, while anything related to the system or apps that came with ML, doesn't work.

  • knidsrok Level 1 Level 1 (0 points)

    Anyone on the 10.8.2 update -- any improvement?

  • joda1956 Level 1 Level 1 (10 points)

    No changes on that topic with ML 10.8.2

  • bjw Level 4 Level 4 (1,325 points)

    I am seeing improvement with 10.8.2

     

    I did a clean install of 10.8.1 and saw no difference.  But this update seems to have fixed it for me.

  • David Rosen Level 1 Level 1 (35 points)

    Same problem here. Back To My Mac will not connect to a remote mac in Mountain Lion unless that Mac is already awake. I have the "Wake for network access" button checked. Once I have somebody touch a keyboard to wake up the remote mac I can share screens (vnc), and share files (afp), but this is obviously a problem if nobody is around to wake up the remote machine. I have screen sharing and file sharing checked, and I'm allowing access to the hard drive to myself as a user. This was not a problem in Mobile Me, but seems to be a problem in iCloud.

     

    Additionally, if I manually type in the the WAN IP address for the remote mac, it will connect to it's associated Time Capsule, but will not connect to the Mac itself. All Macs are 10.8.2.

     

    Any ideas what's going on?


  • bratman91 Level 2 Level 2 (180 points)

    Since upgrading to Mountain Lion (10.8.2) from Lion (10.7) a couple of days ago, neither Eyeconnect nor Filebrowser  on iPhone/iPad can connect to my iMac when it is in sleep. I note that this does not happen until the iMac has been in sleep for quite a long time (maybe an hour or so!- it's difficult to tell but long after the screen goes blank). Energy saving options are the default ones, including putting hard disc(s) to sleep when possible and wake for network access. Is it possible that, with Mountain Lion the hard disc is being put into sleep and that this prevents the wake on network access from working?  If so, maybe the hard drive never went into sleep mode in Lion because programs like, for example, Eyetv were always using some CPU, but Mountain Lion has a more aggressive mode of energy saving. I will uncheck the option for putting the hard disc(s) to sleep and see if this works.

  • Panthr Level 1 Level 1 (0 points)

    Also BTMM wake-up problems by trying to connect my MB-Air via iPhone tethering to the iMac at home.

     

    If iMac is awake, Back to my Mac  works fine.

    But if it is in sleeping, it won't show up in the finder sidebar under "shared devices".

     

    Both Mac are updated to Mountain Lion.

    The energy saving option "wake on network access" is on.

     

    Don't know if this a Mountain Lion problem, because I didn't use BTMM with Lion.

     

    Could it be, that  "wake on lan" is not working with third party routers?

    Does maybe require Time capsule oder Airport? 

  • bratman91 Level 2 Level 2 (180 points)

    With Lion, my iMac Time Machine made a backup about once an hour even when the iMac was asleep (or I assumed it to be asleep). With Mountain Lion 10.8.2, Time Machine makes backup only when the iMac is active and not asleep so, either this is as it should be, or even the iMac's internal programs are unable to wake it from sleep. Time machine writes to an external hard drive connected to the iMac by USB, so no router is involved.

     

    However, Eyetv does wake up the iMac in order to make a scheduled recording but, rather disconcertingly, the screen jumps back into life while it is recording. It never did this in Lion. The Eyetv and Filebrowser apps on my iPhone and iPad are still unable to wake up the iMac while it is sleeping and this is the case whether or not my network is wifi or ethernet.

  • bratman91 Level 2 Level 2 (180 points)

    Further to my post above, I have been trying out various Apple and third-party apps to see what effect, if any, they have on the "wake for network access" issue. I have an iMac 10.8.2 and all the Energy Saving options are set to the default ones. Filebrowser and the Eyetv app for iPhone are unable to wake the iMac after it has gone to sleep. The Apple remote app for iPhone will at least partially waken the iMac from sleep and operate iTunes if iTunes is open. This allows Filebrowser to work but not the Eyetv app. Hipporemote Lite will wake up the iMac fully, albeit not instantly, and this then seems to allow all apps to access the iMac.

     

    Hipporemote Lite is free so, for those people whose apps or devices will not wake up a sleeping Mac, it is worth trying as a fix pending Apple providing a better one. If you want to access a sleeping Mac, use Hipporemote to wake it up and then use it normally. This probably won't help everyone but it may help some.

  • joda1956 Level 1 Level 1 (10 points)

    Thanks bratman91, You're right concerning the wake on lan topic.

    You can use any wake on lan app available in the appstore and it works. To wake my mini from the imac I use the WOL tool by Dirk Lembens, which is available for free.

    The main topic for me is to wake up a mac by selecting a share and to keep the mac awake while network traffic is in progress.

Previous 1 3 4 5 6 7 Next