AEBS 802.11n only connects at 54Mbps?

http://img266.imageshack.us/img266/6168/airportwifi1dm6.png
im wondering if this the proper connection speed for the AEBS 802.11n im on wifi so im not connected to my router via ethernet, and im sue a MacPro with a preinstalled AirPort Extreme card.
any suggestion on how to get a faster transfer speed/rate?
thank you very much!

thank you very much for your time.
alright i applied that to the airport i did the 802.11n 5GHz option
and it states in my network utility im connected at Link Speed: 270mb so i'm assuming thats the proper speed?
its been a quite long time since ive messed around with wireless and all that, and im new to the apple wireless hardware.
i mean the connection is fast and great but im just wondering which option is better to use for a faster connection?
thanks again!

Similar Messages

Unusual setup experience on AEBS 802.11N

I got my new AEBS 802.11N only 3 days ago, this was intended to upgrade my old AEBS 802.11b/g device. I installed the new Airport Utility software on my MacBook Pro, it went through the usual setup steps.
My MBP saw the old AEBS when Airport Utility was open for first time, I saved the config file of the old AEBS onto my MBP, shut it down and then started up the new AEBS 802.11N.
Since new AEBS device was at factory default, I imported the old AEBS config file into new AEBS, noticed that it would automatically set the Wireless security to None. The old config file definitely had the security settings on WPA/WPA2 Personal.
After applying the config to new AEBS noticed that it will not even advertise the SSID which I had set and yellow light was lit steady, probably meaning - no security enabled.
My MBP's Airport will not see the new AEBS' SSID no matter what I tried WEP, WPA, WPA2, even tried joining it manually with no security. Occasionally when security was set to None, the SSID would appear on my MBP momentarily then when I try to join it, it would say "Error Joining network".
I do have Airport Extreme Update 2007-001 installed too, even a reboot of my MBP did not help. I even reset the new AEBS to factory default and started fresh, it still did not work, it simply will not advertise it's SSID even when setting for Closed Network was left unticked in the Wireless Options pane and network mode was in Create a Wireless Network??
However I was able to get to the Internet when using the Ethernet ports on new AEBS which was connected to a DSL Modem but not on Wireless because the SSID is not advertised??
Next I fired up my MacMini which I had been using as a Media Center, it came on and saw the new AEBS SSID and joined it just fine at 54Mbps 802.11g (MacMini has no N) by this time I had the new AEBS set to WPA/WPA2 Personal security. ??
So I went in and tinkered further with the new 802.11n AEBS, I decided ah well lets create a WDS network pairing with my old AEBS, I set the new AEBS to WDS Main and old AEBS as WDS relay.
The new AEBS decided to announce Network Status as Error WDS, I went in and set the correct MAC addresses for the peer-to-peer WDS and then suddenly at this point the new AEBS refused to restart?? I really thought ah well it's time to call Apple?? Then I decided to unplug power source wait 60 seconds and started up the new AEBS again, it still reported Error WDS probably because old AEBS was also off by then.
I decided to go back to "Create a network" and suddenly voila the new AEBS started to work, the SSID was appearing on my MBP's Airport pane and I could join it. My MacMini was at this point happily chugging along on Wireless Internet as well. However my X-Box360 wireless will not join even when I selected WPA, it worked fine on my old AEBS in WPA Personal security mode.
There is something not right with the new AEBS 802.11N that I got, could it be a firmware issue? I have version 7.0 on mine. Just out of curiousity, I restarted my old AEBS and it works fine on 802.11b/g with all my devices including the XBox360.
My MBP reports it's only running at 144Mbps on the new 802.11n AEBS, is this right? I thought N could go higher or could it be because I have radio mode set at 802.11n (802.11B & G compatible) ??
Anyway thought it was worth reporting this.

I discovered something new with these AEBS 802.11N (firmware ver 7.0) devices last night.
It seems when I set it on Create Wireless network, 802.11n (b/g compatible) with WPA/WPA2 security and Channel selection set to Automatic (13), the unit will not advertise it's SSID even when Closed Network is deselected?
My MBP C2D and PB 15in will not pick up the SSID at all.
Howver when I switch the Channel selection from Automatic or anything other than channel 13, the SSID is picked-up by the MBP and PB and able to join the network perfectly ??
Has anyone out there discovered this issue with the new AEBS 802.11n? Does anyone have fix for it yet?
However my MacMini C2D seem to chug along just fine in any setting i select on the AEBS?
XBox360 only works in No security settings.
MBP C2D, MacMini C2D, PB Alu 15in. Mac OS X (10.4.8)

AEBS 802.11n question about bridging

using AEBS 802.11n and connecting to an existing network which is using DHCP...
internet button chosen
internet connection panel chosen
connect using : ethernet
configure ipv4 : using dhcp
ethernet wan port : automatic (default)
connection sharing : share a public ip address
is the AEBS acting as a bridge here? so, now the AEBS can pass out ip addresses that are different (local) network addresses than what the AEBS is receiving from the established network, which it is joining?? the established network 192.168.1 the AEBS DHCP network 10.0.1
internet button chosen
internet connection panel
connect using : ethernet
configure ipv4 : using dhcp
ethernet wan port : automatic (default)
connection sharing : Off (bridge mode)
or...
the AEBS is acting as a bridge here? (off (bridge mode)) can the AEBS pass out ip address using a different network address here? and if it does so there will be no NAT functionality?
what does it mean to have DHCP functionality and no NAT. does using DHCP and no NAT mean that each computer, on the local network connected to the AEBS, that segment, must have a static address?

In your first configuration, where connection sharing = share a public IP address, the AEBSn is still acting as a wireless router and, effectively, has created a second wireless subnet.
In the second configuration, where connection sharing = Off (bridge mode), the AEBSn is "passing thru" the NAT/DHCP services from the router it's connected to so any devices connected to the AEBSn will still be on the same network as the upstream router.

Laserjet 1505 connected to AEB 802.11n via USB keeps timing out after print

I have a HP Laserjet 1505 connected on my AEB 802.11n via USB and shared on my network, on my network are two macs connected via wifi and 3 WinXP PC connected via wire. I have Bonjour and WinXP laserjet drivers installed on all Win PC. Everytime I print from any of the computers, it will print the first time, but when I try printing again from any of the machines, the macs and winxp pc's cannot detect the printer. When I go to airport utility, the printer cannot be detected anymore. I have to hard reset the AEB for it to detect the laserjet printer again. But the same thing happens again after I print out another document. Has anybody encountered this kind of problem. Can anyone help me resolve this?

Here is what I got from HP support :
The driver for the Laserjet P1006 is not available yet for Os 10.5...we are hoping it will be release in the next week or so...please click on the link below to sign up for an email update as soon as it is available..As a workaround, some people have been able to use the 10.4 driver from the cd, but this is not guaranteed to work in all applications therefore the only solution is to wait and install the 10.5 driver.
So we wait.
Yves

AEBS 802.11n, TC and APXn with 7.3.1 is very flaky indeed - cant connect -

HI Guys I think many of you on these forums have posted because you are having joyless experiences with the new APX 802.11n, the AEBSn and the TC not able to be managed via the AIRPORT UTILITY.app v5.3.2 with firmware 7.3.1 in the former devices. After a search there's many of these posts with people with the same issues.
I have these devices in my place so I have had lost of experience configuring these over the years:
1 x 802.11n AEBS, 1 x TC, 1 xUFO white AEBS, 2 x APXg's and lastly the problematic 1 x APX802.11n (one subnet and 2 x networks 2.4Ghz and 5 Ghz)
I am at my wits ends trying to get the new APXn regularly responding to the AP utility.app (error reading configuration).
I have tried most of the remedies on these forums but they do not consistently solve the problems of the APX not responding to the AP utility.None of these have consistently worked:
• trying to factory reset it using the POWER ON+RESET and waiting for the amber flashes then green - butt this procedure NEVER WORKS to factory reset!
• using the reset button in any form (it doesn't do anything)
• connection through ethernet (sometimes works ).
• takes long to power up (than the older 802.11g)
• rest APXn back to factory defaults through the AP utility then ...
• downloaded 7.3 firmware - worse and wont work
• lastly I found that RESET+POWER ON then wait for 20 secs as as it powers up DEPRESS the RESET again and then it becomes readable.
Additionally, I have been unsuccessful in getting PORT FORWARDINg to work at all for the AEBS 802.11n with and without the TC in the mix. I had this working for several years with the White UFO AEBS ... It beats me.
I think the firmware is very very flaky and i have no resolutions for these recent problems.
Hope for a fix soon.
I will be polling these forums for any clues.
w

Hi Guys
REgarding the APXn's (802.11N Airport express) inability to consistently be seen by the Airport Utility.
this just worked finally for me now and have tested this 7 times and all seems ok now..
Simply: when APXN in list, save configs, reset to factordeafuts, downgrade to 7.3, upgrade to 7.3 and reinstate .configs.
UPdate: a probable work instruction that seems to consistently work.
Here is the work instruction i used.
(1) turn off all other WIFI base stations where you are that you can. (important I believe)
(2) turn off airport in your mac
(3) connect troublesome APXN to mac via ETHERNET cable. Set DHCP on your mac or some address in IPV4
(4) power off and on the APXn (yes again )
(5) whilst it is powering up, use a pen of toothpick to RESET the APXn again (i think this causes something to move around inside the magic-ware)
(6) the light will flash amber (no network to connect to)
(7) launch /utilities/airport utility.app
(8) the one and only APXn appears in the list
(8.5) optional: (cross fingers and legs :))
(9) when profile comes back, use FILE/SAVE a COPY AS to the ~/desktop to save the complete profiles and settings of what you have in there currently.
(10) select the one and only APXn and perform a airport utility.app/base station/ RESET TO FACTORY DEFAULTS - and wait for 30 secs and then it will restart
(11) when complete, quit and relaunch the /utilities/airport utility.app
(12) the APXN will be as when you bought it (pristine and no stuff in it from you)
(13) connect your mac back to internet via ethernet if possible. (avoid the wireless just to be sure but at this stage you could reinstate all your exiting wireless infrastructure)
(14) select the one and only APXn AGAIN and perform a airport utility/base station/ UPLOAD FIRMWARE and select version 7.3 (back level) . THe firmware will load into APXn 0%-100% guage and then it will restart.
(15) when complete, quit and relaunch the /utilities/airport utility.app and it will warn that one of the basestations (the only on the list - the APXN) has later FIRMWARE available for it. [This is 7.3.1].
(16) reply OK to UPLOAD NEW 7.3.1 firmware. (yes yes I realise ths sounds silly but it works ok ) 7.3.1 Firmware will up load into the APXN as above and restart will take place.. so say 120 seconds.
(17) quit and relaunch the /utilities/airport utility.app. THE APXN will appear as before as now with 7.3.1.
(18) just to make sure, (we're not quite finished), remove the ETHERNET cable. If not already done form previous optional step, ENABLE the AIRPORT (WIFI) on your mac.
(19) power OFF then power ON the APXn.. wait for the usual 70 secs..
(20) Again, to be sure, QUIT and RESTART the /utilities/airport utility.app, the APX as factory default with amber icon will appear in the list [along wit the rest of your apple airport base stations).
(21) Select it in the list fo MANUAL and the configuration will be read quickly.
(22) do this (steps 18-21) 3 or 4 times to see that it is consistent. (I this it 7 before posting this).
last step...
• select the APXN (default settings) and IMPORT the save configuration file (~/desktop/nnn.baseconfig) (all it) from the ~/desktop. Ignore any errors (untick them), add a password for the base station and UPDATE!
• wait for the usual 70 secs.
• without quitting the /utilities/airport utility.app, the UPDATED APXN with your configuration will be in the list.
NOw try and selectit for manual and it should respond in time without timing out.
Test by powering off and removing from wall socket and moving around too to make sure you can SEE it in the /utilities/airport utility.app and select it for MANUAL CONFIGURATION.
After many days of frustration on weekend and over night, this appears to have worked ok for me.
(now to work out the AEBSn port forwarding issue - it wont work).
HTH
w

Use USB-connected hardidsk as timemachine backup using AEBS 802.11n

Hello
I got this external hard disk MyBook 1TB. When it is connected to my Macbook Pro directly via USB or firewire, I can configure it as backup disk for timemachine.
Hwever if I connect this same hard-disk to the AEBS 802.11n via USB I cannot see it in the time machin utility.
I thought this would be an alternative to the timecapsule. (as i was told it is possible).
Any hints?
SL

Time Machine via Airdisk: Possible? Yes. Apple supported? No.
Time Machine backups to AirDisks (e.g. USB HDD attached to Extreme 802.11n) is unsupported, but has been successful by some. As well, once you decide to move any old TM backups (HDD connected directly to the Mac) to an AirDisk, you cannot continue backing up to your previous TM backup. The format it saves to vs. a local HDD is different. The folder structure you see becomes a sparsebundle/disk image via the AirDisk.
If you are interested in proceeding with your plan, check these links out:
http://discussions.apple.com/thread.jspa?messageID=8225748&#8225748
http://discussions.apple.com/thread.jspa?messageID=8650723&#8650723
http://jamesshore.com/Blog/How-to-Accelerate-Time-Machine.html

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

802.11n only MBP connects new MP not

When I set the Airport Extreme Base Station to 802.11n only (5GHz) then my MacBookPro (2009) does connect wirelessly, as do the other Airports in the chain. But my brandnew MacPro (mid 2010) does not. Is it possible this one works on 2.4 GHz only and does not recognize the 5 GHz band?
I read something about some Airports being dual band. How can I find out if mine fall in that category?

Something strange seems to happen here. First time I changed to 5 GHz the other AX's in the chain reconnected. But the MacPro did not, even when trying to reconnect with network Name and Password. Then, changing the network from a closed network (Name has to be known) to one that can be seen, suddenly the MacPro did connect to the Airport network. Is there an issue with networks in closed status? (Wireless>>Wireless Network Options>>Create a closed network).

MacBook Pro elbows out MacBook from Internet connection on AEB (802.11n)

I have recently setup Airport Express Base Station (802.11n) to connect to Internet via PPPoE. I have the following:
a) MacBook Pro;
b) MacBook;
c) ITouch;
d) Wii
All four hook up to the AEB, and connect to the Intranet individually.
But the two laptops do not connect to the Internet simultaneously.
If the MacBook Pro is already connected, the MacBook does not. When I shutoff the WiFi on the MacBook Pro, I have to go through all the steps in the Airport Utility on the MacBook, to connect to the Internet. It works fine, as long as the WiFi on the MacBook Pro remains switched off. As soon as I connect MacBook Pro to the AE, the Internet on the MacBook drops out. The MacBook does however continues to show the name of my AE network (along with several others in the neighborhood) networks.
Internet Connection from ITouch and the Wii remains unaffected.
My intuitive analysis was that perhaps both laptops are using the same frequency or channel to connect to the AE. So I changed from "Automatic" to "1" on the MacBook Pro and "2" on the MacBook. It did not help despite more combination.
Any suggestion please.
regards ... Ajay

Ajay,
Welcome to the Apple Discussions!
Do me a favor, as so many others are experiencing this as well with multiple Macs on a network. I've suggested so many different things, but this one just came to mind while I read your post. Try this on all the Macs and let us know...
*Can’t Access Certain Web Sites / DNS Server Settings Issue*
I'm wondering if either or both Airport Utility & Network Prefs have proper DNS server settings. Try this
Launch Airport Utility.
Select TC on left.
Click "Manual Setup".
Select "Internet" from the toolbar above.
What's listed for "DNS Server(s):"?
Try putting in these servers from OpenDNS
208.67.222.222
208.67.220.220
Click "Update".
Your TC will restart with the new settings.
Next, launch System Prefs --> Network Prefs.
Select the service you usually connect with on the left (Airport or Ethernet).
Then click, "Advance..."
Click the "DNS" tab.
What's listed for "DNS Server(s):"?
Usually "10.0.1.1" will be listed first in gray. This refers back to the settings in the Airport Utility.
Nevertheless, it doesn't hurt to add the DNS servers noted above here as well.
Click "OK" then click "Apply".
Finally, reboot your Mac.
Now see if you have internet access all around.
Let us know if this resolves your issue.
Cheers!

Lose Network Connection w/AEBS 802.11n when transferring large data amounts

Hi,
I have a LaCie 500GB external hard drive that is connected to my AEBS 802.11n via a USB hub. Lately, when I am backing up my MacBook Pro to that drive, transferring 5GB or so of data, I notice that my MacBook Pro loses connection with the AEBS (i.e. the network goes down) right smack in the middle of the data transfer. I either have to reboot the MacBook Pro -- or -- unplug and replug the AEBS to reestablish connection.
I was just wondering if this sort of network connectivity loss is being experienced by other people doing large data transfers over the AEBS to an external drive?
Thanks.
Message was edited by: jmFightSpam

I hate to be the one adding a "me too" post, but, me too!
When I try to open iPhoto (library stored on a USB drive attached to AEBSn) the AEBSn crashes, flashes orange once or twice and then restarts. Currently running firmware 7.2 because 7.2.1 wasn't allowing me to reconnect to AirDisks after MacBook went to sleep. If the drive is connected directly to my MacBook there is no problem.
If anyone, anywhere has any idea, I'd be very grateful!

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.

AEBS 802.11n 5GHz gives "invalid password" - need a solution!

After an update to 7.2.1 I've been trying for the past 4 hours to get back on my 5GHz network, but no success. I hope someone can resolve this, because it's getting extremely annoying.
- 802.11n (b/g compatible) 2.4GHz, pass or no pass -> works
- 802.11n only 2.4GHz, pass or no pass -> works
- 802.11n 5GHz, no password -> works
- 802.11n 5GHz, WPA2 Personal pass -> invalid password
I tried everyting. First setting it to b/g compatible at 2.4GHz (when it works in Leopard), then to 5GHz -> invalid password. Added it to my preferred networks, hard reset of the AEBS, downgrade to 7.1.1 and a hard reset, new names for the networks, different passwords, deleted everything from the keychain to avoid any mixups, countless reboots...
No results. I just cannot connect to a 5GHz network, because Leopard claims the password is invalid.
I have no clue what to do next. It worked fine until I upgraded to 7.2.1, and now even when I downgraded to 7.1.1, it still won't work. And 5GHz works fine without a password. But as soon as you set a WPA2 Personal (this or WPA2 Enterprise, which I don't want), Leopard says invalid password.
I also noticed that when I setup a preferred network in Leopard, and insert a WPA2 Personal password, it changes it to simple WPA, without the 2, when I save it. Although this is strange, it shouldn't matter. Because when I setup a 802.11n 2.4GHz instead of 5GHz network with a WPA2 Personal password, it works great with my WPA(no 2)-preferred-network settings.
I'm completely lost here. Who can help me out?
(Just a tip: do not, I repeat, do not ! update to 7.2.1).

Hi guys. "Good" to know we're not the only ones. I reported it also, let's hope an update follows soon.
I still don't know where the problem lies exactly. Mainly because it did work for me in Leopard, after I did a completely clean install last friday. It just picked up the network and it worked. I tried 7.0, 7.1, 7.1.1 and 7.2.1 about 5 times each now. All along with complete hard resets, powerdowns and all the possible settings I could think of, nothing works. First I'd say it's probably the AE firmware, but since nothing works anymore, I'm leaning towards Leopard now...
Maybe the password isn't being sent correctly to the AE, or the respons of the AE doesn't get received properly. There already was a Keychain update right after the release, maybe there are still more updates in that area, and they'll be included with the next big update.
If anyone finds a way to fix it, let us know! I'll keep trying, although I don't think it'll do much good

Airport Express - Extreme: only 6 MBit in 5 GHz 802.11n-only mode??

Hi!
I got an Airport Express (early 2008 model) a few weeks ago that I used in client-mode (aka "join a wireless network") in my 54 MBit WLAN.
Eventually, everything worked as I wanted and I basically always got connection speeds of 48 MBit or 54 MBit.
So yesterday, I got an Airport Extreme Base Station (802.11n model with GBit-LAN) and used it to create a new wireless network.
The settings are: 802.11n only, 5 GHz, wide channels.
Using my MacBook, I can connect to the AEBS with speeds up to 270 MBit.
But when I make the Airport Express join the new Draft-N WLAN, I only get connection speeds of 6 MBit, and that's even when I place the Express 10cm away from the Extreme.
The wireless monitor (Airport Utility->Advanced) for the Extreme shows a signal strength of -30 dBm and -95 dBm noise - still only 6 MBit connection speed.
Using my MacBook, I get much worse values but much higher connection speeds.
Both Airport devices have the latest firmware and wide channels are enabled on both, too.
I'm suspecting there might be something wrong with my Express (5GHz antenna maybe?).
Does anyone have an idea? Should I call Apple?

Problem solved:
As soon as I attach an Ethernet device to the AP Express, it's MAC address shows up in the Extreme's wireless monitor with reasonable speed while the MAC address of the Express is still listed with 6 MBit.
Looks like a "feature" of the bridge mode - when I deselect "allow ethernet clients" the "real" connection speed shows up.

AEBS 802.11n, Crashing while using bittorrent

Hi, I have recently purchased an AEBS 802.11n (gigabyte ed. and using the 7.2.1 firmware) and am experiencing some problems using bittorrent.
First off, I use azureus for my torrents, and with my former linksys router I had no issues. However since purchasing the AEBS I have tried multiple torrents now, and seemingly randomly during the transfer I loose wired/wireless connectivity to my router and am unable to restore it. When looking at the actual base station though the status light is still green, but going through my mbp the device will not appear when I scan for base stations. The only way to fix this problem is to unplug/replug the router.
This happened with the first AEBS and thinking it may be an error with the actual router, I returned it. However, after unpacking the new one, configuring it... I am having the exact same issue. I haven't experienced the router crashing any other times outside of using bittorrent, so I am unable to pinpoint whether this is something random or not. However it is almost a sure bet that letting azureus run for a few minutes will crash it. Furthermore upon restarting the router, all of its logs seem to clear so I can't even begin to troubleshoot this.
I can't see how a $60 linksys router is able to outperform this very nice offering from apple, and I really would like to see this problem fixed. I hope this doesn't come down to tweaking some rare setting in the bittorrent client as I have many people that use my network weekly and it will be an increasable pain to take them through some unique setup which should not be required.
If anyone has any ideas let me know, I am fairly competition with computers and networking issues and willing to do whatever is needed to fix this. Thanks in advance.

I'm using Azureus 3.0.2.2. However this really shouldn't be an issue of client settings or what not.
The fact of the matter is, I can sit here on my friends $30 d-link, and download from BT just fine, close my laptop, open it at my house, continue downloading/seeding, and almost guarantee a crash... with the exact same settings. Furthermore how can I expect anyone on my network to dig through their respective clients settings just to use my network, and the first time someone forgets... poof router/network locked.
This is definitely a problem with the router, however I'm not sure if its a firmware or hardware issue. Hopefully this is a bug that they will be able to fix, if not the AEBS is going straight back.
I still haven't had a chance to call apple on the matter, as I am away on business... I will be returning Monday and hopefully they have some answers.

802.11n 5ghz Connection Problem with OS X 10.4.11 Tiger

I've searched the communities for answer to this vexing issue to no avail, so I am trying a post.
Situation:
I have a dual-band 1TB TC at home set up with three networks: 802.11g/b/a, 802.11n ((5ghz), and Guest Network (g/b). There are four Macs accessing it: (2) mid-2009 15" MacBook Pros, 2009 MacBook Air, mid-2006 24" iMac. All are running Snow Leopard 10.6.7 except the 24" iMac (Core 2 Duo) running 10.4.11.
All Macs can connect to to all networks EXCEPT the iMac which has a problem with the 802.11n (5ghz) connection ONLY. The iMac has the n-enabler installed (can see it registered when looking at Network Utility). In fact, the iMac will connect but any attempt to access to the Internet or TC disk stalls the system. Switch back to 802.11g and everything is fine.
I've looked at the Console for guidance but cannot find anything problematic (to my eyes, anyway). I booted this iMac to Snow Leopard from an external disk and the problem cannot be duplicated, so I am assuming this is not a hardware issue with the iMac. I also, did a fresh install of Tiger and updated it to 10.4.11 plus all Airport updates and n-ebabler on an external drive, booted from this drive and have the same issue with the 5 ghz n-connection.
By the way, when connected to 802.11n (5ghz) network with the iMac, I have full bars on the menubar fan, but then one bar drops after a minute or so. When this happens, I cannot access the Internet nor the TC disk.
I've tried various tweaks as described in the many, many discussion threads here: resets, establish new locations, clear/repair the keychain, and many others.
I did not have this problem in the past with this iMac, so don't know what has changed with the system configuration. The g-connection is rock-solid, so Internet access is fine, but file transfer speeds ober the network are obviously much slower now than with the 5ghz n-connection.
Anyone have any ideas? Without suggesting an upgrade to 10.6...clearly that should do the trick. I have other reasons for running Tiger on the iMac.
Thanks.

I wonder if all the activity was too much for the hard drive and it failed....you might contact Apple about this repair extension program to see if you qualify...
http://www.apple.com/support/macbook/hd/repairextension/

AEBS 802.11n only connects at 54Mbps?

Similar Messages

Maybe you are looking for