My MBP doesn't connect to 802.11n networks

Software Versions:
Menu Extra: 6.2 (620.24)
configd plug-in: 6.2 (620.15.1)
System Profiler: 6.0 (600.9)
Network Preference: 6.2 (620.24)
AirPort Utility: 5.4.2 (542.23)
IO80211 Family: 3.1 (310.6)
Interfaces:
en1:
Card Type: AirPort Extreme
Firmware Version: Atheros 5416: 2.0.19.8
Locale: Korea
Country Code: KR
Supported PHY Modes: 802.11 a/b/g
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 149, 153, 157, 161
Status: Connected
Current Network Information:
SSD87:
PHY Mode: 802.11g
BSSID: 0:25:bc:8a:3f:51
Channel: 11
Network Type: Infrastructure
Security: WPA2 Personal
Signal / Noise: -58 dBm / -96 dBm
Transmit Rate: 54
Other Local Wireless Networks:
SSD875G:
PHY Mode: 802.11n
BSSID: 0:25:bc:8a:3f:52
Channel: 157
Network Type: Infrastructure
Security: WPA2 Personal
Signal / Noise: -55 dBm / -96 dBm
SSD875G:
PHY Mode: 802.11n
BSSID: 0:1f:5b:86:e9:74
Channel: 157
Network Type: Infrastructure
Security: WPA2 Personal
Signal / Noise: -58 dBm / -96 dBm
==============================================
From the information above, my MBP doesn't access 802.11n network after install Mac OS X 10.6 Snow Leopard and all of updates.
Snow Leopard changes Phy mode of 'Atheros 802.11n WL card' to 802.11g, and It works fine as 11n under 10.5.8 Leopard.
What makes this situation?
Message was edited by: xeon.thebrick

defecta wrote:
So by the virtue of my MacBook being compliant with the 802.11d standard I am open to these issues? And from the way you are explaining it it sounds like Apple is ahead of the curve with implementing 802.11d compliance?
They're not ahead of the curve +per se+, but as an example many Windows XP machines are behind the curve if you will.
Would it be legal to write an app or driver that you can set ignore certain problem country codes when you want it to? Because something like this would help my issue also rather than playing lotto each time I turn my MacBook on or wake it from sleep, hoping it will see my wireless network first.
Unfortunately, I'm not a lawyer and not in Australia so I couldn't begin to guess at what is legal and what's not in this arena.
However, there is no interface to the driver to be able to manually set a country code, so the point may be moot.
I don't know what kisMAC can and cannot display, but the country code is broadcast within the 802.11 beacon frame and/or probe response frame if the frame's dot11MultiDomainCapabilityEnabled option is true, so you may want to try looking at its output of beacon frames.
Three octets make up the country code - the two character country code and a third octet which is one of:
    * An ASCII space character (0x20) if the regulations under which the 802.11 station is operating encompass all environments in the country.
    * An ASCII ‘O’ character (0x4F) if the regulations under which the 802.11 station is operating are for an outdoor environment only.
    * An ASCII ‘I’ character (0x49) if the regulations under which the 802.11 station is operating are for an indoor environment only.
The way the 802.11d standard specifies this all works is:
9.9.1 Operation upon entering a regulatory domain
A STA that is enabled for operation across regulatory domains shall default to passive scanning when it has lost connectivity with its ESS. Passive scanning is performed using only the receive capabilities of the station and is, thus, compatible with regulatory requirements. The timeout for determining the loss of connectivity is system dependent and beyond the scope of this standard.
When a STA enters a regulatory domain, it shall passively scan to learn at least one valid channel, i.e., a channel upon which it detects IEEE Std 802.11 frames. The Beacon frame contains information on the country code, the maximum allowable transmit power, and the channels to be used for the regulatory domain. Optionally, the Beacon frame may also include, on a periodic basis, the regulatory information that would be returned in a Probe Response frame. Once the STA has acquired the information so that it is able to meet the transmit requirements of the regulatory domain, it shall transmit a Probe Request to an AP to gain the additional regulatory domain information contained in the Probe Response frame, unless the information was previously received in a Beacon fame. The STA then has sufficient information available to configure its PHY for operation in the regulatory domain.
http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=946610&userType=inst
Note that this spec dates to 2001, so it's hardly something "new," just something that wasn't necessarily widely supported.

Similar Messages

Macbook Pro with Vista does NOT connect to 802.11n

I have a Macbook Pro running Vista and a wifi Linksys WRT350 access point/router, which does 802.11b/g/n. The Macbook Pro only connect to the access point at 802.11g 54Mbps the access point is set to mix-mode. If I set the access point to only 802.11n, the Macbook Pro cannot connect to the access point. If I use bootcamp to load the Mac OS X, the Mac OS X is able to connect to 802.11n. The signal level is pretty good on Vista ad Mac OS X.
Any ideas?

Usually when connecting a camera only the SD card is mounted, so it is normal to see only the SD card mounted on the Desktop. The camera is not actually the device, rather the SD card (and interface) is. Apparently System Information does report correctly on the camera itself.
Be sure to check at Epson's support site for an updated driver compatible with Lion. You can also download the latest drivers package from Apple: Epson Printer Drivers v2.9 OS X.
Of importance is if the scanner is working. If it is working, then it really doesn't matter, except cosmetically, that the device is reported as a printer. You can report that to Apple via Apple Feedback.

New Macbook Air will not connect to 802.11n, but my old 2011 model will

I have just bought a new MBA 13", i7, 8 GB RAM, 256 GB SSD.
When I connect to my home network I see it as a 802.11n network, but as soon as I log on, I only have 802.11g connection. I still have my old 2011 MBA, and it connects to the n-standard just fine.
I went to the local Apple reseller to have them look at it, but the problem was not present when connecting to their airport extremes.
Has anyone else had this kind of problem, and is there a known fix?
Casper

The warranty entitles you to complimentary phone support for the first 90 days of ownership. If you bought the product in the U.S. directly from Apple (not from a reseller), you also have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different.

Broadcom 802.11n Network Adapter not working on Windows 7 64bit

As the title suggests, my laptop (Alienware m17x) is installed with the Broadcom 802.11n Network Adapter and Windows 7 64bit Home Premium. I have had several other driver incompatibility issues with Windows 7, but those I have slowly been able to resolve. This however just cropped up after two months of successful use. Yesterday it started failing to connect to the internet, telling me that no wireless connections are available. I live in a dorm, and everyone else on my floor has successful wireless, including my Ipod Touch, PS3 and XBox 360. I called Alienware/Dell Support and we spent hours trying to fix the problem and all look well until I rebooted my laptop this morning and the same issue reappeared. When I reboot my laptop, all I get is a notification that no networks appear in range. If I uninstall the broadcom chip and let windows install it after a boot up it works until the machine is rebooted a second time. I have tried over a dozen windows 7 drivers for the chip, and about half a dozen vista drivers and they all have the same results, works on the first boot, fails every time after that

Just registered to say, on an Alienware M17x system as well running Windows 7 Ultimate, here is a link to a solution that worked exactly for me:
http://forum.notebookreview.com/alienware/436486-guide-properly-solve-wireless-connection-problems-m17x.html
All I did was section I.a. If the link is down, I copied the only section that I needed to follow out of this guide, in order to get my wireless to work repeatedly without having to uninstall the wireless driver every single reboot. Now it works perfectly,
already connected to a wireless network on startup.
I.a. Disable Device sleep on disconnect
Some newer Nvidia Ethernet drivers have a feature called Device sleep on disconnect. This is the culprit. Normally, it should only put the Ethernet adapter to sleep when the cable is disconnected, but it's buggy and thus kills the wireless connection as
well.
Follow these steps to disable this feature on your Nvidia Ethernet Adapter:
1. Open the Windows Device Manager by hitting Win+Pause, then click on Device Manager on the left side.
2. Double-click on Network adapters.
3. Double-click on NVIDIA nForce Networking Controller (yes, that's the wired Ethernet adapter indeed).
4. Click on the Advanced tab.
5. Select Device sleep on disconnect.
6. Set the Value to Disabled.
7. Click OK and wireless should work again (might require a reboot afterwards, but probably not).

Iwlwifi does not detect present 802.11n networks

I just got a new laptop, and the iwlwifi driver it's using is not detecting 802.11n networks that I know are there. My old laptop, which is also using the iwlwifi driver, is currently connected to that network less then 2 feet away. The old laptop has kernel 3.4.4, whereas the new one has kernel 3.4.7. Is that the problem, or is it the card?
New laptop:
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 2200 (rev c4)
iwconfig wlan0 says "IEEE 802.11bgn"
Old laptop:
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
Last edited by Daenyth (2012-08-08 19:35:17)

Gusar wrote:
.:B:. wrote:You're reading things that are not there mate. 802.11n is both a 5 GHz and a 2,4 GHz standard. The old IPW 2200 only does 802.11bg. Had one myself.
I know that. Are you saying the new 2200 only does N at 2.4GHz?
Oh, and I not only had an IPW 2200, I still have it! . Actually, I have an IPW 2915, which also does 802.11a in addition to 802.11bg. It uses the same ipw2200 driver though.
Edit: Did a bit of googling, the new 2200 indeed only does N at 2.4GHz. Let me just say that this is totally and completely insane. It's so insane I couldn't imagine such a thing could even exist.
It's a billion dollar company. What do you expect? I found out yesterday Microsoft actually has a 16 GB memory limit on Windows 7 Home Premium. You need a Pro version to use more. There I was, telling my friend to get 32 GB for his video editing rig.
As for daenyth's card, convention has it that bgn is 2,4 GHz only. An a(b)gn card can do both 2,4 GHz and 5 GHz. You don't need to check specs for that. It's sad indeed, but there are still plenty 2,4 GHz-only 802.11n cards around. This new laptop I got a few months back came with one, and that wasn't a 300 EUR netbook.
Last edited by .:B:. (2012-08-09 11:48:55)

Wireless Music and Surfing on Express via a 802.11n network

Hello.
Just a quick query I hope. I am setting up a 802.11n network but i would still like to stream music from my mac to my hi-fi. As i understand it the two specifications (g and n) are compatible, however I would still like the benefit of the 802.11n network, as such i would use a dedicated 'n' router for the network and just have the express base connected to the stereo.
If i set-up my Express base station, would this comprise speeds for internet surfing, file sharing, and reliability / performance? Or would it simply use the 'n' router network for the net but iTunes would pickup the express base-station for music?
All advice welcome, regards, Jim.

I suggest, if practical, to set up a "dual band" network with your new 802.11n AirPort Extreme Base Station (AEBSn) and the AirPort Express Base Station (AX) to take advantage of their features.
Setting up a "dual band" network is described in the Designing AirPort Networks Using the AirPort Utility document, starting on page 48.

MBP APE can not connect to 802.11n only 5GHz

I purchased a 17" MBP about a month ago and then got the APE two weeks ago.
I am running DSL to a Linksys (not WiFi) router. I attached the APE to the Linksys and created a network using 'Bridge'. Everything worked great. During setup I tested 802.11n (b/g compatible) and 802.11n only 5GHz, but left it at b/g compatible. Airport Utility is on my G5 dual 1.8 which is hard wired to my Linksys.
A week ago I lost the connection from my MBP to the APE. I unplugged the APE for a minute and then plugged it back in. I got my connection back. This has happened only once.
A few days ago I applied the APE update to my MBP and everything seemed okay.
Today I tried switching from b/g compatible to n only (5 GHz). When I choose n only from Airport Utility my MBP can no longer see my APE network (this did work before).
I did a restart, Repaired Permissions and I also unplugged the APE. No joy.
Everything is fine with b/g compatible but n only does not work.
Any ideas?
Thanks,
--ken

Yes, I did run the n enabler when I first set up my MBP and I was able to connect as n only for several weeks. Then two things happened, I lost connectivity which unplugging the APE fixed and a few days later I ran the APE for Intel update.
Thanks,
--ken

Wont connect using 802.11N

My imac can see the name of the network but refuses to connect to it using 802.11N. Its really odd because my Apple TV has no problem connecting to the router using 802.11N

I have the exact same problem but haven't been able to figure it out. My problem is that my C2D iMac 24 (white) will see 802.11n only network, but will not attach to it. Monitoring the network attachment process on Network Utility shows a few seconds of trying, then eventually gives me a small "instruction" saying "See Administrator". That's not so helpful.
If you were having the same problem and had figured it out, I'd love to hear it.
My wireless AP has no WEP or any Mac filtering enabled.

Connecting an 802.11n Express to an older WEP-enabled WDS network

I have a domed 802.11g Extreme base station connected to an older (802.11g) Express in a 128-bit WEP enabled WDS network - works great.
I recently purchased a new 802.11n Express and would like to add it as another remote in my WDS. The new Airport Setup Utility will not allow me to set up the new Express as a remote in a WDS network with 128-bit WEP. The closest I can get is WEP Transitional Security Network. When setting it up this way, it demanded a 13-character password -- which I dutifully supplied AFTER changing the password on my domed Extreme to the same thing. After all this effort - the new Express won't get past the blinking yellow light thus requiring me to reset it using the manual reset button.
I can get this same unit to "join" my existing network just fine. In that case, it accepts 128-bit WEP without a whimper.
Is there a basic compatibility problem here? Can I get the new unit to connect to the old 128-bit WEP network by using Transitional Security Network? Do I need to update the whole network to WPA? Or is there some other issue here that has nothing to do with the security issue?
Thanks for any help.

Hello Tim Hopmann. Welcome to the Apple Discussions!
You should be able to access the "earlier" WEP modes by first changing the radio mode on the 802.11n AirPort Express Base Station (AXn) to one of the non-"n" modes. To do so, just be sure to hold down the <Option> key before making the radio mode selection in the AirPort Utility. Once you choose one of these non-"n" modes, the WEP 40 & 128-bit options become available.

MBP and Netgear RangeMax NEXT (802.11n)

Hi,
Does anyone know if MBP works with RangeMax 802.11n? I am thinking about getting one of these but wondering the compatibility issue.
15.3" MacBook Pro 2.33GHz Core2Duo & 20" iMac 2GHz Intel Core Duo 2GB RAM Mac OS X (10.4.7) 30GB iPod, BlackBerry 8700g and can't ask for more!!!

I have a friend who uses one of the RangeMax 802.11g models with no problems. They do list Mac OS among the system requirements for both. I also understand from reviews that the interface has changed very little. I would say that bodes well for the 802.11n model working with the Mac as well as the 802.11g did.
I have never been impressed with Netgear using any wireless cards than their own though. As I understand it top speeds can only be achieved using their wireless card. I have also found range to only be acceptable (despite the RangeMAX name) with Netgear routers, never great.
YMMV. Those have just been my experiences with them.

Connecting AX (802.11n) and AX (802.11g) to create WDS

Hello I'm currently trying to connect my new Airport Extreme (802.11n) to my old Airport (802.11g)
in the aim of extending my network. So I would like to have the 11n as my main.
and 11g as a remote I think?
can anybody give me a step by step on how I would go about this on Airport Utility?
I think my main problem is that my old Airport is connected to a different network.
Kyle

You would need to configure the 802.11n AirPort Extreme base station (AEBS) to operate in an 802.11g compatible mode. You would need to configure one AEBS to operate as a WDS main. You would need to configure the other AEBS to operate as a WDS remote (or relay). An Unfortunate side effect of WDS is that each link cuts your available wireless bandwidth in half. Therefore the maximum wireless bandwidth achievable is 1/2 the 802.11g rate.

Why doesn't the AEBS 802.11n support NTFS?

I am wondering why users need to go through hoops to make the $200 AEBS 802.11n recognize NTFS formatted disks. Is it really that complicated for Apple engineers to add this support? Is there any way to reach Apple tech and request this? Or is asking for NTFS support utterly ludicrous and fundamentally not feasible. If it is futile to hope for Apple to add support for NTFS to the AEBS 802.11n, then how does one go about returning - who to contact to return and get the money refunded.

Hello durlov. Welcome to the Apple Discussions!
... how does one go about returning - who to contact to return and get the money refunded.
Here is Apple's Return and Refund Policy.

Can't join "802.11n only 5Ghz" but can connect to "802.11n only 2.4 GHz"

Using an airport extreme and two MacBook C2D's, I'd like to have the airport create an "802.11n only 5 GHz" network using WPA2 Personal security. For some reason, I can create an 802.11n only 2.4 GHz network and join it, but am unable to join the exact same network using 5 GHz.
Can anyone help me solve this?
I live in an urban environment with TONS of competing networks / microwaves / sonos / cell phones / cordless phones ... on the 2.4Ghz bandwidth and want to use 5 Ghz. What could be causing this problem?

Me reporting back again - I may have narrowed down the problem, on my system at least. I bought a new Airport express with 802.11n capability and I set it up as a separate network to my stereo, broadcasting at 5GHz. It worked fine, and in fact it eliminated the interference problem I was having. Since my computer manages at 5 GHz, as well as the new Airport Express, it means that the problems I have been having broadcasting at 5GHz originate from the Airport Extreme base station. Could be that others are having that problem as well? I'm only sorry that the base station is beyond the warranty period, so I can't return it.

Connecting AEBS 802.11n to netgearNB5Plus4w modem/router

Hi
Can anyone help me with this. Im trying to connect my whole wireless network (xp, ps3, wii, pda, macbook) through the base station because the range on my netgear is **. But im having trouble with the configuration part. Im not sure how its meant to be set up between the netgear>AEBS>Macbook. ie things lke static or dynamic ip, bridge, filters etc... Especially in the netgaer settings.
Any help would be greatly appreciated.
ps Makes it even harder when the sales asistant told me my AEBS replaces the netgear, which i found out when i got home that thats not how this thing works!

Dont apoligise mate!
The netgear is a modem/router. i did fix the probem to a degree. When i set it up i had the plugs in the wrong order and went through the set up process with difficulty. But since rebooting the aebs and going through the airport utility again it set up perfeclty under bridge mode. I DO LOVE MAC! easy set up!
However the essence of my original problem remains. Is their a good 'SET UP' for security or whatever for my netgear - airport extreme base station - macbook? ie things like firewall (because now i have two - netgear and macbook), bridging, static ip addressess or dynamic etc. its all working but im just looking for a GOOD SET UP idea. Im not that tech savvy to do this myself.
Any help would be great thanks

Airport Drives Me CRAZY! New 802.11n Network Slower Than Old 802.11g/b

I've been using Macs since 1988 and consider myself an advanced user. However, every time I setup a new Airport wireless network or re-configure an existing one, I feel like a helpless newbie trying to figure out how to open a folder on my desktop. No matter how many times I read the manual or the help files or these forums, I can never grasp what seems like it should be a simple path from A to B to C.
Anyway, here's my current situation: I've been successfully (I think) running a 6 year old AP Extreme Base Station [AE] (in my home office addition) and 2 Airport Expresses [AX] (one AX roughly 15 feet from the base station--through sheetrock, and the second AX roughly 30 feet from the first AX--through sheetrock and some wooden stairs. (so roughly 45 feet from AE to 2nd AX). It wasn't the speediest thing going but it did the trick with older Macs.
I recently bought a MacBook Pro which supports 802.11n. I most often use this laptop at the point in the house furthest away from the AE (Base Station) The AE (Base Station) is in my home office connected to my MacPro desktop (see #1 below). In addition, the family iMac is also in that room furthest from the AE. Using the new MacBook Pro with the old 802.11/g/b network turned out to be painfully slow. I was experiencing the same slow network connection my family has complained about for years with their older Macs and 802.11g/b.
I decided it was time to upgrade the whole network, if only to speed up my MacBook Pro connection. Bought new 802.11n Airport Extreme (MC340LL/A) and 2 new 802.11n Airport Expresses (MB321LL/A). Setup did not go smoothly. Again, my normally competent Mac persona was reduced to a babbling three-year-old. Had three different Apple techs on the phone trying to help me through it. Got different, contradictory instructions from the last two. Finally got all three units working, only to find that not only does my MacBook Pro seem even more sluggish than when connected to the old 802.11g/b network, but my wife tells me web pages are taking at least twice as long to load as with the old network.
As concisely as I can lay this out:
*1. Airport Extreme (Base Station)*
Connected via Ethernet from its WAN port to my Comcast cable modem. One Ethernet (LAN) port on that AE is then connected via Ethernet to my Netgear 8-port Ethernet switch. Ethernet from switch to Ethernet port 1 on my MacPro. (MacPro does NOT have an Airport card because I forgot to order one. Also I confirmed that this setup was functional by connecting to the AE wirelessly with my MacBook Pro showing the name I'd given the new network prior to adding the two AX's to the mix).
Some Airport Extreme settings of note (all accessed via "Manual Setup" button):
Airport Tab > Summary
Version 7.5.1
Wireless Mode: Create a wireless network
Channel: 149 (Automatic), 1 (Automatic)
Wireless Clients: 3
Airport Tab > Base Station:
Allow Setup over WAN: Unchecked
Airport Tab > Wireless:
Allow this network to be extended: Checked
Airport Tab > Guest Network:
Nothing checked
Airport Tab > Access Control:
MAC Address Access Control: Not Enabled
Internet Tab > Internet Connection:
Connect Using: Ethernet
Ethernet WAN Port: Automatic (Default)
Connection Sharing: Share a public IP address [Think this one is probably wrong]
Internet Tab > TCP/IP:
Configure IPv4: Using DHCP
Internet Tab > DHCP:
Shows Beginning & Ending Address
Internet Tab > NAT:
Enable default host at: Unchecked and blank field
Enable NAT Port Mapping Protocol: Checked
Internet Tab > Advanced
Didn't touch anything here, so all at defaults
*2. Airport Express #1: Living Room Express (Closest to AE (Base Station)*
Airport Tab > Summary
Version 7.4.2
Wireless Mode: Extend a wireless network
Connect using: Wireless Network
Channel: 1 (Automatic)
Wireless Clients: 1
Airport Tab > Base Station:
Allow Setup over the Internet using Bonjour: Unchecked
Airport Tab > Wireless:
Wireless Mode: Extend a wireless network
Allow wireless clients: checked
Airport Tab > Access Control:
MAC Address Access Control: Not Enabled
Internet Tab > Internet Connection:
Connect using: Greyed-out, not selectable
Connection sharing: Greyed-out, not selectable
Internet Tab > TCP/IP:
Configure IPv4: Using DHCP
Shows IP Address
Internet Tab > Advanced
Didn't touch anything here, so all at defaults
*3. Airport Express #2: Dining Room Express (Furthest from AE (Base Station)*
Airport Tab > Summary
Version 7.4.2
Wireless Mode: Extend a wireless network
Connect using: Wireless Network
Channel: 1 (Automatic)
Wireless Clients: 2
Airport Tab > Base Station:
Allow Setup over the Internet using Bonjour: Unchecked
Airport Tab > Wireless:
Wireless Mode: Extend a wireless network
Allow wireless clients: checked
Airport Tab > Access Control:
MAC Address Access Control: Not Enabled
Internet Tab > Internet Connection:
Connect using: Greyed-out, not selectable
Connection sharing: Greyed-out, not selectable
Internet Tab > TCP/IP:
Configure IPv4: Using DHCP
Shows IP Address
Internet Tab > Advanced
Didn't touch anything here, so all at defaults
SETUP/GOALS:
With Airport Extreme (Base Station) as the starting point, have the two Airport Express units with the strongest, fastest signal possible, provide Internet access (and file sharing, iTunes speakers capability) to three Macs (one older iMac, one older PowerBook and my new MacBookPro). Again, I believe my new MacBook Pro is the only one with 802.11n support, so I don't expect the other Macs to take advantage of the speed boost offered by the three new 802.11n devices.
+Any and all help with this will be greatly appreciated. Thanks!+

{quote}With the AirPort Extreme, in the AirPort panel, Wireless tab, click on the button for "Wireless Network Options", check the box for "5 GHz Network Name", and enter a different network name. (That can be trivially different, such as the name of the main network suffixed with an underscore and the digit 5.) Once configured that way, connect your "N" gear to each network in turn to see if one is any better than the other. (If you're wondering what effect this would have, it allows segregating your "N" gear from the older gear to prevent the older gear from slowing down your network. However, distance and interference from things like walls may negate any advantage.){quote}
William: I was gone most of yesterday, but had a chance to implement your recommendations today. I added the 5 GHz network as you suggested, but in order to connect to that at all with my 802.n11 MacBokk Pro, I need to be within a few feet of the AE (base station). If I try to access that network even from the next room (well within reach of both the AE and the livingroom AX, I get one bar and "failure to connect" messages just trying to logon to that network.
However, I did some experimenting that (as of right now, anyway) resulted in much faster network access, not only from my MacBook, but also from the older iMac which is the furthest Mac from the AE. According to my wife, that iMac is "loading web pages faster than I've ever seen them!"
Here's what I did:
1. Moved all three units to places where it seemed they would have the least amount of interference with the clearest path from unit to unit, also raising the height of both AXs from about 2-3 feet from the floor to about 5-6 feet from the floor.
2. Changed one setting on the AE (base station): Wireless Tab > Wireless Network Options > Multicast Rate ---> Changed this from Low to High.
I have a feeling the location shifts made the real difference, but I will try changing the multicast rate back to "Low" just to see what happens.
Paul

My MBP doesn't connect to 802.11n networks

Similar Messages

Maybe you are looking for