Upgraded to 10.6.7 and wifi problem is back

1) if my "$1000" (and only it) is confused by my neighbours devices then the point is not to upgrade my neighbourhood

2) issues that magically happen after a software-upgrade are not the ones to get fixed by relacing hardware that run flawlessly since years (even if its ONLY $30 ) and still do with other devices .. additionally there are no official statements from Apple to this issue .. so replacing hardware is still a try - without garantee (what i would expect having a Apple-care for ) ..

3) misinformation here may happen because Apple-support cant give them proper support , else a solution would have spread already

4) i dont think that all thread-users here are totally dump noobs just because they have "0-points".. and just because this wierd situation didnt happen to you (yet?), doesnt mean everybody here is wrong (time will tell ) and they better reinstall their unix-system und change all surrounding hardware ( what a joke )

i would prefer staying on track finding a technical solution .. not some voodoo

trueshanti wrote:

1) if my "$1000" (and only it) is confused by my neighbours devices then the point is not to upgrade my neighbourhood

It is your router, not the computer. Your router only supports the older protocols. Your neighbors have probably gotten themselves similar junk routers over the past three years. There isn't enough bandwidth to go around anymore. There are enough free channels to support your older devices, but not your Macbook Pro. If you had an 802.11n, you would have a lot more channels to choose from with a lot less interferance, and better security.

2) issues that magically happen after a software-upgrade are not the ones to get fixed by relacing hardware that run flawlessly since years (even if its ONLY $30 ) and still do with other devices .. additionally there are no official statements from Apple to this issue .. so replacing hardware is still a try - without garantee (what i would expect having a Apple-care for ) ..

If you are convinced 10.6.7 is the cause, you can always roll back your system to an older version. There is no guarantee that it will ever be fixed. In fact, it is likely that it won't be fixed. Apple's priorities are supporting newer, faster protocols, not 8 year-old devices. Apple doesn't even support their own 8 year-old devices, let alone those from other companies.

3) misinformation here may happen because Apple-support cant give them proper support , else a solution would have spread already

A solution has spread - upgrade your router.

4) i dont think that all thread-users here are totally dump noobs just because they have "0-points".. and just because this wierd situation didnt happen to you (yet?), doesnt mean everybody here is wrong (time will tell ) and they better reinstall their unix-system und change all surrounding hardware ( what a joke )

I can assure you that point totals have no guaranteed correlation to expertise.

i would prefer staying on track finding a technical solution .. not some voodoo

You have two, but keep rejecting them. You can upgrade your router, which will certainly fix it, or downgrade your OS, which probably won't. You are free to try either, or just keep complaining about it. I am happy to help with technical solutions, but I don't care to read rants.

no rant was intended .. so sorry if came that way .. a appreciate your support-intentions ..

well opinions are many .. JUST had the effect with the dropping wireless-connection again ( while another wifi-laptop had uninterrupted download ) .. i had the nice effect to come back online by sending MB to sleep and wake up .. i read that people start having outages after waking up their device .. but vis versa i like :-) i hope this could be a hint .. so my router may be 802.1-g-type but as other devices handle it well at the same time .. i give 10 out of 10 to a software-issue on MB .. also because rebooting the router never changed anything at all.

I too was having internet dropout after upgrading to 10.6.7, and I think I've finally resolved it. For two weeks I tried all the troubleshooting tips I could find to no avail; very frustrating. In the end, the combo of resetting my router and creating a new wireless network did the trick for me. This could've been in combo with any number of other steps I tried before that, or it could've been just those. I'm not sure of the logic of why the old network would cause the drop with the MBP software upgrade to 10.6.7, but there it is. Some background:

- Airport Express router, up to date firmware.

- All other devices (another MBP, iPhones, and Xbox) continued to function fine on the wireless; just my MBP was dropping after the upgrade.

- Would drop after minutes or sometimes last a few hours, through sleep and wake.

- In addition to actual drops, overall page downloads (typically photos) were sometimes very slow. Sometimes they were regular speed.

- Turning airport off then on would usually connect me temporarily but then I'd get a drop.

- Manual IP would connect me temporarily but then I'd get a drop.

- Tried various DHCP settings. No luck.

- Tried switching wireless band, channels, password protocols. No luck.

- Tried resetting cable modem and soft reset of router to force new router IP from cable modem (but not new network at first.) No luck.

- Tried switching IP handouts of router from 10 series to 192 series. Seemed better at first but then dropped.

- Tried new user, deleting Airport protocol and adding anew, deleting old network location and all keychain access to old network and adding anew. No luck.

- Tried trashing several network/airport preferences mentioned in this string and others. No luck.

- Probably leaving out a few steps I tried.

Ultimately the reset of my router (using a paper clip to hold down the reset button - honestly cannot remember if I did this while powering up for a full factory restore) AND creating a new network worked for me. So far I've been operating 2 days without a drop. Fingers crossed my wireless continues to be solid.

Hope this helps someone.

I had to chime in here because etresoft is way out of line. For the record, I'm one of the many (apparently) affected by the 10.6.7 wifi bug. Yes, it's a 10.6.7 wifi bug. Not a router issue. Not a Mac issue. It's the 10.6.7. For sure. No ifs, ands, or bugs.

Now that the sentence fragments are out of the way, let me be more clear about my situation. Like everyone else, my router has been working perfectly for nearly a year. It is a dlink wireless N router that has been rock solid since it was taken out of the box. Every device, from my three week old Mac Pro Server, my Dell laptop, my Android phone, my PS3, my xBox, my eMac, my wife's netbook, and even my TV have connected with no instability whatsoever until installing 10.6.7 on the Mac Pro. The Mac Pro with the 10.6.7 update is the only device that has ever had connectivity issues with my router.

The first time this happened I was caught off guard, because the issue doesn't creep up right after applying the update. For whatever reason, and I think this is quite significant, the connectivity issue doesn't rear its ugly head until several days of use. I recently reinstalled OS X and all of my apps and had to manually reconfigure all of my server settings (I'm on Mac OS X Server, so believe me, this isn't something I looked forward to) but this time I made a carbon copy clone of the 10.6.4 installation. I re-applied the 10.6.7 update (for the same reason that others mentioned; the iApps ask for it) and at first all seemed well. About 20 minutes ago, however, the **** thing crapped out again, and upon looking for solutions to the issue, I was surprised to see that so many people were having the exact same problem. This is not something that should be quickly dismissed, and contrary to etresoft's inflamatory posts, it's not a matter of Apple "supporting 8 year old devices." This is clearly, without a doubt an issue with their own software update, not a hardware issue. Neither my router nor my Mac Pro Server are in need of repair. For now I've reverted back to my 10.6.4 installation, but I'm not very pleased by the lack of acknowledgment this issue has received. I should also mention that Bootcamp, like 10.6.4, works perfectly! As an enterprise customer, Apple will definitely be receiving a call tomorrow morning.

etresoft wrote:

The wireless circuity in that FRITZ!Box only supports 802.11g. That means it is ancient - up to 8 years old. Get yourself a decent 802.11n router and connect it via the LAN port. Your problems will likely go away. If not, see if you can get rid of the FRITZ!Box entirely.

Gosh, you are so condescending. No, maybe you're right, and maybe you're the only one out of hundreds of posts on the subject to know the truth behind this issue. It's definitely not the 10.6.7; it just so happens that at the exact same time (or as many have noted, some time after) installing the update, our routers have spontaneously become ancient and can no longer function. That, apparently, includes my <1 year old wireless N router which has run perfectly with every device, including the very Mac that now has connectivity issues. It's just one, big, widespread coincidence.

Hi all - I am just joining this conversation.

I recently upgraded to 10.6.7 on a 2010 Macbook Pro 17" that I normally use at work and my wifi stopped connecting at work.

If I bring home my laptop it connects fine to my home wifi network.

My iPhone connects fine to my work wifi network.

Other co-workers with 10.6.7 connect fine to the work wifi network.

Based on the suggestions in this thread I have tried

- Repairing my disk permissions

- Resetting my PRAM

- Reinstalling 10.6.7 combo update

None of these have worked.

Same problem here with 10.6.7 - that is - wifi issues.

So I walk into my neighborhood Panera Bread and fire up my shiny new macbook pro. Much to my dismay, the wifi connection that previously worked like a champ, will not work any longer. While my Windows PC brethren happily click away, here I sit with my thousand+ dollar investment - dead in the water. I love my mac and I like Apple. I am not bashing, but this is NOT a router problem perse. While the router is part of the equation, it's up to the smart people at Apple to make sure that my macbook, like a microwave oven or a toaster, does the same thing, every time - make great toast!

APPLE....HELP!!!!

Hi everyone,

I don't want to get your hopes up, but I MAY have found at least a temporary solution to this very annoying problem. It involves deleting a preference file and restarting, so it's worth a shot. I can't promise that it's a permanent fix since I've only just gotten my connection back up and running, but it is a start.

Simply go to your Library/Preferences/ folder and look for the com.apple.alf.plist and delete it by holding shift+apple+backspace. You may want to back up this file prior to deleting this, as this file is associate with your firewall. Any changes you made to your firewall will need to be reapplied, so keep that in mind. After deleting the file, simply restart and make sure your wifi settings are right. This worked for me after one restart, and I've now been running solid for about an hour. Again, I don't know if this will be a long term fix since the connection seems to fail after a few days of use, but at least it's a step in the right direction.

Please let me know if this has been of any help.

Unfortunately, @Veggiebacon, that did not work for me (delete com.apple.alf.plist). 😟

Did you restart after deleting the file? Did you renew the DHCP lease? Do you have it manually assigned to an IP?

The error I got after upgrading may have been different from yours. In my case, I kept getting a "self-assigned IP." No matter how many times I tried to renew the DHCP lease, or restart, it would not connect. Even assigning a manual IP would only allow me to connect to the router, but not to the internet. After deleting the file I mentioned, then turning off the firewall (I'm in OS X server 10.6.7 but you can turn off the firewall as well in the security tab), restarting, and renewing the DHCP lease, I was then able to connect. Please try that and let me know. My "solution" may only be for those experiencing the very specific version of the problem that I experienced.

I did reboot but my issue is actually connecting to the Wifi network in the first place. See below:

Well one thing that has kept bugging me using third party wireless routers was signal interference, let me explain. I live in an apartment build so separate people's wireless routers are in almost every apartment and I can see all those networks with OS X (and a program call iStumbler=http://www.istumbler.net/). So I changed my wireless channel to one that none of my neighbors were using and my wireless connections problem disappeared. However I know this will not be the problem for a lot of people in this thread.

To try a preference reset try these steps:

1. Turn off the Airport card by going to System Preferences->Network, highlight the AirPort card and turn if OFF! Don't skip this step!!!

2. Navigate to the folder /YourHardDrive/Library/Preferences/SystemConfiguration/ and find the files com.apple.airport.preferences.plist, NetworkInterfaces.plist, and preferences.plist, then drag them to the Trash Can (but don't delete them yet).

3. Reboot so OS X can rebuild those files you removed!

4. Upon the reboot first go into /Applications/Utilities/Keychain Access and delete any saved passwords for your wireless password.

5. Go to System Preferences->Network, highlight the AirPort card and turn the Airport card back on a rejoin your wireless network. You will have to re-put you wireless router password again but by this step you should be able to get back into your wireless router.

Lastly the application I mentioned earlier (http://www.istumbler.net) is free and is good to have to see all there wireless channels that are being used around your wireless network. This way you can avoid using the same wireless channel that others around you are already using.

Good luck.

P.S.: The folder for the Preference files are NOT in you Home Library, they are in the Main Library folder.

Sorry - no luck. Unfortunately I have no access to the router so I can't do anything to it to try to resolve this.