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...

Similar Messages

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

Leopard unable to find preferred WiFi network after waking from sleep

This keeps happening sporadically - I have a WEP encrypted (would use WPA2, but roommate's old iBook can't use it) network with a non-broadcasted SSID. I've entered it into the preferred networks list as the only entry. About maybe once in every 4 or 5 times that I wake the system from sleep by opening the lid, it will fail to find my wireless network and the only way to get it to pick it up again is rebooting the machine. I've even had this happen while sitting right next to the router, so it's definitely not a signal quality issue...
Any ideas?
Ryan

FYI, I had the same issue with Leopard not remembering my preferred network, and tried every suggestion I could find from these lists -- to no avail. I filed a bug report with Apple, who responded by asking me to send a log file to them from my machine.
They wrote back, after having determined it was a keychain problem. To quote Apple:
"Please use the Keychain Access utility (in Applications -> Utilities) to attempt to repair your login and system keychain.
In the worst case, you may need to recreate your system keychain:
sudo systemkeychain -C -f
and then you will need to manually join your AirPort network once to write the password to the system keychain."
FYI what Apple failed to mention is that once in Keychain Access, there is a "Keychain Access First Aid" menu option that I didn't notice until too late. Brute force deletion of the login and system keychains worked for me.
Hope this helps (you and the hundreds of others with this issue)

MBA doesn't connect to wifi network after waking from sleep

I just bought a new MBA 13". More often than not, it fails to connect to my wireless network when it wakes up from sleep. This is annoying to say the least. Any ideas?

Hi,
I'm thinking about a trouble with the route table. Try this in a terminal session after startup:
netstart -rn
ping <network address>
After somes answer, close the cover to go to sleep mode.
Open the cover and look the result of the ping command
Normaly you don't have a network
cancel the ping command and redo the netstat commande
Normaly some rows are missing in the result (i don' know why)

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.

IMac loses WiFi connection after waking from sleep on OSX 10.8.2

Bought a new mid-2011 21.5 inch IMac this week. It is not re-establishing WiFi connection after waking from sleep. Was happening on OSX 10.7 that it came with, so updated to 10.8.2 and same problem exists.
I am running a mid 2012 MacBook Pro with Retina Display alongside, on OSX 10.8.2 and no problems at all. Cannot work out what is causing the IMac to fail and neither can Apple!
Could it be the Netgear Wireless Router 3 years old? Full signal strength!

Me too!
I am on a MAC Pro desktop and I am having the same issues. I go to system preferences and just click the network icon. Then I close mail and when it opens it now sees the network. This is getting very annnoying.

Losing WiFi connection after waking from sleep

I've iMac 27 in. with recently upgraded OS X Lion to 10.7.4. After this was done the problems strated with connecting to Wi-Fi through my Time Capsule (2TB, 802.11n 4th Gen) after waking from sleep. Everything works fine when iMac is started after shutdown. My internet router is connected through ethernet cable to Time Capsule and iMac is using Wi-Fi connection with Time Capsule.
I've tried to install iMac Wi-Fi update v1.0 but it I cann't do it because my OS X is 10.7.4 and the update installer is stopping the installation after the check of my OS version.
Could anybody help to solve this problem, please?

but when the
computer goes to sleep and is then awakened, there
are no wireless networks listed in chooser... like
there are no wireless networks available...
Hi greaser5!
That is definitely NOT typical operation. Yes, your Core Duo iMac must restart after sleep, but It should reconnect to a working network instantaneously (less than a second), although it will probably take longer than that for your iMac to fully restart after sleep and actually be able to use the network.
Delete all prior wireless configurations that you have saved on the "Location:" selector of the Network panel of System Preferences. On the Network>AirPort>AirPort panel also delete all your preferred wireless networks. Click the "Apply Now" button.
Restart your Mac. Turn on AirPort. Use the Network panel's "Assist me..." button and the following blue "Assistant..." button to configure a fresh wireless connection to your working wireless network. This will be fresh and total, just as you did when your iMac was new. There is no need to give your network either a new name or a new password, as the old ones will work just fine in the new configuration, since as you know, the current network is working fine, the iMac simply can no longer connect to it correctly using its current configuration.
I have not been able to test the above on a Core 2 Duo, so do not know first hand if it will make any difference on those iMacs, but that or some similar fiddling should resolve the issue.

Wifi won't connect to WPA2 network after waking from sleep, requires reboot

My office has a WPA2 network that I use my MBP to connect to. When I go home for the day, I close the MBP and put it to sleep. When I get home and open it, it automatically connects to my home wifi network. I do the same coming back to work and when it wakes up it shows a connection to the wifi network, but whenever I initially do any network task, the connection drops and I am unable to connect until I reboot my mac.
I've tried turning off the wifi before sleeping, then turning it back on, but it does the same thing.
Any ideas?

Hi,
I'm thinking about a trouble with the route table. Try this in a terminal session after startup:
netstart -rn
ping <network address>
After somes answer, close the cover to go to sleep mode.
Open the cover and look the result of the ping command
Normaly you don't have a network
cancel the ping command and redo the netstat commande
Normaly some rows are missing in the result (i don' know why)

Can't connect to any wireless network after waking from sleep

I have a Netgear wgr814 wireless router and a Powerbook 12" 867mhz. A few months ago, every once in a while when the PB awoke from sleep, it would not be able to connect to any wireless networks. My network showed in the airport menu, but the computer would not connect to it. I believe that the network settings show a self assigned IP of 169.x.x.x. Usually I can see 4 networks in the airport menu, but when it gets in this state only mine shows. Nothing I did on the computer side could make the computer reconnect: renew dhcp, restart, reseat airport card, etc.
After trial and error I found that if I restarted my router, the pb would reconnect and all would be well. The problem occurred about once a week for a while. Since resetting the router fixed the problem I thought that it may be my router so I updated the firmware. After doing so, the problem didn't occur for about a month, but now it happens at least once per day. Resetting the router always fixes the problem. I don't have to do anything to the PB. Once the router comes back up the PB obtains its IP and is happy again.
I'll mention that a Dell Laptop on the same network never has any issues and when the PB loses connection the Dell is always fine.
What could be doing this? My PB is over 3 years old, so is the airport card starting to die? That's the only thing I can think of.

hi there
alright.... I tried a bunch of things and I'm not exctly sure what I did that did the trick, but I got the problem solved. I turned off the WPA encryption on the AP. Then I turned it back on with a different password.
I wonder if the first password I had was too short and that was some how causing confusion.

Problem with external HD when waking from sleep

I have just bought a formac oxygen mini 80G external HD, i am using firewire to connect to my iBook. Problem is that pretty much everytime I wake from sleep the warning dialog appears saying that I didn't eject the drive properly and some data may be lost. Any ideas?
Thanks in advance
iBook G4 Mac OS X (10.4.6)

Hi, r.r.
The behavior you describe implies that your FireWire drive is not recognizing Mac OS X power management commands: when the Mac enters sleep, the drive may actually be powering-off.
If a FireWire drive is powered off or disconnected without first being Ejected, you would also see that message. In some cases, that can result in the partition map of the FireWire drive becoming corrupted, requiring that one use data recovery tools or services — such as discussed in my "Data Recovery" FAQ — to recover the data on the drive.
1. Check with Formac to see if there is a firmware upgrade for your FireWire drive.
2. In combinations, try a different FireWire cable and a different FireWire port on your Mac.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

13"w/ext display loses WiFi connection after waking from sleep

I have my 13" macbook pro (mid-2009) connected to an external monitor. When the system goes to sleep and wakes up, the wifi is disconnected and an error window pops up saying something to the effect of another computer is using the IP address assigned to my computer.
If I reset the modem it usually works, otherwise I must wait about 15 minutes for system to connect again.
It does not happen if there is no monitor connected to the notebook.
Is there something I can do to stop this from happening?

I have a strong suspicion that I am getting wifi interference from my neighbors. Several new wifi signals have appeared in the last month coinciding with new neighbors moving in and some old ones getting wifi. Upstairs, I can pull up 6 or 7 networks, some broadcasting on the same channel. Downstairs, where my MacPro resides, I do not see those networks. My problem seems to manifest itself on my MacBook Pro when I move upstairs and can pick up the extra networks.
When I power cycled my router this morning, I noticed it changed channels from 11 to 6, indicating that the Auto setting is determining a better channel. Also, this problem seems worse after 5 pm. So, I'm chalking this one up to neighbor interference. If my iPhones could use the 5 GHz band, I'd use that exclusively... or maybe it's time for a simultaneous dual band router.
I wish I had a dollar for every time I've advised a customer that interference was the cause of his wireless connectivity issue.

AirPort does not auto-connect to existing network after waking from sleep

...but I can easily connect it manually. I read the FAQ on this subject and followed the resetting steps in system preferences/network (the procedure was specific for Intel iMacs-but I did it anyway)
It did not help. The flaw just occurred a couple of days ago, after a year of flawless operation Please help.

Solved! I trashed the internet connect preference in the library, and it worked!

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.

On my new iMac, mail has no sound after waking from sleep. If I select do not wake for network access in general preferences, the problem does not occur. Anyone have an idea on how to fix this?

On my new iMac, mail has no sound after waking from sleep. If I select do not wake for network access in general preferences, the problem does not occur. Anyone have an idea on how to fix this? Thanks --

Same here on an older iMac since Lion. Thanks for the uncheck wake for network access tip though, it doesn't do it either in that case, I will leave it that way.

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

Problems with wifi network after waking from sleep

Similar Messages

Maybe you are looking for