Wifi Constantly Dropping in Lion

Add me to the list - must be MacBook Pro related - new MBP 10,1 (OSX 10.8) Wifi connection dropping and reconnecting same as old MBP...

Thank you thank you thank you!!!

Finally got rid of the disconnections!!!

If I ever run into you in real life drinks are on me

jrpeterson5 wrote:

This tells us what we pretty much already know - not a hardward issue....has to be something in Lion. I haven't installed Mountain Lion yet but probably will soon. Just wanted to chime in that the MacBook Air has no connection issues when running Windows 7 in Bootcamp.

I've stated this several times before - it's Lion, but it may not be a software bug in Lion.

The example I cite is imagine the router has a firmware bug where it calculates "2 + 3" as "5" but "3 + 2" as 6.

It's not the responsibility of Apple to work around the broken router and always make sure it only adds "2 + 3," but if Windows does nothing but add "2 + 3" then Apple gets blamed for having a "bug" when it's the router that's at fault. (The "It works under Windows!" fallacy.)

This does not mean it's not a Lion bug - it certainly could be - but rather that your experience does not necessarily prove that it is.

Something is wrong here! Every thing I write , disappears immediately

Final Fix..

Downgrade the kext/driver of wifi to snow leopard version kext.

juato4 wrote:

Final Fix..

Downgrade the kext/driver of wifi to snow leopard version kext.

Well, this can work, because it allows your mac to ignore the errors that your wireless modem, or ISPs DNS/connection has. There has been a demonstration of the cause being related to dropped packets which make other devices seem "slow". A couple of people have switched just ISPs and fixed the problem, so you might want to do some more investigation of the cause of your specific issues to see if other people using the same ISP in your "area" have the same problem. In other words, if you have friends with the same ISP, go see if you have the same problem on their network. If you have friends with another ISP, or a coffee shop or something that you know is using a different service, see if you have the problem there.

Talk to your ISP if you can determine that you only have the problem with that ISP. One person reported that their ISP's technical team said that their network had a lot of packet loss, and this was causing DNS over UDP to be very unreliable and other things related to Apple's new network security measures instituted in Lion, to create "you are not connected to the internet" messages.

In particular, this person had the same router as a friend who was on a different ISP, in the same building. He litterally went to the basement, and switched phone lines at the punch down board so that he was using his friends phone services and thus DSL service. Suddenly, he had no more problems.

There are lots of diffferent experiences people are having, but suddenly, it really seems that Apple may be relying on an advanced network feature or behavior which not all networks can provide, reliably.

Thank you gphnei. I was one of those guys but all our postes are deleted here. It seems something is going wrong. I am reposting that in a new thread.

Doesnt matters Why is the problem, leave this to apple, the fix is downgrade the kext wifi to snow leopard version.

And anywaty, "you cant make a car if the actual fuel will not work well... "

I reposted a comprehensive subject about how I solved my problem here:

https://discussions.apple.com/thread/4233962

I also sent a feedback directly to Apple. Hope they can fix it universally.

After having issues for weeks losing my connection sometimes several times an hour I CAN CONFIRM that after upgrading to 10.8.1 I've not had the issue even once in almost 24 hours.

Don

iMac Mid-2011

Had an old Linksys router, had the same problem, then it went away after I updated with a Mac Wifi update or something, I forgot, but last week I got a new Cisco EA4500 router which is meant to be pretty advanced, but I've found that the wifi has started to drop randomly every minute or so.

How can I fix this? 😢

I'm not saying this about you but to the posters that are telling every one to go out and buy the newest and best router. I've been replying back to them to stop telling people to go out and replace their Routers because they think it's an Apple conspiracy forcing us to upgrade. That's not the fix so don't waste your money on an fix that doesn't work.

I'm happy you posted that it didn't work so people will see. I'm not happy that you're still dropping wifi.

I don't know why you replaced your router and it doesn't matter. Just thanks for posting new routers aren't the answer.

I can confirm that I went from dropping wifi every 24-48 hours to 6 hours after I upgraded to 10.8.1. I've passed that onto Apple.

Is this fix (Snow Leopard) still working for everyone that tried it? Does any one know exactly what changes it is making? What's different from ML?

gsspike wrote:

I'm not saying this about you but to the posters that are telling every one to go out and buy the newest and best router. I've been replying back to them to stop telling people to go out and replace their Routers because they think it's an Apple conspiracy forcing us to upgrade. That's not the fix so don't waste your money on an fix that doesn't work.

I'm happy you posted that it didn't work so people will see. I'm not happy that you're still dropping wifi.

I don't know why you replaced your router and it doesn't matter. Just thanks for posting new routers aren't the answer.

What people are saying, is that new routers sometimes solve the problem. Most likely that happens because something changes in how they are using WiFi. The security mode, the channel, or even the location, relative to some other form of interferring signal.

What is really going on, is that people without the technical background to understand how all the pieces work, are trying one piece here or there, and not finding a solution. Instead, they should be working on understanding which part of the complex stack of technologies is failing, so that they can then be able to pin point how to solve the problem.

Getting people to talk openly in the formums is a rarity. The other night, I did successfully walk through helping "MacsSa" walk through steps to figure out that his ISP had a problem with DNS processing, or DHCP wasn't working to completely populate the needed information to make his network work.

That tedium is sometimes what is necessary. Not everyone is having the same problem, but it appears that some of the problems might, by accident, have a common solution.

If you want to really solve the problem, then you need to work on the problem resolution steps first. If you don't find the real problem, then a solution is going to be hard to find, without PURE luck.