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.

Similar Messages

  • Is there a way to force my new MacBook to use 802.11n only?

    I am trying to force my new aluminum MacBook to only use 802.11n as I am experiencing slow connectivity. Does anyone know if this is possible?

    niceshoes6 wrote:
    Join the club. everyone is experiencing slow connectivity
    Not "everyone" because I am not. All is just as it was with my original MacBook, and plenty fast. I am using Wireless-G (MacBook 2.4 is only machine here which has Wireless-n in it).
    Phil

  • IPhone 5S won't use 802.11n

    Recently I was messing around with my WiFi router's settings to test moving to a 5Ghz spectrum from the 2.4Ghz one.  Sometime during the process I noticed that my iPhone had disconnected from the router and would not connect to it no matter what I tried.  As a last resort I turned off the setting that required all devices that were connected to be using 802.11n.  As soon as the setting was changed my iPhone connected to the wireless network.  When I looked in the connected devices tap it said that it was using 802.11g.  To my knowledge the phone was using 802.11n on iOS7 but something changed after the update to iOS8.1.  Is this a software problem (and are other people experiencing the same problem), or could it be a hardware problem with the phone?

    I have EXACTLY the same issue & and just spent nearly an hour on the phone with BT trying to get an answer, to no avail!
    My setup is:
    BT HH 2.0 set up for 8011.2 b/g/n (as recommended)
    BT HH has BTFon on and sharing - as well as BT Openzone
    Several mobile devices - but let's focus specifically on the Dell Latitude E6510 with an N-Series wireless card
    The scenario is:
    My BT HH is showing an 'actual data transfer speed' of 130Mbps
    My laptop connects to the BT HH SSID at a constant 54Mbps
    My laptop connects to the BT BTFon SSID at a constant 130Mbps
    My laptop connects to the BTOpenzone SSID at a constant 130Mbps
    My laptop connects fine to other N-Series routers at 130Mbps outside of my home - so I am ruling out any configuration issues with the laptop.
    There are no other wireless devices connected to the router at present. 
    I've used inSSIDer 2.0 to validate that the router is broadcasting at 130Mbps using 802.11n and the signal is constantly strong
    So, why is my laptop unable to achieve a speed of 130Mps from the router?
    Why can I achieve better throughputs if I connect to BTFon or BTOpenzone?
    My question to the BT Support staff (for which they had no answer) is if I am enabling BTFon and BTOpenzone on my router, is that in some way reducing MY internal throughput in speed?
    The BT HH 2.0 is promoted as an N-Series device - yet I cannot use it as such - and I make use of the BTFon community as I travel about, so I do not want to switch it off. 
    I know that I can connect via Ethernet to the HH, and do when I am static - however, I also stream some large files/videos around the house, for which N-Series is perfect - when it works!!!
    Any advice / help gratefully received.

  • 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.

  • Forcing Apple TV to use 802.11n

    My wireless network is as follows.
    Airport extreme connected to internet via cable modem.
    Airport express configured as remote WDS base station.
    Apple TV connected via wireless to network.
    My problem.
    Both the airport express and the airport extreme are within range of my Apple TV however the Apple TV appears to connect to my wireless network via the airport express limiting it's speed to 802.11g. The airport extreme capable of 802.11n is clearly within range of my Apple TV and I would like it to only connect via 802.11n. Is there any setting within the Apple TV to force it to stay on the 802.11n network even if the signal from my airport express may be stronger.
    20" iMac core duo 2.0Ghz, Black Macbook core duo 2.0Ghz, 17" iMac 1.8Ghz G5, Powermac G4 1.0Ghz   Mac OS X (10.4.9)   Apple Extreme (pre-n), Airport Express, Apple TV

    DML,
    RE:Another option would be to set up the Extreme to use Access Control, limiting it to specific machines, by entering MAC addresses. If you don't enter the Apple TV's MAC address into the Express, would it be forced to find the Extreme, where it has 'permission' to access the network ?
    That was an awesome idea and I think it might solve my problem. I setup the access control list on my express to only accept connections from my macbook. I'll post again after some further testing with my Apple TV. Many Thanks.
    20" iMac core duo 2.0Ghz, Black Macbook core duo 2.0Ghz, 17" iMac 1.8Ghz G5, Powermac G4 1.0Ghz   Mac OS X (10.4.9)   Apple Extreme (pre-n), Airport Express, Apple TV

  • 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.

  • Packet loss / pausing when using 802.11N (Intel 6300)

    Hi,
    Previously, I had posted a thread involving the Intel 6250, and lack of detection of N WiFi on that card. Some time later, I bit the bullet and got an Intel 6300 card off eBay. After receiving it today, I popped it into my Thinkpad X220, and it worked.... sort of. I can definitely see wireless N support, and can associate with my 2.4 GHz mixed-mode B/G/N network at 130 Mbps, and my 5 GHz N-only router at around 243 - 270 Mbps. However, right off the bat, it seems the number of "Tx Excessive Retries" in iwconfig climb up to several thousand within ~ 15 - 20 minutes of connecting. Also right off the bat, pings are rather inconsistent (typically at least 2 ms greater than when the card is forced to work in G-only mode, and with pauses and spikes up to 800 - 2000 ms, and packet loss from 5 - 10%)
    From what I have gathered so far, there has been a bug in the iwlwifi kernel tree that affects N wireless users, and this bug has been around since around 2010 or even earlier. However, I was under the impression that some sort of fix has been merged into the mainline Kernel at this point (I'm on 3.5.3-1-ARCH BTW), and my symptoms are somewhat less aggressive than the ones others described (basic web browsing works reasonably well, though there is often noticeable lag in the response times, but anything latency/packet loss-sensitive will suffer in a major way.) Has anyone managed to get wireless N to actually work reasonably well on Arch (or for that matter, ANY linux distro)? As I understand it, the matter is one of relation to the kernel module itself, so distro-distro variations of userspace apps shouldn't be as much a factor anyway. I am using WICD for my network manager, and am happy to say that it does its job admirably well (assuming the card is set to G-only mode, but the connection itself is actually maintained quite stably even in N mode.)
    While I understand that the 11n_disable=1 "fix" allows most people to get on with their lives, I am rather alarmed that this is being considered a long-term solution. Many laptop owners (ThinkPad owners like myself for example) are essentially locked into Intel WiFi cards, unless we are willing to take an expensive risk and flash our BIOS to one that that doesn't have a "whitelist" of approved cards (something that can void the warranty or worse, brick a laptop.) All the while, Intel is still claiming Linux support for a card whose major capabilities are essentially neutered purely based on the OS a user chooses to run (yes, I do consider N to be a major capability, considering 300 Mbps N WiFi is basically old news, with many manufacturers coming out with full 450 Mbps routers. Also, chipsets like Atheros seem to have no problems with offering both performance and stability under Linux... my desktop rig using an Atheros card manages perfectly fine on a full-rate wireless-N network with essentially no packet loss or latency spikes.)
    Below is some information that might be useful:
    iwconfig (802.11g, ~ 1 hour after connection and running a few speedtests, browsing, ping testing):
    wlan0 IEEE 802.11abg ESSID:"dd-wrt"
    Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
    Bit Rate=54 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=69/70 Signal level=-41 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:359 Missed beacon:0
    iwconfig (802.11n, 5GHz after ~10 minutes browsing/ping testing):
    wlan0 IEEE 802.11abgn ESSID:"net2"
    Mode:Managed Frequency:5.745 GHz Access Point: XXXXXX
    Bit Rate=243 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=55/70 Signal level=-55 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:860 Invalid misc:50 Missed beacon:0
    iwconfig (802.11n, 2.4 GHz after connecting and running a speedtest):
    wlan0 IEEE 802.11abgn ESSID:"dd-wrt"
    Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX
    Bit Rate=117 Mb/s Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=66/70 Signal level=-44 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:974 Invalid misc:59 Missed beacon:0
    dmesg | grep iwl :
    [12011.488089] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [12011.488092] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
    [12011.488269] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [12011.488271] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050f8000
    [12011.488273] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
    [12011.488585] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
    [12011.491862] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
    [12011.492112] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
    [12011.492114] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
    [12011.492116] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
    [12011.492117] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
    [12011.492119] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
    [12011.492121] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
    [12011.492206] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12011.502925] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
    [12011.502928] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
    [12011.502930] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
    [12011.502946] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [12011.503105] ieee80211 phy8: Selected rate control algorithm 'iwl-agn-rs'
    [12011.503456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12011.503661] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12011.745631] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12011.745868] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12073.651471] iwlwifi: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [12073.651474] iwlwifi: Copyright(c) 2003-2012 Intel Corporation
    [12073.651660] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [12073.651661] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900050b8000
    [12073.651663] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
    [12073.652241] iwlwifi 0000:03:00.0: irq 50 for MSI/MSI-X
    [12073.655662] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
    [12073.655887] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
    [12073.655890] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
    [12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
    [12073.655891] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
    [12073.655892] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
    [12073.655894] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
    [12073.655975] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12073.666587] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
    [12073.666593] iwlwifi 0000:03:00.0: Device SKU: 0x1F0
    [12073.666595] iwlwifi 0000:03:00.0: Valid Tx ant: 0x7, Valid Rx ant: 0x7
    [12073.666618] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [12073.667056] ieee80211 phy9: Selected rate control algorithm 'iwl-agn-rs'
    [12073.667456] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12073.667659] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12073.908411] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12073.908632] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.261869] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.262090] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.487757] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.488010] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.699574] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.699781] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12087.837322] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12087.837526] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12097.329577] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12097.329832] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12097.797748] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12097.797970] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12098.016220] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12098.016458] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.458762] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.459006] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.608769] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.609021] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.764093] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.764341] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12100.979029] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12100.979228] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    [12101.159987] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [12101.160208] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
    lshw | less :
    *-network
    description: Wireless interface
    product: Centrino Ultimate-N 6300
    vendor: Intel Corporation
    physical id: 0
    bus info: pci@0000:03:00.0
    logical name: wlan0
    version: 35
    serial: 00:24:d7:be:9e:74
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress bus_master cap_list ethernet phy
    sical wireless
    configuration: broadcast=yes driver=iwlwifi driverversion=3.5.3-
    1-ARCH firmware=9.221.4.1 build 25532 ip=192.168.1.145 latency=0 link=yes multic
    ast=yes wireless=IEEE 802.11abgn
    resources: irq:50 memory:f2500000-f2501fff
    Thanks,
    - A.G.

    I have an ASUS UX32VD-DB71 which has the Intel Centrino 6235 wifi card. I've been having this laptop for more than 6 months and I've tried different solutions to fix the issue with Wireless-N but none of them were stable other than disabling N completely using 11n_disable=1
    I've tried different kernels all the way from 3.2 to the latest 3.7 series of kernels (both in the openSUSE tree as well as mainline) with no luck whasoever. I also tried installing the compat-drivers from 2013-01-23-1-u version onto my 3.6 kernel which provided the same results too. I see packet loss with N and the G speeds are just too slow. I have a workstation in my network and I can only transfer effectively at 1.5 MB /s max over G whereas an old laptop from 2007 which has an 1x1 MIMO antenna (again Intel though) can connect at 144 Mbps to my router and transfer files at least 3-4 times faster (if not more).
    It is totally unacceptable for Intel to not just fix this issue for Linux.
    Last edited by Tuxdude (2013-02-17 01:38:59)

  • 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 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

  • Can I Use 802.11n Base Station and 802.11n AirPort Express in an 802.11 ac Time Capsule Main Base Station WDS Network?

    I havea "wirelessly challenged" 2-story home and need to extend the range.  Currently I have an 802.11n Main Base Station with an 802.11n Airport Express Remote.  It's not getting the job done (upstairs connection is weak).
    I am considering getting an 802.11ac Airport Time Capsule to help, even though I currently only have devices with 802.11n wireless connectivity (future-proof a little).
    I an planning on setting up a Wireless Distribution System (WDS) Network:
    1.) Setting up the Time Capsule as the Main Base Station connected to a Cable modem
    2.) Reconfiguring and Setting up the current AirPort Extreme 802.11n as a Relay Base Station
    3.) Reconfiguring and Setting up the current AirPort Express 802.11n as a Remote Station
    I cannot "hard wire" one Base Statio to the other.
    Will this work?

    Will this work?
    Unfortunately, no.  WDS is a older, very inefficient way to extend the wireless network signal.
    As such, newer operating systems like Lion, Mountain Lion and Mavericks do not even offer settings for this older WDS type of network.
    In addition, the new Time Capsule has no capabilities to use WDS settings at all, even if you used a Mac with another operating system to try to set things up.
    Even if it were possible to set up a WDS network, the speed on the network would be incredibly slow. As you know, WDS only operates at "g" wireless speed levels. Each "relay" or "remote" that you add to the network each cuts that bandwidth or speed in half.
    With a WDS "main", "relay" and "remote", the network would be operating at about 14 Mbps......a tiny fraction of what the devices would be capable of providing normally.

  • Macbook refuses to use 802.11n?

    I have an 802.11n router, running in MIMO mode with WPA2/AES encryption, with only two machines attempting to connect to it. Both are running OSX 10.6.5:
    My macbook air 1.6GHz (December 2010). This machine connects perfectly as 802.11n, every time.
    My wife's 2GHz Macbook 2,1 (I think somewhere around mid-2007 manufacture). This machine has the n extension installed (I can't recall installing it, but network utility shows it as 802.11 a/b/g/n). Whenever I attempt to connect with this machine, connection initially fails, but it eventually connects as an 802.11g connection (as shown by option-clicking on the network icon). When it does connect - not very well - it slows the connection of the macbook air way down.
    I'm guessing that if I could force my wife's machine to connect in n mode, everything would be OK. Does anyone have any suggestions?
    What I've tried so far:
    .deleting and re-enabling the wireless drivers in the network preferences panel
    .making a new network location
    .deleting all relevant plists
    .repairing disk permissions
    Relevant background information:
    .the 'n' router only supports channels 1-12 (i.e. we can't force n by using non-g channels)
    .this network is in a crowded apartment block - I can see around a dozen other networks in istumbler
    .the router is using directional paired (MIMO) antennas to bounce the signal from one apartment to another off an adjoining building. Of course, this could in general be problematic; but the received signal strength is OK - not good - according to both istumbler and a separate linux metering program. And the MBA works perfectly well in the same locations.
    .it's using channel 1; there are two g networks in the building also using channel 1, but according to istumbler, our signal is strongest of the three in the 'receiving' apartment (in channels 6 and 11, there are other stronger signals, so 1 is the only rational choice).
    .the router is running in mixed, not greenfields, mode
    .although the MB is only able to connect in g mode, istumbler on the MB still shows it as an 'n' network
    .we have never encountered any previous wifi problems with the MB (but this is the first time we've tried to connect it to an n router)
    .and just to repeat, the router is using WPA2/AES encryption, which should be compatible with 802.11n
    TIA for any help

    SOLVED!
    Who in the world would have guessed??
    Trendnet support provided this information:
    <<Note: Due to chipset compatibility issues, if you choose WEP, WPA or WPA2-TKIP encryption this device may operate in Legacy Wireless mode (802.11b/g). You may not get 802.11n performance as these forms of encryption are not supported by the 802.11n specification. >>
    I had used WPS2-TKIP, just by accident. I changed it to Authentication WPA-Auto and Cypher type auto, and now it works on 802.11n, as well as g!! Even on my Powerbook G3 and HP laptop.
    Who would have guessed?

  • 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.

  • Imac 17" 1.83ghz - OK, it's incompatible, but how can you use 802.11n???!

    The Imac Intel G5 17" 1.83ghz does not work with airport extreme's draft 802.11n, for whatever reason. What are the ways to make it compatible? Currently using it on 802.11g but I do want to use the 802.11n.....
    Any ideas?
    Many thanks.

    The Imac Intel G5...
    Intel and G5 are 2 completely different things. You do not have a G5 you have an Intel-based iMac. It either has the "Core Duo" processor or "Core 2 Duo" processor.
    You should take a look at some of the USB solutions offered by QuickerTek.

  • 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 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.

Maybe you are looking for