Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.6: A fix for failure to connect to new wireless networks Network
Snow Leopard only hintAfter upgrading from 10.5.8 to 10.6.1 on my MacBook Pro, I was unable to connect to wireless networks unless I had already connected to them running under 10.5.8. Snow Leopard would "see" the new networks, but could not connect to them.

The Genius Bar at the Apple Store helped me solve the problem. We opened Library » Preferences » SystemConfiguration, and trashed the entire contents of that folder. We also deleted all locations in System Preferences » Network, and recreated the location Automatic. Finally, we rebooted.

So far, I have been able to connect to all wireless networks that I want to using OS X 10.6.1.
    •    
  • Currently 2.47 / 5
  You rated: 4 / 5 (19 votes cast)
 
[16,593 views]  

10.6: A fix for failure to connect to new wireless networks | 5 comments | Create New Account
Click here to return to the '10.6: A fix for failure to connect to new wireless networks' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.6: A fix for failure to connect to new wireless networks
Authored by: jemuel85 on Nov 04, '09 09:12:35AM

What exactly happens when you trash the contents inside SystemConfiguration? I assume that things like smb servers list, preferences and everything else gets wiped out?



[ Reply to This | # ]
10.6: A fix for failure to connect to new wireless networks
Authored by: MtnBiker on Nov 04, '09 09:53:55AM

I've deleting files in this folder forever (at least a year through all updates) as my MacBook has problems with my home network. Not as much gets deleted as one would expect. Lately I've just been deleting com.apple.airport.preferences.plist.

You can of course backup your files and try it out. Create a .zip file or .dmg of the folder, delete and reboot (or turn Airport on and off). If you lose something you wanted, just replace the new files with the old ones. Keep the backup though as the files might get written too during the shutdown.

I started doing this based on something I found on the internet. Checked my notes, it's been over two years with different computers. Here's one of the recommendations:
===========
If you delete a few files in:

/Library/Preferences/SystemConfiguration/

NetworkInterfaces.plist, 

com.apple.network.identification.plist, and

preferences.plist

 - then on a reboot OS X will rescan your network ports and generally Do The Right Thing.
===========

from a comment here:

http://www.macosxhints.com/article.php?story=20080227061320185

I don't have the source for an earlier similar recommendation.

---
Hermosa Beach, CA USA



[ Reply to This | # ]
10.6: A fix for failure to connect to new wireless networks
Authored by: BiL Castine on Nov 05, '09 05:32:30AM
Deleting the network interface configuration files is standard procedure when moving a system image to dissimilar hardware, and is documented in Apple Training Series: Mac OS X Deployment v10.5. The files i always remove when creating a system image to deploy on multiple disimilar machines are
/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/com.apple.network.identification.plist /Library/Preferences/SystemConfiguration/preferences.plist
Use sudo to grant you the rights to delete these three files, then reboot. You'll need to rename your computer in the Sharing preference pane and any non-automatic settings needed for your network interface.

[ Reply to This | # ]
10.6: A fix for failure to connect to new wireless networks
Authored by: tatopuig on Nov 13, '09 08:05:11AM

I also found that creating a new "Location" under "Network Preferences" makes it possible to connect to new and old wireless networks without having to delete the system files and recreating the "Automatic" Location.



[ Reply to This | # ]
Adding new location worked
Authored by: alec kinnear on Jan 03, '12 01:50:19PM

Thanks for the tip, tatopuig.

That worked for me too (I had a new machine misidentifying Airport as USB and now it's considered Airport properly).

---
Moving the world to freedom, one Typepad weblog to Wordpress at a time.



[ Reply to This | # ]