Ever since I installed 10.6 -- I constantly drop my wifi connection.
I have VPN turned off and the all the same settings from 10.5, and I never had a problem before.
Whether I am far away (reception is worse) or only 3 feet away, I drop my signal constantly for no reason.
I have latest Firmware on router and powered down modem and router.
Many times I can not turn off airport as well, and I need to restart my latpop in order to get a strong wifi signal again? Any suggestions?
My router is a Belkin G+ Mimo - most updated firmware
Thanks!
MacBook Pro 2.16 - 15 Inch,
Mac OS X (10.6),
4 GB RAM, 320 Gb HD
Hi, I installed SL like 2 weeks ago but from today I experienced dropping wi-fi.
Like every 5-10 minutes the internet doesn't work however wi-fi is still strongly connected.
By turning off airport and on again, the internet works for like 5-10mins.
SAME PROBLEM !!
"Just to add my voice in case Apple is counting, I'm having problems with dropped internet access since upgrading to snow leopard too. I have a mac mini that talks wirelessly to a time capsule. Worked perfectly before upgrade, now it drops connections constantly".
Holoon wrote:
Hi, I installed SL like 2 weeks ago but from today I experienced dropping wi-fi.
Like every 5-10 minutes the internet doesn't work however wi-fi is still strongly connected.
By turning off airport and on again, the internet works for like 5-10mins.
Please create a new thread and describe *in detail* what you mean by "doesn't work" - error messages, debugging steps you've tried,
etc.
If you're still "strongly connected" you're not experiencing the issue this thread addresses.
forum1983 wrote:
Oct 23 18:38:11 -MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
This means your router forcibly disconnected you because it felt your connection was idle too long.
Are you using a Netgear by any chance?
For example, some Netgear routers are known to have firmware bugs that cause this; here's an example of someone with a
different operating system experiencing a very similar issue:
radlure wrote:
That all sounds great BUT can you explain as easily why an Apple iMac, a macbook and an HP laptop never loss the wireless connection-while the MBP constantly lost it?
Could be a hardware issue with the MBP or the MBP's AirPort card, interference with the MBP, or different reception characteristics affecting the MBP.
Then there are just plain hardware issues that may be at play if, say, the other three machines had Atheros-based Wi-Fi chips and the MBP uses a Broadcom.
Finally of course there are possible issues with plists and keychains.
There are a wide variety of debugging steps that can be undertaken before accusing Apple of not testing their software before releasing it.
Could be anything (as long as it doesn't insult the Apple team)
I ran ubuntu from a livecd on the MBP and it never lost connection in over an hour of use-where as with 10.6.1 it couldn't stay connected for more than 15 minutes-but could lose the connection in as little as 5 minutes.
I had tried the file deletion fix (plist) and it didn't fix anything.
I still say it possible that there is a bug in leopard and sl with certain hardware that causes the thread topic.
Note: I was able to fix the dropping issue for my home network by upgrading the router and reconfiguring the network, but that does not explain why only one machine, the MBP, was continually losing the connection while the others either connected to wireless solely or in unison didn't.
I can see my the dropping of connection for my MBP varies locations to locations. The worst is with the 2wire router (AT&T) at home. At work, some router is ok and some router it seems be working fine.
So the dropping does have some relation with the wifi setting as well as the OS (in my case, 10.5.x was working fine).
But hey, I can not ask our MIS to change the router setting just because my problem while everyone else's PC are running fine.
I paid top dollars for my MBP. And I expect a reliable machine that I don't need to worry about. And compatibility means it is compatible, not sometime compatible.
If you buy a piece of equipment, and it will work only 90% of time, are you satisfied? This is called "Lemon". And certainly this is due to flaw in the quality control in Apple. Who else to blame?
I fixed my issue by manually adding in the DNS addresses into the DNS list within Network Settings/Airport/Advanced/DNS. I had to actually call my internet provider to get the proper one, as the one I had by default was causing drop outs. SL has issues with DNS addresses and it needs you to pretty much manually fix it to one or it jumps around and drops connections.
As Garettmac, I resolved my issue for now my merely changing the SSID for my network. The router was a bit wifty after that but a 2nd restart resolved the problem. We'll see how long the solution holds. Any bets?
radlure wrote:
Note: I was able to fix the dropping issue for my home network by upgrading the router and reconfiguring the network, but that does not explain why only one machine, the MBP, was continually losing the connection while the others either connected to wireless solely or in unison didn't.
Because by definition if a firmware update helped, it was probably a firmware bug.
It could be anything from an issue with how the router handled a certain sequence of packets to it not handling more than a particular number of clients properly.
This means your router forcibly disconnected you because it felt your connection was idle too long.
Are you using a Netgear by any chance?
For example, some Netgear routers are known to have firmware bugs that cause this; here's an example of someone with a
different operating system experiencing a very similar issue:
Thanks for the reply. I gathered as much from the kernel.log myself but I am still without a solution thus far. I am using a 2WIRE Residential Gateway provided by AT&T for their U-Verse service. I've logged into the gateway to update the firmware and it is currently up to date. I will try adjusting some of it's advanced settings as suggested earlier in this thread, I will let you all know if it works since I saw some of you are using the same AT&T routers. And/or I will look into the "fix" that the NetGear user did in the forum you provided a link to.
Just to support @radlure and myself, this is most definitely more work than any "joe-blow" mac user should have to deal with while setting up anything. These machines are very expensive when compared to similar products. It is no secrete that we all pay the extra price for a better "user" experience then offered by Mac's PC counterpart. Apple advertises and uses this as a selling point. Something to the effect of "It should just work" has been thrown around by Apple. So if I have to figure out how to login to my router, change advanced wireless settings, all just so my MBP will not disconnect from the WiFi every 5 minutes, I will but only because I have to. It isn't to unreasonable to expect a person to open up their notebook and power it up and it connect to the WiFi network without any fuss. The most work we or any other user should have to do is input a network key if one is needed. This idea goes right with Apple's motto. There is definitely something weird when all wired desktops/notebooks/Xbox's (either Mac or PC) have no connectivity issues, and that all wireless devices (except for MBP) work just fine. I find the above "fixes" to not even be fixes but a temporary workaround and that ultimately Apple WILL need to address this and release a update to fix this bug. Or at the very least acknowledge it as a legitimate problem if they can't do anything except wait for router manufacturers to catch up with new firmware upgrades that support MBP and other Mac devices.
I understand your frustration, but if a third party router isn't following applicable standards or has firmware bugs,
they have to fix them.
If it's Apple's software,
Apple has to fix it.
Given the vast majority of Snow Leopard users do
not have AirPort issues, it's hard to know where the exact problem lies.
I hate to repeat myself, but I have not had an AirPort connectivity issue since Mac OS X Tiger, where for others Tiger was the last time their network worked properly.
More often than not a router firmware update fixed users' connection issues.
Router manufacturers do
not issue updates to be "compatible" with Apple equipment; they release updates because Apple found bugs in their firmware.
So to reiterate, my MBPs "just work." Have for almost two years now.
I realize, that doesn't help you, and when mine didn't, I felt just as frustrated.
This is also why you should always contact AppleCare with these issues; if say Apple finds that many owners with a particular router are having problems, they'll investigate it and either fix their driver, if its their fault, or notify 2Wire of the problem, if it's the router's fault.
Whether 2Wire fixes the issue is, of course, entirely up to them.
I apologies if I am budding in because you all have smarts way above me in this so I thought I would try . I am now using a router so my daughter and wife can access the internet . But I feel I shouldn't have to have done that . This has to do with the internal airport card in my iMac . I posted this on the 25 of this month .
I have read all kinds of posts on airport , but they do not answer a question or two that I have . My daughter bought an iPod in April of this year and we were able to use the airport card in the iMac to connect to the internet . Then when Snow Leopard came out I installed it on that day . Then the connection started to be on and off then I couldn't turn airport on unless I rebooted then it may or may not work . One apple support person said that I shouldn't even be able to share the internet that way . I got ahold of another person in support and she had me do some things to see if the hardware was the problem . It wasn't so she had me do a clean install of snow leopard and it has worked fine until three days ago . Now apple support says that what I am trying to do is not supported and I was more or less lucky to have had it work that way . So they say I need a router . Even my wife's net book has been doing what the ipod touch has been doing . Now my other question is even if I had a router to connect to the airport card it would have to receive and transmit , which support says it is not a transmitter . What the blank is the airport card suppose to do the , besides take up room Thank you for reading this far .
I emailed a person and this is part of that persons response.
Ah… Mac OS X 10.6.x: and therein, lies the problem. Apple may have dropped explicit support for what is termed Internet Sharing with the release of Snow Leopard's first update, but it is not entirely clear if this is the case. Behind the scenes, there are mixed messages. Some AppleCare support and Apple Store employees have indicated that it is no longer explicitly supported, while others have insisted that it is. The question has been escalated to Engineering, but it may be weeks before there is an official answer or, if necessary, a fix. They've done things like this before—with Address Book interaction for dialing or SMS transmission with a mobile handset, for example, with the introduction of Mac OS X 10.5—and telephony features like that one I just described have never been reintroduced.
Yes 10.6 But what did the number one do . Just a couple of minuets ago the airport icon went empty and in order to get it to have the arrow in it I have to restart . Its just hard for a beginner . There just dosnt seem to be any answers right now but I am hopeful .