Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Macbook Connection Timeout?

Hey there,

I'm having the same issue but unfortunately none of all solutions described above worked out for me.

The only and last solution I have in mind is the downgrade to a previous version of OSx. I'm a bit reluctant about that because my problem started long time after my 10.5.2 update. So to me, this is not related.

Thank for the help
 
What revision Mac Book does everyone in this thread generally have who's having this problem? I have a Santa Rosa, and I never seem to have this problem.
 
I believe I have the original MacBook (black) released on May 16th, 2006.
 
I've just updated OS X. I'm now on 10.5.3. Unfortunately I still have the same problem.
I'm wondering, is it possible my airport card just died? I mean, would it behave like that?
 
What revision Mac Book does everyone in this thread generally have who's having this problem? I have a Santa Rosa, and I never seem to have this problem.
Click to expand...

I also have a Santa Rosa Macbook, $1399 model. I know you said that the update didn't fix anything, but I am downloading it as I write this and I am just crossing my fingers.
 
Same issue here with a new Penryn Blackbook and a Linksys WRT350N v1 router running DD-WRT v24 final. Just did a reset of PRAM/NVRAM, then a fresh install of 10.5.2, then immediate upgrade to 10.5.3. No change.

When this crops up I start to see erratic ping times to the router (1-80 seconds, yes 80000ms) and heavy packletloss. However, yesterday I caught a situation where while the router was unpingable, the (also wireless) 17" MBP in the room was pingable pretty normally. That really blew me away, and makes me think something about the router is at least partly to blame.

AirPort still shows connected, although usually the icon will indicate 1 bar less signal strength at that moment (weird). This usually (but not always) happens right after waking from sleep and looks exactly like what is documented at http://www.applefritter.com/node/22945. I get the same AirPort: Roam (DeAuth/DisAssoc) message in system.log. Eventually the Macbook will reassociate on its own and things return to normal but this always take a while. Flipping AirPort on and off won't do it.

I'm pretty sure this is some little incompatibility between certain router chipsets and airport drivers, and it certainly sucks. I'm tempted to buy an Airport Extreme from Amazon and see if things improve. Has anyone seen this problem with an AE as the router?
 
Set up your router to 802.11g only. I have had these problems with my 802.11n-upgraded Mac Mini and sadly I had to downgrade my home wifi to g-only (though it allows mixed g/n mode). Works flawlessly ever since, a tad slower though. My router is Dlink DIR-655.

I'd love to have the ability to manually choose if I want the computer to connect with G or N, if network offers a choice...
 
Code: 
64 bytes from 192.168.1.10: icmp_seq=26096 ttl=64 time=2.108 ms
64 bytes from 192.168.1.10: icmp_seq=26097 ttl=64 time=2.068 ms
64 bytes from 192.168.1.10: icmp_seq=26098 ttl=64 time=2.267 ms
ping: sendto: Network is down
ping: sendto: No route to host
ping: sendto: No route to host
64 bytes from 192.168.1.10: icmp_seq=26107 ttl=64 time=19.972 ms
64 bytes from 192.168.1.10: icmp_seq=26108 ttl=64 time=0.848 ms
64 bytes from 192.168.1.10: icmp_seq=26162 ttl=64 time=15.705 ms
64 bytes from 192.168.1.10: icmp_seq=26163 ttl=64 time=2.076 ms
64 bytes from 192.168.1.10: icmp_seq=26164 ttl=64 time=2.074 ms
64 bytes from 192.168.1.10: icmp_seq=26165 ttl=64 time=2.668 ms

The first 3 pings are before entering sleep. Coming back from from sleep, it takes about 9 seconds before the network fully comes back up, and it works for 2 seconds (sequence 26107 and 26108) before dying completely for 54 seconds, at which point the DeAuth message appears in system.log and AirPort apparently re-associates, and pings resume normally.

Unfortunately G-mode only is unacceptable and did not solve the issue in the link I posted, though I have yet to try myself. I have tried disabling ACK timing in DD-WRT but no change.
 
I changed my router and my Macbook works now. I went from a (Netgear) G router to a (Belkin) draft N. I'm not sure what the problem was since I did it before 10.5.3 came out. I really hope it doesn't come back.
 
Jpoon said:
What revision Mac Book does everyone in this thread generally have who's having this problem? I have a Santa Rosa, and I never seem to have this problem.
Click to expand...

It doesn't appear to be associated with any particular model of MacBook/iBook nor does it appear to be isolated to any particular router. I have an iBook G4 from 2004. Others have MacBooks and MBPs.

My previous laptop was a G3 iBook with the original Airport card (not Airport Extreme.) I was running the exact same OS (10.4.11) and same router settings. The G3 iBook had no trouble staying connected. The G4 iBook exhibited the frequent disconnects.

So, I think it's specific to Airport Extreme cards and it appears to have started for most people around 10.4.10. Apparently downgrading to 10.4.9 fixes the issue for some people.
 
BTW, I had some limited success with changing the network port config settings described in this thread. Sadly, the disconnection problem appears to have returned a week later, but maybe I'm on the right track.
 
My logs don't show exactly the same behaviour as yours.
When I toss a ping, it will ping descently for the first five minutes and then just show a:
Code: 
64 bytes from 192.168.1.1: icmp_seq=257 ttl=254 time=2.306 ms
ping: sendto: No route to host
ping: sendto: Host is down

If I disconnect and reconnect I'll get the same issue as the original post of canucks-17. The impossibility to connect having a "connection timeout" on the logs.
Otherwise the connection stays connected but cannot ping the router...
 
I just want to say I used to never had this problem; I got it when I set up a Airport Express, and it went away when I got rid of it.
 
Nice article. Thanks.

Unfortunately I cannot associate any of the specified issue with my problem. Yesterday I brang my macbook at a café down my street. I had the same exact problem with their open wireless. My connection dropped after a slightly longer time (7-8 minutes) and couldn't reconnect it back (connection timeout). I had to reboot/standby to do so.

So whatever wifi access I have: private WEP or open free, I got disconnect from the routeur with this error showing up in system logs:

Code: 
Apr 2 10:22:19 Lena airportd[940]: Could not find any preferred networks; trying broadcast requests..
Apr 2 10:22:22 Lena airportd[940]: Broadcast requests failed..
Apr 2 10:36:45 Lena airportd[1067]: FastFinder scanning channels again
Apr 2 10:36:54 Lena airportd[1067]: Error: Apple80211Associate() failed -6
Apr 2 10:36:55 Lena airportd[1067]: Could not find any preferred networks; trying broadcast requests..
Apr 2 10:37:06 Lena airportd[1067]: Error: Apple80211Associate() failed -6
Apr 2 10:38:00 Lena airportd[1085]: Error: Apple80211Associate() failed -6
Apr 2 10:38:00 Lena SystemUIServer[966]: Error: airportd MIG failed = -6 ((null)) (port = 37895)
Apr 2 10:38:11 Lena airportd[1085]: Error: Apple80211Associate() failed -6
Apr 2 10:38:11 Lena SystemUIServer[966]: Error: airportd MIG failed = -6 ((null)) (port = 37895)
Apr 2 10:39:23 Lena airportd[1097]: Error: Apple80211Associate() failed -6
Apr 2 10:39:23 Lena SystemUIServer[966]: Error: airportd MIG failed = -6 ((null)) (port = 37895)
Apr 2 10:39:35 Lena airportd[1097]: Error: Apple80211Associate() failed -6
Apr 2 10:39:35 Lena SystemUIServer[966: Error: airportd MIG failed = -6 ((null)) (port = 37895)

I'm about to purchase a new airport card because everything is leading me to the conclusion that my airport card is faulty/broken.
 
I though my issues had gone after I updated to 10.5.3. I didn't have any issues for 24 hours but then I started dropping my connection every couple of minutes I was sill able to get back on however. Fast forward 24 hours, I'm dropping my connection frequently and sometimes I get the 'connection timeout' error. Its getting beyond a joke.
 
I started having this problem about 2 days ago. Noticed that when my connection reads "low strength" on the bar I also can no longer see my neighbor's wireless networks. This is the at the same time when I cannot connect to my own.
 
Okay, this is seriously making me *really* angry. This problem renders my MacBook basically unusable for about 10 minutes after waking from sleep or being powered on. This is unacceptable. Any other ideas?
 
I basically tried everything I could. I finally decided to buy a new airport card. I'm waiting for it right now and cross my finger this is not due to an (more serious) issue like the motherboard or something...
 
All right, you probably won't like this but I just installed the new airport card I have ordered and everything is working just fine.
 
The wireless network at my job gives my MacBook conniption fits. "Flaky" doesn't begin to describe it, and the connection timeout issue persisted between restarts and cold boots. It's had this issue on occasion at home, but it's even worse at work.
 
Sorry guys, but ever since .5.3, I have been Connection Timeout free :). I feel bad that you guys are still having it as I am used the the common frustration. For the guy that was getting the new Airport card, man, just give Apple a ring and give them a piece of your mind, seeing if they can give you a new one instead of buying a new one. Good luck.

:apple: simon
 
IK noticed yesterday that mmy connection issues started after my MacBook was unplugged when it had previously been powered by the AC adapter. Here's what happened to me today:

I connected to the office wireless network while on battery. I then plugged my MacBook in. Later in the day, I unplugged it and walked around with it. At this point, the MacBook dropped the connection and had connection timeout issues. So I unplugged it, shut it down, and started it up again while unplugged. It reconnected and behaved the rest of the day regardless of whether it was plugged in or not.

I'll have to see if this was just a coincidence or whether I'm actually on to something, though.
 
Still suffering since 10.5.4, over a mount and counting. Apple thanks for letting me and thousands of other people down.
I'm hoping todays update may solve the problem, but I'm not holding my breath.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back