Problem with iCal events after waking from sleep mode

I have a daily iCal reminder that starts playing a playlist in iTunes at 6:00 am. However, if I leave the computer in sleep mode at night, and then manually wake the computer (BEFORE 6:00 am), the iCal event won't play on time...it's delayed 20-30 minutes. Any ideas why?

Have you tried it with a different mouse? I'm no expert, but you might want to find out, if the problem is mouse-specific.

Similar Messages

  • Problems with wifi network after waking from sleep

    I have recently started using a new wifi network and have had some problems connecting to it. When i first tried to connect it gave a message that said "An error occured while trying to join". After some trial and error, I found that I could connect by going to network preferences, clicking "Assist me...", then "Diagnositcs...", clicking the AirPort dot then continue, then clicking on the network name and continue, then it prompts for a password, but there isnt one so i just pushed continue and all of a sudden it connected. I figured it was functional now, but after waking it from sleep mode, the error message popped back up. The only way I know to connect is through that annoying diagnostics path... What is the Problem, is it the computer or the router or the settings on the admin computer? (by the way, I don't know what kind of router it is, but its definantly not an apple airport)

    Sorry to drag this back up, but I may have found the source of the problem, I just need the solution. When I first created settings for the network, it automatically "detected" that the security was WPA2 Enterprise, and knowing there was no password, I just pushed join and it saved it that way. When I go through diagnositics as described before, it lists WEP as the encryption. I had a friend with almost the same problem, but in tiger. They were able to fix it by changing the encryption on the login screen that comes up when you click on the network name from the menu bar. But that screen no longer exists in Leopard, it only goes by previous settings. How do I change the encryption in settings, I'm sure it will fix the problem...

  • How do I investigate and solve Pages, Notes, Mail intermittent 'offline' and failure to synchronise problems with Mountain Lion after waking from Sleep

    When I wake up my iMac after sleep, i get a variety of intermittent - but mostly FREQUENT and FRUSTRATING problems including:
    Notes app is offline - as stated by a message in the window bar. If I close Notes and reopen, the app appears to be online. However, Notes does NOT update with items I know are on my iPad or in the web iCloud. Furthermore, if I create a new note on my iMac, the new Note does not upload to iCloud. This is IRRITATING!
    Pages and Numbers - similar situation. I can edit a Pages or Numbers document on my iMac (stored on the iCloud). But then the Pages doc doesn't ALWAYS get uploaded to the iCloud. Then I end up with conflicted versions of the file in the cloud, my iPad, and the two iMacs I use. Then I get CONFUSED and FRUSTRATED. For example, consider these steps:
    Open Pages on my iMac, edit an iCloud file, then save and close file
    Pages/File/Open/iCloud - I note in the iCloud file list the edited file has a little 'cloud' icon against its name. From experience this warns me of TROUBLE - namely that the file has NOT yet been uploaded to the iCloud. However, I just checked the new Beta iCloud on the web, and to my surprise, the file edited on my iMac is apparently in the icloud. But now, I edit the iCloud version, and the changes DO NOT appear on my iMac pages version. OK I realise its in Beta version...
    So now, I open my iPad, open Pages. I note the iCloud version of my edited document updates to my iPad, as indicated by a blue download line. 'It just works' as Steve Jobs claimed at Apple Developers Conference a couple of years back. Again, the edited version form my iPad is now 'up in the cloud' correctly....
    Oh - and now mysteriously the Pages version on my Imac has become synchronised with my iPad/iCloud version! Luck ... but that's about all I can say. It doesn't always happen. I'm LUCKY today.
    Meanwhile, the Note I created on my iMac (Item 1 above) has still not yet appeared on my iPad or iCloud... even though I HOPE it would be given that Pages on my iMac, iPad and iCloud are chatting nicely now! The Note says it's in my iCloud - but  NOT. Similarly, notes updated or added on my iPad, which appear in iCloud, are NOT on my iMac.
    Mail - last but NOT LEAST! and MOST INFURIATING!!! My Gmail, Vodafone NZ and Orcon accounts (in Mail) are all active and receiving after the night's sleep. However, my iCloud mail account has the dreaded offline.
    The message on Mail is "There may be a problem with the mail server or network. Verify the settings for account “ICloud - [email protected]” or try again. The server returned the error: The server “p03-imap.mail.me.com” cannot be contacted on port 993." Despite the message, mail was received this morning at 8:59 am ... some time before I woke-up my computer (a late start this morning).
    If I sent an email FROM my .me iCloud account TO my Vodafone account, the message whooshes away, it's in my SENT box. But it doesn't get delivered to my Vodafone account on my iMac Mail, or anywhere else, Despite the message being listed in my 'Sent' mailbox!!!
    In contrast, a message sent from my Gmail account to my Vodafone account (in Mail) gets sent and received almost instantly on  my iMac and iPad.
    All of the above mishaps are extremely frustrating, as I rush off from working on my iMac at home, get to my iMac at work and find documents I have been updating on my home iMac not available correctly on my work iMac ... or even my iPad. I expect these things from Apple to 'just work'. Furthermore, emails I THINK I have sent (as indicated by them appearing in the Sent folder on my home iMac) ... have not actually been despatched.
    Frankly, I can no longer rely or recommend the Apple iCloud stuff, so I am converting more and more to relying on DropBox and Google.
    These problems only became apparent since I updated to one of the Mountain Lion versions... I can't say when.
    Oh - if I shutdown and restart the computer my Mail works OK. Guess what, I don't want to do that each time I want to use Mail!
    Technicals:
    My iMac is connected by Ethernet cable to my Apple TimeCapsule. The TimeCapsule is connected by Ethernet cable to my Orcon Genius Modem.
    Obviously, my internet connection is A-OK, as I am able to use Firefox to make this posting!
    Mountain Lion 10.8.4
    iMac 27 inch, mid 2010, Intel Core i5 16 Gb

    I've returned to my sleeping iMac after a few days away. Tis time, ALL MAIL accoiunts are offline. I will follow you next set of instructions. In the meantime, here is the DETAIL from MAIL CONNECTION DOCTOR:
    LevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    19.10827 STATUS [Gmail]/Trash (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.179 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    20.10827 STATUS INBOX (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.202 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    21.10827 STATUS "Sent Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.226 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    22.10827 STATUS "Deleted Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
    READ Sep 30 08:35:11.254 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/All Mail" (HIGHESTMODSEQ 561701 UIDNEXT 1666 UNSEEN 105)
    13.10827 OK Success
    READ Sep 30 08:35:11.494 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/Drafts" (HIGHESTMODSEQ 561701 UIDNEXT 1 UNSEEN 0)
    14.10827 OK Success
    READ Sep 30 08:35:11.514 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/Important" (HIGHESTMODSEQ 561701 UIDNEXT 731 UNSEEN 8)
    15.10827 OK Success
    * STATUS "[Gmail]/Sent Mail" (HIGHESTMODSEQ 561701 UIDNEXT 532 UNSEEN 2)
    16.10827 OK Success
    * STATUS "[Gmail]/Spam" (HIGHESTMODSEQ 561701 UIDNEXT 16 UNSEEN 2)
    17.10827 OK Success
    * STATUS "[Gmail]/Starred" (HIGHESTMODSEQ 561701 UIDNEXT 19 UNSEEN 0)
    18.10827 OK Success
    * STATUS "[Gmail]/Trash" (HIGHESTMODSEQ 561701 UIDNEXT 546 UNSEEN 0)
    19.10827 OK Success
    * STATUS "INBOX" (HIGHESTMODSEQ 561701 UIDNEXT 603 UNSEEN 64)
    20.10827 OK Success
    * STATUS "Sent Messages" (HIGHESTMODSEQ 561701 UIDNEXT 138 UNSEEN 0)
    21.10827 OK Success
    * STATUS "Deleted Messages" (HIGHESTMODSEQ 561701 UIDNEXT 89 UNSEEN 0)
    22.10827 OK Success
    WROTE Sep 30 08:35:11.537 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
    23.10827 IDLE
    READ Sep 30 08:35:11.927 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
    + idling
    READ Sep 30 08:35:15.472 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
    220 st11p00mm-asmtp002.mac.com -- Server ESMTP (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013))
    WROTE Sep 30 08:35:24.784 [kCFStreamSocketSecurityLevelNone]  -- host:mail.orcon.net.nz -- port:25 -- socket:0x7fc3161a1b00 -- thread:0x7fc315d05050
    EHLO [10.1.1.4]
    WROTE Sep 30 08:35:24.822 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x7fc316e72a70 -- thread:0x7fc31850bec0
    EHLO [10.1.1.4]
    WROTE Sep 30 08:35:34.080 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
    EHLO [10.1.1.4]
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316fc30e0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc31a6fa8a0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316197890
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316e813d0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0350
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3185c0410
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315ded870
    INITIATING CONNECTION Sep 30 08:35:47.193  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e729b0
    INITIATING CONNECTION Sep 30 08:35:47.198  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
    INITIATING CONNECTION Sep 30 08:35:47.377  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
    INITIATING CONNECTION Sep 30 08:36:40.352  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.352  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31617f290
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316e729b0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31615a390
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e3bbc0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e0cfa0
    INITIATING CONNECTION Sep 30 08:36:40.368  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31829f120
    INITIATING CONNECTION Sep 30 08:36:40.403  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.412  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.565  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.595  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.633  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.687  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.708  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.729  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3183339e0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3186f07e0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315a9b630
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172f6e70
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31616b9d0
    INITIATING CONNECTION Sep 30 08:37:33.323  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.336  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e03950
    INITIATING CONNECTION Sep 30 08:37:33.462  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.463  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.509  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.528  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.557  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.598  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.624  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.646  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:38:26.315  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31686fa30
    INITIATING CONNECTION Sep 30 08:38:26.316  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316fcc7d0
    INITIATING CONNECTION Sep 30 08:38:26.316  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3170d8a90
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc318521490
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e81b30
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316fdf410
    INITIATING CONNECTION Sep 30 08:38:26.318  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d3a890
    INITIATING CONNECTION Sep 30 08:38:26.320  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
    INITIATING CONNECTION Sep 30 08:38:26.350  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316728a90
    INITIATING CONNECTION Sep 30 08:38:26.350  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.495  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
    INITIATING CONNECTION Sep 30 08:38:26.538  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.591  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.619  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.642  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.666  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:39:19.257  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31662a980
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3182e6150
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31605c330
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3184b79c0
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31658f5b0
    INITIATING CONNECTION Sep 30 08:39:19.259  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316e03950
    INITIATING CONNECTION Sep 30 08:39:19.259  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3160d8c80
    INITIATING CONNECTION Sep 30 08:39:19.265  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
    INITIATING CONNECTION Sep 30 08:39:19.287  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316073530
    INITIATING CONNECTION Sep 30 08:39:19.287  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.420  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
    INITIATING CONNECTION Sep 30 08:39:19.457  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.505  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.531  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.552  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.573  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:40:11.346  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3161c6e50
    INITIATING CONNECTION Sep 30 08:40:11.347  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316becee0
    INITIATING CONNECTION Sep 30 08:40:11.348  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31679c620
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3144ad030
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc3158e5b50
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316728a90
    INITIATING CONNECTION Sep 30 08:40:11.363  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315c576d0
    INITIATING CONNECTION Sep 30 08:40:11.518  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.518  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
    INITIATING CONNECTION Sep 30 08:40:11.548  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.568  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
    INITIATING CONNECTION Sep 30 08:40:11.597  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.638  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.660  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.683  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:41:06.173  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318297540
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc314144080
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d435e0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3167306a0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31680f3e0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3170d8a90
    INITIATING CONNECTION Sep 30 08:41:06.197  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31671e630
    INITIATING CONNECTION Sep 30 08:41:06.223  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.223  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
    INITIATING CONNECTION Sep 30 08:41:06.376  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.396  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
    INITIATING CONNECTION Sep 30 08:41:06.431  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.475  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.503  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.527  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:59.159  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.160  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e16c90
    INITIATING CONNECTION Sep 30 08:41:59.160  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3161e71f0
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3170d94c0
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3174bc990
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31820b7d0
    INITIATING CONNECTION Sep 30 08:41:59.174  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162884e0
    INITIATING CONNECTION Sep 30 08:41:59.189  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:41:59.189  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.344  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:41:59.363  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.409  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.430  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.450  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.471  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:42:51.209  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31a613830
    INITIATING CONNECTION Sep 30 08:42:51.210  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3168ae8d0
    INITIATING CONNECTION Sep 30 08:42:51.210  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3161d6110
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315de6190
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316482400
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31829f120
    INITIATING CONNECTION Sep 30 08:42:51.224  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3159e76e0
    INITIATING CONNECTION Sep 30 08:42:51.372  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:42:51.372  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.402  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:42:51.421  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.466  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.492  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.514  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.536  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc315d40d90
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc315ad1930
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc316c27e30
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315adf230
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d49010
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159a1ea0
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc318691eb0
    INITIATING CONNECTION Sep 30 09:43:23.250  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 09:43:23.311  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e1b2d0
    INITIATING CONNECTION Sep 30 09:43:23.311  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.427  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 09:43:23.471  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.524  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.547  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.574  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.598  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 10:06:17.592  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
    INITIATING CONNECTION Sep 30 10:06:17.596  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3174e7bd0
    INITIATING CONNECTION Sep 30 10:06:17.598  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315e08640
    INITIATING CONNECTION Sep 30 10:06:18.674  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.483  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318462600
    INITIATING CONNECTION Sep 30 10:06:19.539  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162d4270
    INITIATING CONNECTION Sep 30 10:06:19.564  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
    INITIATING CONNECTION Sep 30 10:06:19.582  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.653  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.674  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.725  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.747  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:07:19.496  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
    INITIATING CONNECTION Sep 30 10:07:19.523  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3144bad30
    INITIATING CONNECTION Sep 30 10:07:19.531  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.534  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172b7640
    INITIATING CONNECTION Sep 30 10:07:19.550  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315cbb960
    INITIATING CONNECTION Sep 30 10:07:19.626  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315842910
    INITIATING CONNECTION Sep 30 10:07:19.665  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
    INITIATING CONNECTION Sep 30 10:07:19.715  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.805  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.854  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.892  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.915  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:08:19.527  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
    INITIATING CONNECTION Sep 30 10:08:19.553  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3162e8510
    INITIATING CONNECTION Sep 30 10:08:19.555  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315ac9950
    INITIATING CONNECTION Sep 30 10:08:19.564  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.582  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3146b1020
    INITIATING CONNECTION Sep 30 10:08:19.685  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3163d82c0
    INITIATING CONNECTION Sep 30 10:08:19.705  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
    INITIATING CONNECTION Sep 30 10:08:19.756  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.800  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.852  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.876  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.898  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0

  • My zero Key isn't working after waking from sleep mode. This is a real problem for me because my password contains a zero

    My zero Key isn't working after waking from sleep mode. This is a real problem for me because my password contains a zero.  I don't recall spilling anything or jamming it just that it worked before I closed the computer and wasn't after I woke it up.
    I would like to fix the key but if that's not possible right away , Is there a way to reset my password without being able to type with a key thats in it?

    Start by swapping the keyboard. You don't need to spend a fortune, and handy to have spare. USB cables can be bad even new.
    When I had some problems Apple wanted to blame the mouse, keyboard, cable, but in the end I found
    A. run Disk Warrior
    B. Corrupt pref or conflict with version of Hardware Monitor and other background tasks

  • Black screen after waking from sleep mode - Compaq Presario CQ5110F

    My mother's computer has been having the problem listed in the subject -- after waking from sleep mode, the monitor just stays black, and won't come back. After trying everything I could find online, I eventually found the bios update which claims to fix the exact issue. The problem is that I guess my mother had opted to upgrade to Windows 7, while the bios update seems to only work for Windows Vista, as I get the following error message: "Your system does not meet the minimum requirements for this update. Update has been canceleld. (9998)." I've tried running the update in Vista compatibility mode, with no luck. I've tried using a different monitor, I've updated all the drivers, Windows Updates are all current, I've cleared CMOS. Any idea on how to fix this? It's very recent; only for about the past 2 weeks has this been happening, while we've had the computer for over 3 years. It's quite a waste of energy to keep it on all day.

    Hello liltwix,
    When taking your computer out of safe mode the screen just remains black, is that correct? I will try to help you with this issue.
    I understand you upgraded from Vista to 7, was that when the issue started or has the computer had windows 7 installed for some time before this problem started?
    Please respond back at your earliest convenience.
    Thanks
    Clicking the White Kudos star on the left is a way to say Thanks!
    Clicking the 'Accept as Solution' button is a way to let others know which steps helped solve the problem!

  • Satellite A660-18N - Powers off after waking from sleep mode

    My Satellite A660-18N powers off 2-3 seconds after waking from sleep mode. I upgraded the memory from 4GB to 8GB, using Crucial's website, so I know it's compatible. BIOS is updated to 2.00.
    Not sure what to do, how can I fix this without turning off Sleep mode completely?

    Hello
    >Currently I've turned off sleep mode altogether. I've also reset the BIOS settings from the boot menu but it hasn't fixed the problem
    And why you dont test it with pretested memory modules from an authorized service provider? The part number for such RAM is PA3677U-1M4G. Its one 4GB DDR3-1066 MHz memory module.
    Furthermore it would be interesting to know who says that Crucial memory is compatible Maybe its compatible to other Toshiba notebooks but fact is you have problems after waking from sleep mode and this happens only with Crucial memory and not with preinstalled modules.
    I dont think somebody here can provide you a solution for this because its just a compatibility issue and its user to user forum only.

  • Freeze after waking from sleep mode on MBP retina

    After waking from sleep mode my MBP retina freezes for 3-5 seconds. Mouse and touchpad don't work. I wonder if it's mountain lion problem or hardware problem. Anyone faced this?

    Just got a brand new model and OS X 10.8.2 (12C3012) and face the same issue, almost everytime it sleeps for too long. This is not a 3rd type SDD, this is a standard Apple SSD. I turned off the BT, I removed the almost every option from the battery saver mode. The current test is to disable the power nap - I will let you all know the result in a few hours.

  • My desktop background disappears after waking from sleep mode

    My desktop backgroung disappears after waking from sleep mode. Just converted to Lion.

    I spoke with Tech Support this morning. Apparently this is a known issue with Lion. I found it interesting that the rep insisted on saying that "it is the way Lion functions" instead of admitting that it is a GLITCH in the programming. He even said that it happens randomly and not on all computers and not all users experience this. That ought to tell you that it's a glitch.  Anyway, there is a "workaround" which is what you do to put a bandage on a persistent wound that should really get surgically stitched:
    You either have to log out every time you leave the laptop, or you have to change Energy saver preference to set the display to go to sleep AFTER the computer is set to log out (in Security preferences).
    Here is the article that instructs us on applying the bandage::
    http://support.apple.com/kb/TS4135?viewlocale=en_US
    Suffice it to say that Apple does not plan on stitching this one up any time soon..

  • My MacBook Pro won't reconnect to my Wi-FI automatically after waking from sleep mode

    Hello, everyone. Since I updated to Yosemite, my MacBook Pro won't reconnect to my Wi-FI automatically after waking from sleep mode.
    Does anyone know how to fix that?
    Thanks in advance,
    Arthur.

    Hi, arthurpacifico. 
    Thank you for visiting Apple Support Communities.
    Here are a couple troubleshooting steps that I would recommend trying to see if it corrects this issue.
    Intel-based Macs: Resetting the System Management Controller (SMC)
    http://support.apple.com/kb/HT3964
    Reset your computer’s PRAM
    http://support.apple.com/kb/HT1379
    If the issue persists, try the troubleshooting steps I have attached below.
    Symptom: After restarting or waking from sleep, my computer might not connect to the Internet
    After waking from sleep or starting up, your computer may not show that it is connected to a Wi-Fi network.
    After start or wake, your computer may indicate that it is connected to a network, but does not connect to the Internet.
    Solution
    Use these steps if your computer does not automatically connect to your desired Wi-Fi network.
    Check your TCP/IP settings in the Network pane of the System Preferences. Click the "Renew DHCP lease" button
    Choose System Preferences from the Apple menu.
    Choose Network from the View menu.
    Select Wi-Fi, then click the Advanced button in the lower-left hand corner of the screen.
    Click the TCP/IP tab from the top of the screen.
    Click the "Renew DHCP lease" button.
    Select the Wi-Fi tab and view your Preferred Networks list.
    Select each network and click the minus sign to remove those networks from your Preferred Networks list.
    Click OK and close the Network preferences.
    Remove your stored network passwords using the Keychain Access Utility.Restart your computer.
    Open Keychain Access from /Applications/Utilities. Your window will look like this:
    Remove your AirPort network passwords from the login keychain: Select the "login" keychain from the Keychain sidebar. Click the "Kind" column to order the list of keychain items by their type. Remove all entries of the kind: "AirPort network password".
    Remove your AirPort network passwords from the System keychain: Select the "System" keychain from the Keychain sidebar. Click the "Kind" column to order the list of keychain items by their type. Remove all entries of the kind: "AirPort network password".
    Note: The above steps will remove your Wi-Fi network passwords. If you do not know them, or if your network does not use passwords to restrict access, you should contact your network administrator.
    Join your Wi-Fi network. You will need to enter your password for your network again if it requires one.
    Wi-Fi: How to troubleshoot Wi-Fi connectivity
    http://support.apple.com/kb/ht4628
    Cheers,
    Jason H. 

  • Anyone's MacPro have problems after waking from sleep mode?

    After waking from sleep, my MacPro 2x2.4 Quadcore Intel Xeon freezes in several applications that had been running before sleeping. Mail and Firefox both get into endless loops trying to download data and will not force quit. Pulldown restart and shut down do not function when this is occurring. Must shuyt down manually from box and start again. Everything works fine again until it goes to sleep again.

    Start by swapping the keyboard. You don't need to spend a fortune, and handy to have spare. USB cables can be bad even new.
    When I had some problems Apple wanted to blame the mouse, keyboard, cable, but in the end I found
    A. run Disk Warrior
    B. Corrupt pref or conflict with version of Hardware Monitor and other background tasks

  • Dark screen remains after waking from sleep mode

    Whilst using Safari Version 3.1.2, Mac OS 10.4.11 on my Powerbook G4 (aluminum, 1.5 ghz), my screen remains dark upon waking from sleep mode. Trying to increase screen brightness is ineffectual for some reason likely related to this problem. My only workaround is to force shutdown and restart. Any ideas about a solution would be greatly appreciated.

    Hi Gary,
    This behavior is not a Safari issue but system related.
    Close all applications an run in utilities> disc repair permissions.
    After you done reboot an see what happens when your Mac gets to sleep mode again. This time don't open any applications to test it. Just leave it showing your desktop.
    Post back with the results ...
    Dimaxum

  • SMB shares die after waking from sleep mode

    When my Macbook is freshly booted, I can access the SMB shares on my linux server just fine. The fun starts when the computer is put to sleep and then awakened. About 50% of the time, the shares on my server are inaccessible after waking from sleep. When I click on the server in the Finder, it just says it's connecting and sits there. Not only are the shares inaccessible, but the server cannot be "ejected" (Item in use). Plus, the system cannot be rebooted nicely. It just hangs with the spinning wheel until I ctrlcommandreset the thing. Other services on the server remain accessible from the Macbook after samba dies (iTunes library, FTP). Occasionally, the shares will come to life if I sleep/wake the computer again, but that is rare.
    Tiger worked fine with the same server, it wasn't until the 10.5 upgrade that I began having trouble. I called Apple tech support about the issue, and waited 2 weeks for them to tell me to "install Bonjour on the server." I have formatted and reinstalled Leopard more times than I care to count, but the problem always remains. I've been dealing with this for almost a YEAR now and am totally desperate for a solution. Has anybody ever heard of this before?? The server is running Clarkconnect (Centos derivative).

    Hi Gary,
    This behavior is not a Safari issue but system related.
    Close all applications an run in utilities> disc repair permissions.
    After you done reboot an see what happens when your Mac gets to sleep mode again. This time don't open any applications to test it. Just leave it showing your desktop.
    Post back with the results ...
    Dimaxum

  • My iMac won't automatically connect to wifi after waking from sleep mode

    After dowloading the newest software update and performing a firmware update for my Airport router, my Imac won't connect to Wifi automatically after waking from sleep mode

    Please re-download and install the 10.7.3 update. You can locate it at 10.7.3 (Client Combo). Follow the on-screen instructions. Then test it out, if you still have the same problem please restart, when you hear the startup tone hold down the Option Key and then choose the Recovery Partition. Then open Disk Utilities and Repair Disk Permissions 2x. Then exit DU, restart normally and re-test.

  • 10.7.3 issues with reconnecting to the Internet after waking from sleep mode?

    My iMac worked great until this last update. Now it does not connect to the internet after I wake it from sleep mode. Any fixes?

    I have a similar issue.  My connection has been rock-solid since we went to Uverse, and now my computer loses the internet every 60-90 minutes or so. Driving me nuts.  iPhone still on wireless router to internet, so problem seems to be computer.

  • Bizarre app behavior after waking from Sleep Mode

    My iMac Core Duo runs like a top. It is fast and quiet. I have no problems with applications, both Universal and PowerPC. I maintain it with everything that I suggest others do in posts.
    But, there is this one strange quirkiness that I have put off mentioning because I kept hoping that each new OS X update would address the issue. It has to do with waking my Mac from sleep mode with it logged into my user account. Not every time, but most of the time, if I put my Mac to sleep or it goes to sleep from inactivity while it is logged into my user account, I experience strange application behaviors upon waking.
    For example, upon awaking Mail.app will contact my .Mac account and download any new mail that has arrived. But, if I try to open any of this mail, instead of opening, Mail.app will open a new outgoing email addressed to whomever sent me the mail I tried to open. Quitting and restarting does not solve this problem. Other apps demonstrate similar bizarre behavior. To only way to solve the issue is to log out and back into my user account.
    However, if I log out of my user account and then put the Mac to sleep from the Login Manager I don't experience this issue. So at night I always log out before putting the Mac to sleep.
    Anyone else experiencing similar issues? Any ideas on solving this? Do you think it is a bug in Universal Mac OS X?

    Sorry this isn't a solution, rather is a commiseration. Often after my iMac wakes from sleep mode it refuses to see my internet connection. I have to unplug and reset my DSL modem to force the computer to see that it exists.
    It sounds like the problem might be related, does anyone have any brilliant suggestions?
    Thanks,
    Lonnie

Maybe you are looking for