MacBook Pro constantly losing wireless connectivity

Hi folks,

Well, I read a ton of posts regarding MacBook Pro wireless networking issues before buying a wireless router last month, and now it's "me too."

Our iBook has no problems whatsoever with dropped connections, but the MBP loses access every few minutes or so. I usually follow a sequence of "Turn AirPort Off"/"Turn Airport On" to cycle the connection, and sometimes this works. It's an almost constant problem. This is a standard configuration MBP.

The router happens to be a D-Link DIR-615, but I've seen enough posts about problems with the Airport Express and MacBook Pros to know it's not the router that's the problem--it's the MacBook Pro (I notice a few similar posts even on the first page of this forum).

Dear Apple: what are you doing about this issue?

Has anyone else somehow resolved this problem? If there was only a couple of posts about this issue, then it might be written off as problems with a specific router, or specific users. But when there's a ton of messages all complaining about the same problem, then it's more likely a significant defect that needs to be fixed by the manufacturer, and won't be fixed by standard troubleshooting procedures of the mundane kind (Tech Support Theater: "Is your router turned on?").

Dear Apple: where are you?

MBP, Mac OS X (10.4.11), non

Posted on Jan 20, 2008 8:45 AM

Reply
2,055 replies

Feb 25, 2014 9:13 AM in response to ffredburger

I used the fix for my 2013 macbook pro

Worked well for 2-4 weeks.Then back to square one. Now even the fix below which i used previously is also not working.

This is what solved my problems (albeit temporarily) with WiFi disconnecting randomly, not appearing after awakening, etc.

1. Open network preferences from your WiFi icon in the menu bar. Then click advanced. Delete the network that is giving you problems.

2. Open Keychain in the utilities folder of your hard drive. Find the passwords that are stored for your particular network and delete them. There may be multiple passwords for your network, so search carefully.

3. Repair permissions using the disk utility.

4. Reboot the computer.


5. Reenter your network data to log into the network.



What in the world is apple doing!!! Why doesnt it have a perrmanent fix since a lot of people seem to have similar wifi problems....

Feb 25, 2014 9:56 AM in response to drmittal007

I've actually tried this as well as reinstalling the OS and the onyx cache fix. Nothing. I'll try again when I get home. Maybe the sequence order was different. I don't know. I'm pretty frustrated with Apple after reading these reviews and realizing how huge this problem is. BTW... I just ordered a USB wi-fi dongle or whatever they're called because I don't expect APPLE to do anything since this has been a problem for so long...I don't expect genus to say anything that hasn't already been said either...but I may go back just to complain(maybe they will FINALLY get the message. APPLE????!!!!***?

Mar 1, 2014 2:55 PM in response to ffredburger

From a bash shell on my macbook which loose the WiFi about 5-10 times per daY:


en1: 802.11d country code set to 'US'.

en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165

wlEvent: en1 en1 Link DOWN virtIf = 0

AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).



MacAuthEvent en1 Auth result for: 00:18:39:7a:9e:61 MAC AUTH succeeded

wlEvent: en1 en1 Link UP virtIf = 0

AirPort: Link Up on en1

en1: BSSID changed to 00:18:39:7a:9e:61

AirPort: RSN handshake complete on en1

Mar 1, 2014 3:01 PM in response to laurenmay1

Looking at my Macbook Pro, Today, March 1, 2014:

bash-3.2# uname -a

Darwin Michaels-MacBook-Pro.local 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64

bash-3.2# pwd

/var/log

bash-3.2# grep -i "Mar" wifi.log

Sat Mar 1 09:32:11.260 ***Starting Up***

Sat Mar 1 09:32:11.278 <airportd[66]> airportdProcessDLILEvent: en1 attached (up)

Sat Mar 1 09:32:23.090 <airportd[66]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 09:34:02.683 <airportd[66]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 12:24:50.146 <airportd[66]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 12:26:22.816 <airportd[66]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 12:26:23.879 <airportd[66]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 12:42:38.170 ***Starting Up***

Sat Mar 1 12:42:38.269 <airportd[66]> airportdProcessDLILEvent: en1 attached (up)

Sat Mar 1 12:43:18.478 <airportd[66]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 12:43:21.325 <airportd[66]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 13:03:13.122 <airportd[66]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 13:07:37.942 ***Starting Up***

Sat Mar 1 13:07:38.381 <airportd[65]> airportdProcessDLILEvent: en1 attached (up)

Sat Mar 1 13:08:12.514 <airportd[65]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 13:10:55.371 <airportd[65]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 13:16:20.314 ***Starting Up***

Sat Mar 1 13:16:20.344 <airportd[65]> airportdProcessDLILEvent: en1 attached (up)

Sat Mar 1 13:16:29.797 <airportd[65]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 13:16:38.074 <airportd[65]> _doAutoJoin: Already associated to “jachin”. Bailing on auto-join.

Sat Mar 1 17:25:04.118 <airportd[65]> _handleLinkEvent: WiFi is not powered. Resetting state variables.



I HIGHLY SUPPECT THE LAST EVENT is when I lost WiFi

Sat Mar 1 17:25:04.118 <airportd[65]> _handleLinkEvent: WiFi is not powered. Resetting state variables.


PROVES, my WiFi Card is for some REASON LOSING POWER. PROOF WILL BE IF THIS REPEATS...

Mar 1, 2014 3:30 PM in response to uzi73mm

So, I see this:


HIGHLY SUPPECT THE LAST EVENT is when I lost WiFi

Sat Mar 1 17:25:04.118 <airportd[65]> _handleLinkEvent: WiFi is not powered. Resetting state variables.


As either the WiFi card is actualy losing power.... hardware issue.. but turning WiFi OFF, then ON resolves it.... So I think Apple can fix this via Software... since I do manally when it goes down....

Mar 1, 2014 4:10 PM in response to ffredburger

After installing 10.9.2, I just reset my router to all the channels that the router would do, that my MBP supported. Way more in the Mac than the R6300. For the most part it will hook up for a couple of seconds, then drop saying there is no WiFi to connect to, then the machine freezes. But it constantly tries to connect then fails, most of the time not freezing. But the strange things is that it's trying to connect.

Mar 1, 2014 4:53 PM in response to TheGuyintheProjectionBooth

This issue has been absolutely maddening for me. So much so that when Apple came out with their Mavericks fix this week and the issue was not addressed, a posting where I was at my wit's end was deleted by Apple.


I still believe in Apple products because I've used PCs and PCs are certainly for the birds. However, in searching this forum, I came across a response by an Apple tech guru about changing router channels.


I am looking for any type of fix that won't involve surrending my computer for days on end to the Genius, having to resintall operating systems and praying no data is lost.


Anyway, got on the phone to Linksys technical support and turns out they have received numerous calls from Mavericks users. The person I spoke to knew exactly which channel to change to. Did so, and am getting lightning fast connectivity with no hang-ups.


Please you-who-are-in-charge-of-the universe may this continue!!!!!

Mar 1, 2014 5:42 PM in response to uzi73mm

uzi73mm wrote:


I HIGHLY SUPPECT THE LAST EVENT is when I lost WiFi

Sat Mar 1 17:25:04.118 <airportd[65]> _handleLinkEvent: WiFi is not powered. Resetting state variables.


PROVES, my WiFi Card is for some REASON LOSING POWER. PROOF WILL BE IF THIS REPEATS...


Then reset the SMC if you haven't already:

http://support.apple.com/kb/HT3964

Mar 2, 2014 9:09 AM in response to ffredburger

Looking at /var/log/system.log you can see the NIC itself, NOT ANY ROUTER is the issues....Also, NO VPN client/agent were running at that time...


Mar 2 11:46:07 Michaels-MacBook-Pro kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0

Mar 2 11:46:07 Michaels-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

Mar 2 11:46:07 Michaels-MacBook-Pro.local airportd[65]: _handleLinkEvent: Got an error trying to queyer WiFi for power. Resetting state variables.

Mar 2 11:46:08 Michaels-MacBook-Pro kernel[0]: flow_divert_kctl_disconnect (0): disconnecting group 1

Mar 2 11:46:09 Michaels-MacBook-Pro.local acvpnagent[75]: The network interface for the VPN connection has gone down.

Mar 2 11:46:09 Michaels-MacBook-Pro.local acvpnagent[75]: Function: logInterfaces File: ../../vpn/AgentUtilities/Routing/InterfaceRouteMonitorCommon.cpp Line: 477 IP Address Interface List: FE80:0:0:0:1240:F3FF:FEEE:D898

Mar 2 11:46:09 Michaels-MacBook-Pro.local acvpnagent[75]: A network interface has gone down.

Mar 2 11:46:09 Michaels-MacBook-Pro.local acvpnagent[75]: Function: logInterfaces File: ../../vpn/AgentUtilities/Routing/InterfaceRouteMonitorCommon.cpp Line: 477 IP Address Interface List:

Mar 2 11:46:09 Michaels-MacBook-Pro.local acvpnagent[75]: Function: applyHostConfigForNoVpn File: ../../vpn/Agent/MainThread.cpp Line: 9674 No network interface is available, cannot determine potential public addresses.

Mar 2 11:46:09 Michaels-MacBook-Pro.local acvpnagent[75]: Current network state: No network interface

Mar 2 11:46:09 Michaels-MacBook-Pro.local acvpnagent[75]: Function: applyHostConfigForNoVpn File: ../../vpn/Agent/MainThread.cpp Line: 9674 No network interface is available, cannot determine potential public addresses.

Mar 2 11:46:09 Michaels-MacBook-Pro.local UserEventAgent[11]: Captive: CNPluginHandler en1: Inactive

Mar 2 11:46:09 Michaels-MacBook-Pro.local configd[57]: network changed: v4(en1-:192.168.0.5) DNS- Proxy-

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacBook Pro constantly losing wireless connectivity

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.