Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I too was having this issue when i updated from 10.6.4 to 10.6.5. I installed 10.6.6 on a usb drive and left 10.6.4 on my main drive. I started comparing the two, and noticed that the updated system (10.6.5) was getting very low signal strength (93 dbm on 10.6.6 and about 55 10.6.4) so I knew it had to be a software issue. I took it to the apple store, and of course they didnt want to hear it. They simply told me to replace the wireless card and if that didnt work to replace the mother board. I kept searching for a way to revert back to the 10.6.4 airiport driver while still on 10.6.6 and i ran across this thread.

http://discussions.info.apple.com/thread.jspa?threadID=2644274&tstart=0&start=315

look at the post by chromatic8 Jan 10, 2011 10:01 AM

In response to that thread, I found instructions on how to revert back to the 10.6.4 driver.

http://discussions.info.apple.com/thread.jspa?threadID=2644274&start=330&tstart=0

look at the post by tenortim Jan 13, 2011 12:01 PM

This will solve the issue if you are having trouble after upgrading to 10.6.5, Apple obviously changed the driver in 10.6.5.

I realize that alot of these posts are before the update, but hopefully this will help others. I was about ready to trade mine in, it was driving me nuts.
 
I am connecting to a DLink DIR-655. I have a 2007 MacBook that gives connection timeout. With tinkering, I have been able to get it to connect for about a minute before disconnecting. After it disconnects, it can never connect again.

Devices that work from the exact same room of the house:
Nintendo Wii (.11g + WPA2)
iPhone (.11n + WPA2)
2008 MacBook (.11n + WPA2)
Airport Express "n" (.11n + WPA2)

I tried setting the router to "g only". All the above devices still worked. The problematic MacBook did not.

I just remembered that this particular Macbook had a problem with another DLink router at a different location. I actually took the Macbook to the Apple store and explained the problem to the genius bar with no resolution. Maybe it is an incompatibility with DLink?

I have performed the procedure to reset the "SMC" and "PRAM" with no change in behavior.

Right now, the system prompts for password, then gives "connection timeout" within a second or two. The system works fine via ethernet, of course.

I just tried again, and now it just repeatedly prompts for the WPA password over and over without connecting.
 
I too was having this issue when i updated from 10.6.4 to 10.6.5. I installed 10.6.6 on a usb drive and left 10.6.4 on my main drive. I started comparing the two, and noticed that the updated system (10.6.5) was getting very low signal strength (93 dbm on 10.6.6 and about 55 10.6.4) so I knew it had to be a software issue. I took it to the apple store, and of course they didnt want to hear it. They simply told me to replace the wireless card and if that didnt work to replace the mother board. I kept searching for a way to revert back to the 10.6.4 airiport driver while still on 10.6.6 and i ran across this thread.

http://discussions.info.apple.com/thread.jspa?threadID=2644274&tstart=0&start=315

look at the post by chromatic8 Jan 10, 2011 10:01 AM

In response to that thread, I found instructions on how to revert back to the 10.6.4 driver.

http://discussions.info.apple.com/thread.jspa?threadID=2644274&start=330&tstart=0

look at the post by tenortim Jan 13, 2011 12:01 PM

This will solve the issue if you are having trouble after upgrading to 10.6.5, Apple obviously changed the driver in 10.6.5.

I realize that alot of these posts are before the update, but hopefully this will help others. I was about ready to trade mine in, it was driving me nuts.


Thanks a bunch man, ima try to do that and see if it works :D
 
try this

To cut to the chase, you can run the 10.6.4 drivers on 10.6.6. To do so,
1) Download the 10.6.4 Combo update and the Pacifist program that allows one to extract files from, amongst others, ".pkg" files.
2) Mount the update .dmg, open the package in pacifist, extract the subtree "/System/Library/Extensions/IO80211Family.kext" to a convenient location.
3) As root, cd to /System/Library/Extensions, rename IO80211Family.kext to IO8021Family.10_6_6 (or anything else to back it up), and copy in the replacement IO80211Family.kext that we extracted from 10.6.4.
4) Download, install and run "Kext Utility" (Google it, it's at Insanely Mac). It should ask for your password, run, and fix up the kext permissions and caches.
5) Reboot. You should now be on the new (old) driver/firmware. Verify by running "About this Mac" -> "More Info" -> "Network" -> "Airport". As stated, the newer firmware is 2.1.14.5, the working firmware is 2.0.19.10.
 
Hello fellow MacBook Wi-Fi users encountering connection timeouts,

For the last 2 days that I have owned my MacBook Pro (13.3", mid 2010 -- bought used), its Wi-Fi connection was working perfectly. Today, coming back from sleep after lifting up the lid, it wouldn't establish a Wi-Fi connection, displaying "Connection timeout" in the dialog, and the following message in the logs:

3/11/11 10:50:48 PM SystemUIServer[134] Error joining Bbox-B9CE18: Connection timeout (-3905 timeout connecting)

So I found this thread, where someone mentioned switching channels on the access point. I switched mine from "Auto" (most likely 11 in France) to 6. Immediately afterward, I entered the password once again and the MBP connected successfully, instantly.

Seeing that, it was obvious the current channel was the cause of the problem. It was probably crowded and Mac OS wasn't allowing enough time for the handshake to finish, as opposed to other devices on the same channel which connected fine.

Hopefully this will help someone else.
 
This could end up being yet another one of those "anecdotal fixes" but it worked for me after months of trouble shooting.

I changed the channel from 11 to 6.

Oh my! I'd been getting knocked off my home network alot lately. In the last week I narrowed it down to whenever my brother was home (which is once or twice a week) and he started using his new MBP, my connection to the network would go. I searched loads one evening and gave up, then after not being able to use my network 3 days in a row I just did another search and found this hint. It work perfect! :D I immediately connected straight back to the network so thank you very much for sharing this info :D:D
 
Still problem

I still can't connect to my wireless router on my macbook pro.
Version 10.6.7
Get this connection timeout problem everytime.
All the windows machines can connect with no problems.
I won't be buying a mac again.
 
Did you do the method in #101 and #107?

I still can't connect to my wireless router on my macbook pro.
Version 10.6.7
Get this connection timeout problem everytime.
All the windows machines can connect with no problems.
I won't be buying a mac again.

Did you do the method in #101 and #107?


To cut to the chase, you can run the 10.6.4 drivers on 10.6.6. To do so,
1) Download the 10.6.4 Combo update and the Pacifist program that allows one to extract files from, amongst others, ".pkg" files.
2) Mount the update .dmg, open the package in pacifist, extract the subtree "/System/Library/Extensions/IO80211Family.kext" to a convenient location.
3) As root, cd to /System/Library/Extensions, rename IO80211Family.kext to IO8021Family.10_6_6 (or anything else to back it up), and copy in the replacement IO80211Family.kext that we extracted from 10.6.4.
4) Download, install and run "Kext Utility" (Google it, it's at Insanely Mac). It should ask for your password, run, and fix up the kext permissions and caches.
5) Reboot. You should now be on the new (old) driver/firmware. Verify by running "About this Mac" -> "More Info" -> "Network" -> "Airport". As stated, the newer firmware is 2.1.14.5, the working firmware is 2.0.19.10.
rsilvestre is offline Report Post Reply With Quote
 
Did you do the method in #101 and #107?


To cut to the chase, you can run the 10.6.4 drivers on 10.6.6. To do so,
1) Download the 10.6.4 Combo update and the Pacifist program that allows one to extract files from, amongst others, ".pkg" files.
2) Mount the update .dmg, open the package in pacifist, extract the subtree "/System/Library/Extensions/IO80211Family.kext" to a convenient location.
3) As root, cd to /System/Library/Extensions, rename IO80211Family.kext to IO8021Family.10_6_6 (or anything else to back it up), and copy in the replacement IO80211Family.kext that we extracted from 10.6.4.
4) Download, install and run "Kext Utility" (Google it, it's at Insanely Mac). It should ask for your password, run, and fix up the kext permissions and caches.
5) Reboot. You should now be on the new (old) driver/firmware. Verify by running "About this Mac" -> "More Info" -> "Network" -> "Airport". As stated, the newer firmware is 2.1.14.5, the working firmware is 2.0.19.10.
rsilvestre is offline Report Post Reply With Quote

I cannot wait to try this... I've spent so many hours on a fix and cannot find a solution as of yet. I find it absolutely crazy that Apple cannot and has not worked this into their software updates. I can't say that I won't buy a mac again, but I can say that I am thoroughly disappointed in this persistent problem with my 2007 Macbook pro.

I'll try this and report back.
 
Ok so I tried this method and got nowhere unfortunately. I was really hoping this would work for me, wishful thinking I guess!

Would be great if anyone has any other ideas... Please?! I think I'm going to setup a genius bar appointment.
 
I bought my MacBook pro in 2008, and had similar issues. I swapped the broadcom card for an atheros based card and it worked great until 10.6.5 when I had to do the above process.
 
I bought my MacBook pro in 2008, and had similar issues. I swapped the broadcom card for an atheros based card and it worked great until 10.6.5 when I had to do the above process.

Can you recommend the exact model and place of purchase for your Atheros card? Might have to try this since nothing else works.
 
Connection Timeout

What ive done so far that hasent permanently fixed the "connection timeout" problem:

-unplugged the router/modem
-changed the channels (from 1 to 11)
-reset the modem back to factory settings
-changed my wireless network name and password several times
-karate chopped it

And most of these things were suggested by qwests "techies". Finally i called the manufacturers of the router itself; ie.. actiontec, the technical support number is 888-436-0657, and got to speak to an extremely kind indian for 10 minutes. basically, i lied to the automated phone screener and said that i bought my router from a store like bestbuy when in reality i got it off of craigslist. the automated phone screener just wanted to know if i was in the one year warranty time. lying to robots isnt a sin, right?

the solution:

change my wireless settings from WPA/WPA2 to WEP, which is less secure, but ITS ACTUALLY WORKING!!!!

long story short, see about calling the manufacturers of the router for help.
 
In the case of my MacBook that is having problems, it works flawlessly with my Airport Extreme and Airport Express. So far, both problems were with Dlink routers.

I'm still having the problem, btw. (original post is on this same page)
 
I tried everything in this thread and finally I did something that worked!

I used an identical linksys router (down to the model, broadcast channel, etc.) and it worked like a charm. The problem was with the router and not my macbook :D
 
fixed - finally

i feel like i knew this was the issue but had to re-learn it...

as a previous user said,
"change my wireless settings from WPA/WPA2 to WEP, which is less secure, but ITS ACTUALLY WORKING!!!!"

this is on a Belkin W54G, Mac OS 10.5.8.

It WAS working w/ WPA before, but if I added another computer (eg. work computer came home for a weekend) my home computer would lose connection... this fixed it.
 
The Real Fix - Hopefully

Hey guys,

I am a computer technician and I have had several clients complain of this issue. After attempting the normal diagnoses with the router, computer, software, and hardware, I couldn't isolate the problem.

As it turned out, for some reason the macbook antennae are polar. On each of the computers, I switched the antennae on the wireless card and it fixed the problem. Please let me know if you guys have any success with this.

Max
 
I've experienced this problem off and on for years. I find it most often happens with my Belkin N router while my MacBook is the only device connected. I've never had any issues with Linksys routers running DD-WRT, although the stock firmware can be iffy. I've also had a lot of trouble with Netgear routers.

A friend of mine recently got a new Macbook Pro 13", and it seems to have the kiss of death. Anywhere she brings it, one of two things happen to the wireless network it's on: either her MacBook will say "connected" but not actually allow her to access anything, or her MacBook will connect and work fine while somehow blocking access to all other wireless devices (Mac, PC, and Linux). It'll even occasionally cause problems with wired clients on the same router. Interesting issue…
 
Hey guys,

I am a computer technician and I have had several clients complain of this issue. After attempting the normal diagnoses with the router, computer, software, and hardware, I couldn't isolate the problem.

As it turned out, for some reason the macbook antennae are polar. On each of the computers, I switched the antennae on the wireless card and it fixed the problem. Please let me know if you guys have any success with this.

Max

When you say "switch the antenna" do you mean you opened the unit up an physically switched the antenna leads?
 
That is correct. There are two different versions of the WiFi card inside the laptop. One has 3 leads, and one has 2. Obviously on the one with 2 leads, you just switch them (black and gray). On the card with 3, I believe I switched the outer ones. Let me know if you guys have any success with this.
 
One simple step ! :)

all you have to do to fix this on going problem is go up the top on your mac where the connection bars are. click the icon and click on "Turn AirPort Off" then close the mac lid and wait a while (approx. 1 hour) then open the mac lid and and turn airport on and it should be connected again :) if not repeat actions a couple of times , any other questions contact me on my email : jellybean_yum22@hotmail.com ;)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.