Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My MacBook won't connect to the Internet via my home wireless network that was working just a minute ago. All the other devices connected to the network went back to normal after the AirPort Express was re-started, except for my MacBook. The MacBook's AirPort card is working, hence me being able to join a public network and post this.

Before I call the cable company, I wanted to ask the knowledgeable sysadmins here, how would you go about trying to fix a problem like this? If this had happened at your home, what steps would you take to identify and solve the problem?

Can you suggest any tools, or anything that can help me understand what's happening so I can hopefully fix this myself.

I feel very stupid calling the cable company :). It takes forever, and they are going to tell me to re-start everything (which I already did). There has gotta be a better way.

share|improve this question

migrated from May 16 '11 at 2:44

This question came from our site for system and network administrators.

I'd restart the MacBook and see if that helps as the first step. – boehj May 16 '11 at 2:27
up vote 2 down vote accepted

On my AirPort Express:

If I had another Mac or Windows PC that was able to connect, I'd run the AirPort Utility on that machine to check the AirPort Express's settings.

If I didn't have a way to get back in, I'd hit the paperclip reset button briefly to do a "soft reset" -- this just makes the network visible and security-free for a short time, so you can get wirelessly associated again if you'd forgotten your network name or password.

I'd choose to manually set the channel, and pick one that seems clean (based on using a tool like iStumbler to see what networks I can see around me are on what channels). I'd probably pick a 2.4GHz channel (1-11 or 1-13) because I'd probably have some 2.4GHz-only devices around like iPhones.

I would double-check what wireless security type and password it was using, so that I can enter it correctly on my MacBook if need be.

I would disable the "Closed Network" (hidden network) feature of the base station, because it doesn't really offer much security, and just makes the network harder to get reconnected to when things go wrong.

I would disable any MAC-address based Access Control Lists (ACLs). I think they may call it "Timed Access" now. This doesn't offer much security either, and again mostly causes hassles.

I would make sure I have up to date firmware on the AirPort Express. There have been two versions of AirPort Express: the current one that can do 802.11n, for which the latest firmware is 7.5.2, and the older one that only does 802.11g and earlier, for which the latest firmware is 6.3.

If I were still running the older AirPort Express that can't do 802.11n, I'd go buy a new one. The older b/g model, which was introduced in 2004 is showing its age at this point. Connecting modern 802.11 clients to the older Express seems to cause it to become unstable.

On my MacBook:

I would run the Software Updates tool on my MacBook to make sure I have all the latest software updates on my MacBook as well.

I would go into "Utilities > Keychain Access" and search my keychains for any entries concerning the problem network, and delete them (they'll automatically get re-created later when I'm able to successfully join the network).

I would go into "System Preferences > Network > AirPort > Advanced > AirPort" and edit my Preferred Networks list, deleting any entries I don't honestly need anymore, and delete the entry for the problem network. (I'd let that entry get auto-recreated the next time I'm able to successfully join that network.)

I would go into "System Preferences > Network > AirPort > Advanced > TCP/IP" and make sure I had that set correctly (which probably means making sure it's set to get its address from DHCP).

share|improve this answer
Thank you Spiff. I had done a few of those steps before. I ended up using a different mac book to reset the airport extreme to the factory settings, created the network again, restarted all the devices, and did a software update on my mac book (the problematic one from the beginning). It's all working now. I don't know exactly what the problem was, which is bad. – deb May 16 '11 at 13:49

I got a bit lost reading your explanation. I suggest that you troubleshoot this problem in layers. Can you ping your default gateway? Other hosts on your LAN? What about a peer on the other side? Is name resolution (DNS) working properly?

share|improve this answer
I do suggest that you reboot your MacBook though. – SpacemanSpiff May 16 '11 at 1:48

How many other devices are WLAN connected using the same password? I find each WLAN device cannot use the same password at the same time. Device = smartphone, TV, games console, neighbour using your bandwidth, another computer, etc.

share|improve this answer
WPA Personal (a.k.a. WPA-PSK) and WPA2 Personal (a.k.a. WPA2-PSK) were designed for every machine to use the same password. Even the way Apple products do WEP only allow a single key for the whole network. – Spiff May 16 '11 at 4:49
Hey @user37991, thanks for the post but it comes across more like a question than an answer. Maybe add it as a comment next time. – slotishtype Aug 5 '11 at 11:04

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .