- Many users had reported in forums that WPA2 was not "per se" resolving the issue: it is probably a reminiscent set of parameters that were reset as a side effect of your upgrade.

- Moreover, it is very difficult to admit that my iMAC would not support WEP "de facto": upgrading to WA2 would mean in my case to throw to the bin at least three of my 16 devices (an ipcam, a Hifi extender to stream music, an old win98 PC)

- My mine deception is that by moving to a "one supplier for all stack" paradigm such as Apple, I didn't solve my "father=home system manager" issue to handle the park of machines a home.... :( Back to PCs at the end? Very very disappointed in any case.

Well, I may have fixed my problem. I have gone 48 hours without a failure. It looks a like a software incompatibility issue. Since the menu bar froze when Wifi failed. I started there. I looked at two things in particular: growl and transmit (an ftp client). For me, it looks Transmit was the culprit. Although some think it is actually an interaction between growl and transmit. I have deleted it and the other Panic application I use, Coda 2. Problems (cross fingers) seem to be gone.

I believe there are multiple problems with the wifi communication stack on Mountain Lion. If your problems sound like mine, start with growl because it does notifications which is a new feature of Mountain Lion. If you have the 1.2.2 version, you will see it in the bottom row of your system preferences. There is an application tab that will tell you the programs it interfaces with (Adobe Updater, Dropbox, Evernote, Cyberduck, Coda, Transmit, and Firefox for me). Turn it off. You will need to do so on several tabs. See if you see an improvement. Mine was dramatic. I did a little more research and found that Transmit, while technically compatiable with Mountain Lion, had issues with growl. As I said, I deleted it and its sibling. I also updated growl to the 1.4 version. I have gradually turned the remaining programs back on and have had no problems. If you don't have a known bad actor like transmit, you'll have to do it until you find the problem child.

After reading Kekernan's post I turned off Growl (and Hiss, which is a helper app that puts Growl notifications in the ML notification center) and I've had my first full day since I upgraded to ML without a wifi disconnect!

I'm quite disappointed in Apple. I bought a brand new MacBook Pro last weekend, and I'm also having this issue with no fix in sight. The wifi drops after a few minutes, and I have to turn it off and back on to get it working for another couple of minutes. I performed the latest software update, I tried all the fixes I could find, and nothing is solving this issue. I can't go back to Lion, and I can't do anything on my router because I don't have access to it.

The only thing that does work? Installing Windows 7 and using that. Come on, Apple. This is no minor issue.

I have tried every suggested fix to no avail and my wireless connection will drop every time my Mac sleeps and when woken I always have to wait and enter my closed network manually which is highly annoying.

To others out there with the same problem don't rely on help from Apple telephone support as they seem to be a clueless bunch these days with very limited technical expertise.

Come on Apple get it together and own up officially to this major flaw and get it fixed pronto!

Hi Neale121, I am fully inline with you: this is ML sw issue, n doubt. his given said, there is no much chance to get it solve by complaining I te forums. I am quite surprised by the extended time the Engineers of apple are actuall tring to help over the AppleCare phone lines ...but they apparently are 100% disconnected from Apple forums that are getting that reputation of "complaining place only".

The main issue is that AppleCare is moving to denial mode and just tell customers "WEP is finished for OS X, move to WPA". I have a difficulty to admit this and to throw to the bing quite a flew devices that are WEP-dependent., ,

I am currentely doing a new attempt by fixe DHCP address and move away from DHCP.

Related Articles

This site contains user submitted content, comments and opinions and is for informational purposes only.
Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums.
Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.