You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

A connection timeout occurred 802.11n

I just upgraded my i7 MBP to Lion. I connect to an Airport Express running in dual mode. I can connect to 802.11g but I get this error when I try to connect to the 802.11 5ghz side.


Failed to join "network"

A connection timeout occured


I have rebooted the Mac and the Airport Express. No luck.

MacBook Pro, Mac OS X (10.7)

Posted on Jul 20, 2011 9:03 PM

Reply
140 replies

Jul 29, 2011 7:50 AM in response to SCCThreeIII

I've been working with an engineer from Apple. Basically my mac air thinks my N network is broadcasting the wrong country code, causing the Mac to not see it. But my router is hard coded to North America.


"This basically means your client is seeing an Access Point with Taiwan Country code and setting its regulatory standards and power levels to this zone's settings. This can cause the issue where it won't see certain channel's and or not connect in certain mode's. If you send me your System Information report I can see a little more information."


In my System Info report you can see that I have a TW country code. At least we know why I can't connect to N. Now have to wait for the fix.

Jul 29, 2011 9:01 PM in response to rjvaughn

If you can connect to G but not N, check your SystemInfo=>Network=>WiFi settings, and see if your country code is Taiwan. That appears to be my problem. Now trying to figure out why.



Interfaces:

en0:

Card Type: AirPort Extreme (0x14E4, 0xD1)

Firmware Version: Broadcom BCM43xx 1.0 (5.100.98.75.6)

MAC Address: 58:55:ca:f7:36:23

Locale: FCC

Country Code: TW

Supported PHY Modes: 802.11 a/b/g/n

Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153, 157, 161, 165

Wake On Wireless: Supported

AirDrop: Supported

Status: Connected

Current Network Information:

ronopolis:

PHY Mode: 802.11g

BSSID: e0:91:f5:05:1d:7e

Channel: 6

Country Code: TW

Network Type: Infrastructure

Security: WPA2 Personal

Signal / Noise: -47 dBm / -90 dBm

Transmit Rate: 54

Aug 6, 2011 6:45 PM in response to SCCThreeIII

Well, I think I figured it out, but it's not going to help us.


The issue here is that if you change the key, for some irritating reason Lion won't ask you to input the new one, and even if you delete the WiFi reference it's still somewhere in there.


I deleted the network, shut down WiFi, and rebooted the machine. When it came back up it timed out the connection. When I changed the WPA2 phrase back to the original (on the router), my MB connected to the new network, without asking me for the phrase -- it remembered, even though it should've dumped it along with the rest of the WiFi spot's data...

Aug 13, 2011 10:40 PM in response to SCCThreeIII

Hmmm... maybe a fix here. Got this from MacWorld:

____________________________________________________

Although not likely, you may lose your Internet connection after an otherwise successful install of Lion. If you use Avast’s Web Shield, the solution is to uninstall avast!. There is a known conflict between Avast and Lion. As posted in an Avast forum thread, a supposed bug-fix update, still in beta, is available. In this same thread, the company lays the blame on Apple: “Packet forwarding is broken on Lion. Lion either does not redirect the packets (your case) or crashes. This bugs have been reported to Apple long time before the Lion release, but it is still not fixed by Apple.”


If you don’t use Avast, a more general potential fix is to turn off the Mac OS X Lion Firewall (in Security & Privacy System Preferences), and delete the firewall-related com.apple.alf.plist file in /Library/Preferences (via Terminal if needed). After a restart, you can re-enable the Firewall.

____________________________________________________



I don't use Avast, so I did part two there (deleted the firewall rules). Easy for me, since my firewall rule is: block everything. I also did it through the command line (I'm one of those Unix/Linux guys 😎).


Unfortunately, since this happened at my friend's house, I haven't been able to test the fix yet.

A connection timeout occurred 802.11n

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.