Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

ilovecode Author

Level 1

0 points

Mountain Lion no Wifi after wake from sleep

Hey guys,

I have the following problem:

after I wake my 17" MacBook Pro 8,3 (early 2011) from sleep by opening the lid, it starts searching for a WiFi network to join. It will just keep searching and searching, without ever finding anything. When I try to click on the WiFi icon in the menubar I get the beachball, also the System Preferences are affected by this crash - I can't go to "Network", it also beachballs. The only way out is a restart.

To prevent this from happening I can disable WiFi before putting my mac to sleep, but that's quite inconvenient. I have disabled all Auto Proxies, tried to delete the known networks from both the Network pane and the Keychain.

😟

MacBook Pro (17-inch Early 2011), OS X Mountain Lion

Posted on Jul 27, 2012 11:06 PM

Best reply

ilovecode Author

Level 1

0 points

Posted on Jul 28, 2012 1:22 AM

Ok, I finally fixed this myself.

Go to "System Preferences > Network" and select the WiFi-Service from the list on the left. Select "Options" from the bottom right of the right pane. In this window, delete all the known Networks and hit OK. Then go ahead and delete the WiFi device. Create a new WiFi device and you're done.

View in context

421 replies

FishNYC22

Level 2

390 points

Jul 29, 2012 9:02 PM in response to ilovecode

Here are the similar ones I have:

Launch Daemons:

com.adobe.SwitchBoard.plist

com.barebones.authd.plist

com.microsoft.office.licensing.helper.plist

Launch Agents:

com.adobe.AAM.Updater-1.0.plist

Dr_David

Level 1

10 points

Jul 29, 2012 9:08 PM in response to Dr_David

For completeness sake.. Here's my Login items. You can find YOURS by going to System Preferences, Users & Groups, Login Items:

(click to see it all)

kreme

Level 1

35 points

Jul 29, 2012 9:16 PM in response to primalman

primalman wrote:

How do we officially notify apple of this issue? Any one know?

Google Apple Feedback and the form should be among the first two or three links.

My problem won't generally restart until after I've connected to another network though and I won't be able to thoroughly test this until after I've gone to work and connected there.

Basically, what I did was disconnect by turning off Wi-Fi. Then I deleted my Wi-Fi in Network Preferences, along with all of my connections and created a new one. I also set my IPv6 to Local-only. So far, I haven't had an issue since and I won't know for sure until after I go back to work on Tuesday and re-connect to their Network.

Right now it seems to be working okay but this is an issue that will rear its ugly head after a couple of days so I'm not inclined to hold my breath at this point.

dzatona

Level 1

0 points

Jul 30, 2012 1:11 AM in response to ilovecode

So, finally I'm keeping my fingers crossed, but today I've opened the lid and wi-fi is working. For almost two days I have been looking for the fix and tried at least 3 of 4 of them. By THIS moment — everything seems to be working good. I have completely removed parallels and also Little Snitch 2.4 was installed on my MBP. I've uninstalled LS 2.4 and replaced to LS 3 Preview and wi-fi freeze has gone away just for now. Don't know if it help someone but let's keep trying! Come on guys, together we will do it! =) Still watching if it happen again. Will post my thoughts.

FishNYC22

Level 2

390 points

Jul 30, 2012 4:06 AM in response to ilovecode

I have Little Snitch installed as well. However I don't believe some of the others do. Also. Just realized I opened my MBP this am and just started typing this. No freeze. How novel an idea. Maybe it will fix itself.

Jul 30, 2012 4:40 AM in response to ilovecode

Parallels is the only thing I have in common, other than adobe stuff (designer). Could this be about parallels?

lungboy

Level 1

5 points

Jul 30, 2012 7:07 AM in response to ilovecode

Had stuff downloading in the background, started ping test, put MBP into display sleep. After some amount of time, the WiFi was turned off and didn't return until after I woke the system up.

64 bytes from 173.194.75.99: icmp_seq=369 ttl=46 time=31.335 ms

64 bytes from 173.194.75.99: icmp_seq=370 ttl=46 time=28.766 ms

64 bytes from 173.194.75.99: icmp_seq=371 ttl=46 time=27.688 ms

64 bytes from 173.194.75.99: icmp_seq=372 ttl=46 time=26.776 ms

64 bytes from 173.194.75.99: icmp_seq=373 ttl=46 time=34.237 ms

64 bytes from 173.194.75.99: icmp_seq=374 ttl=46 time=28.841 ms

64 bytes from 173.194.75.99: icmp_seq=375 ttl=46 time=28.762 ms

64 bytes from 173.194.75.99: icmp_seq=376 ttl=46 time=114.804 ms

ping: sendto: Network is down

ping: sendto: No route to host

Request timeout for icmp_seq 377

Request timeout for icmp_seq 378

Request timeout for icmp_seq 379

Request timeout for icmp_seq 380

Request timeout for icmp_seq 381

Request timeout for icmp_seq 382

64 bytes from 173.194.75.99: icmp_seq=383 ttl=46 time=29.295 ms

64 bytes from 173.194.75.99: icmp_seq=384 ttl=46 time=34.655 ms

64 bytes from 173.194.75.99: icmp_seq=385 ttl=46 time=27.608 ms

64 bytes from 173.194.75.99: icmp_seq=386 ttl=46 time=28.654 ms

dzatona

Level 1

0 points

Jul 30, 2012 9:39 AM in response to primalman

I think yes.

dzatona

Level 1

0 points

Jul 30, 2012 9:40 AM in response to ilovecode

There were almost 3 deep sleeps after all fixes, now everything is working properly. I tend to think that it was caused by Little Snitch 2.4 or Parallels. Will keep an eye and keep you informed.

kreme

Level 1

35 points

Jul 30, 2012 9:46 AM in response to kreme

IPv6 didn't solve my issue. I turned my Mac on this morning and Wi-Fi wouldn't connect again. Had to turn Wi-Fi off for 10 seconds and back on to get it to connect. I'm going to do a clean install today and see if it helps. For the record, I don't have either Little Snitch or Parallels on my machine. The only apps I have that aren't from the App Store are the same ones I had before I did my last Clean Install. My Wi-Fi connection worked fine then and it was the same OS. This appears to be an erratic bug with no real rhyme or reason.

It's very annoying.

Jul 30, 2012 9:48 AM in response to kreme

Yeah IPv6 didn't help for me either. I also don't have Little Snitch.

Might help if we report whether this happens while plugged in to ethernet. Since an AirPort issue is one of the leading hypotheses, and some people have reported that turning off Airport helps, I wonder if this happens if network access is available by another service.

dzatona

Level 1

0 points

Jul 30, 2012 9:58 AM in response to ilovecode

It is not about IPv6 or hardware issues, I suppose.

kreme

Level 1

35 points

Jul 30, 2012 10:06 AM in response to dzatona

Airport isn't the issue. I don't use airport. I'm also wireless. I have 12 minutes to go on my clean install. I'll see what happens after that.

Jul 30, 2012 10:08 AM in response to kreme

To clarify, by Airport I meant "Wi-Fi" (I guess the name of this service has been changed now).

kreme

Level 1

35 points

Jul 30, 2012 10:48 AM in response to Jonas Kaplan

Jonas Kaplan wrote:

To clarify, by Airport I meant "Wi-Fi" (I guess the name of this service has been changed now).

Gotcha. Well, a clean install didn't solve my issue. I've just turned off the Airport Utility through the terminal and will see what happens.

Mountain Lion no Wifi after wake from sleep