Currently Being ModeratedAug 1, 2012 3:49 AM (in response to pcarlson)
I too have been having wifi issues after the upgrade last week. It would drop intermittently. The browser would fail on DNS lookups, and I couldn't ping my access point (Cisco WAP4410N). By accident, I was on facetime with someone when this happened BUT while I couldn't browse the web via neither Chrome nor Sarafi, the facetime connection didn't drop. So I ran nslookup and it worked for entries both fresh and cached by my DNS server. Weird. This means the network connection sort of worked and ML was selectively dropping stuff. Then suddenly, everything dropped after about 5 min.
After I read this post, I noticed my "preferred networks" under the wifi setup had "WPA/WPA2". So I went and changed my AP to only accept WAP2 instead of both WAP and WAP2 (mixed mode) since I couldn't configure the mid-2010 MBP to only use WAP2. Haven't had a drop since.
Note to Apple: QA'ing this systematically with automated tools is not easy, testing with multiple APs is even harder, but WiFi is increasing the only network connection we have - my wife's MacBookAir doesn't have a ethernet port.
Currently Being ModeratedAug 1, 2012 7:02 AM (in response to vmdude)
Thanks for that addition.
I was originally going to try the mixed WPA/WPA2 mode. Now I'm glad I didn't. The reason I didn't was because some of the suggested fixes were to take wifi off Automatic, i.e., create a new location, change the router from Auto to a fixed channel, preferably 1, 6 or 11 (I have it on 6), set a fixed DNS address, etc.. So I decided, in changing to WPA alone, to have everything fixed, not in auto mode, so that, hopefully, the Mac wouldn't constantly be searching for the link.
Currently Being ModeratedAug 1, 2012 8:32 AM (in response to pcarlson)
I actually did try changing the auto channel to fixed and vice versa and that didn't help. I also tried turning off IPv6 and that didn't do the trick either (under the assumption that it was self assigning an IP address and sending stuff out the v6 stack - something my router doesn't understand).
What I did notice after I changed from mixed mode to WPA2 only was that my connection worked a LOT faster. I can't imagine the WPA key was renegotiated for every fwe packets so I can't figure out why.
What I did forget to mention is that I had to delete the wifi network profile on the Mac and recreate it so it only says WAP2.
I also have to admit that I was perhaps a bit fast on the trigger. The problem has returned since my last post. It does work really well when it works, but when it doesn't........ I will let you know if I find anything else.
Currently Being ModeratedAug 1, 2012 11:07 AM (in response to vmdude)
My connection is also a lot faster, and we haven't had a dropped connection in 2 days now. I am using an assigned channel on the router. I chose 6 as the channel. I think I left the IPv6 alone, since it seemed to make no difference if I set it locally. And I also deleted my network profile and recreated it.
Since so many people are having this issue, I hope Apple addresses it. Apparently, the problem has been ongoing for a few years now, only made much worse by Mountain Lion.
Currently Being ModeratedAug 1, 2012 9:13 PM (in response to pcarlson)
My wifi connection was also dropping every few minutes. I could expidate the drops by streaming a couple videos at the same time. Snow Leopards wifi was never perfect for me either (it would drop about once a week) but it was stable. Upgrading to ML made it so much worse.
I had found a solution that made it completely stable (see below) but still looked for a proper fix:
Enable WLAN: Yes
Mode: IEEE 802.11g Only
Transmitting power: 100%
Enable WMM QoS: No
Not having EXACTLY this brought the problem back.
Finally, after already checking if there was a firmware update for my router by going into its configuration and it telling me it was up to date, i wondered if my router was wrong. Sure enough i went to the dlink website (i have a dlink dir-615) i found a new firmware version had been available for the past 2 years.
After updating the routers firmware my wifi is running so so smooth with whatever settings i choose.
Hope this helps!
Currently Being ModeratedAug 4, 2012 9:22 AM (in response to biochemgineer)
I took the cue and upgraded the firmware in my cisco WAP 4410N from 220.127.116.11 to 18.104.22.168. All the issues went away and it's been stable for almost 3 days now. I was a bit too fast on the trigger for the last post so I waited a bit. I have now done everything from copying a 2 gig file to doing a full time machine backup (60GB) over wifi. I think it's safe to say it's fixed now.
Cisco WAP 4410N has the following config:
- 802.11N only
- Auto channel selection
- firmware version: 22.214.171.124
- No vlan
- No QoS
- WAP2-personal only
- wireless isolation disabled
- auto chanel bandwidth, guard interval, and GTS
Currently Being ModeratedAug 25, 2012 4:19 PM (in response to wifiguru)
Netgear RangeMax - not sure of the model any longer and would have to unplug it to find out. It is about 3 to 4 years old, and I also did a firmware update, which probably helped as well. It is Apple Support that told me I could use WEP, but the Mac would continue to drop the wifi connection if I did, and the change to WPA was fairly painless.
Currently Being ModeratedSep 20, 2012 7:55 AM (in response to wifiguru)
Hey everyone. Unfortunately, at work, I don't have access to our router (nor would I know what to do once accessing it!). There's someone coming in tonight familiar with networking/wireless that might know what to do. My boss seems to have thrown his arms up in the air
Our router is a Cisco WAP4410N, hooked up to a whatever the newest Comcast business modem is.
My coworker thinks our firmware might need to be updated - so we'll see if we can get that handled tonight.
Forgetting all this - shouldn't WiFi work without having to upgrade or mess with our router?
Currently Being ModeratedNov 3, 2012 3:10 AM (in response to pcarlson)
Spoke with Apple Care who fixed my intermittent network connection issues after having upgraded to Mountain Lion:
This is what he asked me to do:
1. Go to your Macintosh HD drive in Finder (system drive)
2. Go to Library
3. Drag the 'SystemConfiguration' Folder onto the Desktop (creates a BU copy - just in case)
4. Delete the 'System Configuration' Folder within the 'Library Folder' (empty the Trash Bin - just in case)
5. Reboot - This recreates the network files (automatically)
6. That's it!
Works now like a charm
P.S.: Just in case if you have done custom network configurations, write them down first.
PPS: I did the above and it works, but please don't hold me liable for anything you do on your own machine : )
Currently Being ModeratedNov 8, 2012 10:47 AM (in response to daveglanz)
@daveglanz: After deleting the folder, I do not have it any longer either (it may have been a redundant folder from my SnowLeopard->Lion->Mountain Lion upgrade. But my network is super stable now. Sorry to hear it did not work for you.