An Unusually Bad Experience

Huze... for what it's worth.

I believe this is an issue for ALL vendors that have implemented the beta N specification. Here is an article that I think explains what is happening.

http://www.engadget.com/2006/08/14/finalized-802-11n-specs-pushed-further-into-t he-future/

The XBOX 360 doesn't support N specification which may explain why it's having issues. The XBOX 360 is not the only "device" that is having problems. We are seeing this across the board.

I have to disagree a little about ALL vendors.

I go back to my PSP example. I had a PSP that was firmware 2.0.? (which was way before pre-N routers started appearing in the marketplace). I was able to connect to the Airport Extreme 'N using WEP and get the latest 3.x update. Whereas the 360 wireless would not connect using WEP.

WEP should work with the 360. It's the oldest protocol and well tested (and hacked 🙂 ).

Methinks that Microsoft satifised the bare minimum requirements to support the encryption protocols. And, 'N routers might make some previously optional facets of the protocols to now be required.

I definitely think it's shoddy implementation on Microsoft's part.

Personally, I just want it fixed. I guess we will see which company fixes the problem. If Apple releases a firmware update or if Microsoft includes a patch in the Spring update.

I still think it's an N spec implementation issue.

So I just got my shiny new AEBS today and was planning to replace a Netgear 802.11g router with it, but now I guess I'll be hanging the Netgear off one of the wireless ports of the AEBS and using it solely to run my XBox360, moving everything else to the AEBS. What a pain. I hope someone fixes the situation soon.

thats what i'm gonna do

This issue with the new Apple Airport Extreme is a wireless "N" spec issue. As you know, the original Airport Extremes worked fine.

Apple needs to figure out what has changed and fix it. You can't expect ALL companies to implement a wireless specification that hasn't been finalized. Yes, other companies that have chosen to implement the new "N" spec and are experiencing connectivity problems with "devices."

You can't expect ALL companies to implement a
wireless specification that hasn't been finalized.

Since my XBox 360 uses 802.11g (not "n"), and that IS an established standard, I expected that there would be no issues between the devices.

On the other hand, I also expected my shiny new 15" MBP C2D to be able to handle WPA and WPA2 encryption with my Netgear 802.11b/g router (something even my 4 year old iBook and 2 year old Powerbook G4 can both do just fine), but it can't. Had to fall back to WEP. I was hoping this new AEBS would be the magic bullet to let me upgrade the whole network to WPA or WPA2 and still give me good coverage and speeds.

I am not happy, because they censored one of my question, but there are a lot question that are not answered

SO I repeat myself so everyone knows!

- Issues with VPN, this DOESNOT work!!! unlike the old AEBS
- WDS is also a nightmare or it works but without security !!!
- USB disk does not spin down yuppeee thank you for the global warming and the eletrcity waste
- and probably some other complains

B

I just bought one of the new Airport Extremes
(802.11n) today and am having a very bad experience.
For starters, the new Airport Utility is crashing
all the time on my iBook. Second, I am having
trouble getting a few devices in my house to
recognize the network I have created (Specifically
the Xbox 360). Third, I cannot establish a WDS
connection between my old Airport Extreme and the
new one. I am not very familiar with creating and
setting up complex wireless networks, but I didn't
have nearly as much trouble with the old one. Any
help would be appreciated.

14 in. iBook G4 Mac OS X
(10.4.8) 1.5GB RAM 60GB HDD 1.42GHz
G4

Okay so here's what I can add to this. Exact same issue. New 'n' station, no Xbox 360 connection. I'm not willing to run without encryption so I set up the 'n' station as a master WDS station and set the encryption to WEP (Trans). No option to select the 128-bit and what not. I imagine that this reason is why the Xbox can't connect. Apple seems to have changed the WEP transmission/encrlption and since you can't force it to use 128-bit or lower no go. But I digress, I have my old station set as a WDS remote and of course match the network name but tell it to use 128-bit WEP. Bingo. The Xbox connects to the old station with the old setup that works just fine. Xbox live works and all is good. I have not tried to create a closed network but since it's running off my old station in WDS mode things are good. Guess we'll all have to wait for an Apple update or a 360 update to get WPA.

Set up the 'n' station first and have the WDS set as master. Set the encryption to WEP but remember the key MUST be 13 characters long for ACSII or the 360 won't like it. Then set the old air station up (with the old Admin utility) with the network name you want to extend, the same WEP passkey but make sure it's set to 128-bit. Then set it so that it doesn't give out a DHCP address. Just de-check the box in the network tab that says "Distribute IP address". This worked for me Live works and my PSP and PS3 connect no problem as well. If it works, you can even up the old station closer to the Xbox and get better signal.

Until a fix is released by somebody (M$ or Apple), here's what I did and it works like a charm:

I set up a new network (Zenith) using the new AEBS and WPA on all the machines in my network EXCEPT the XBox360. This mixed network is a desktop PC connected via ethernet, two desktop PCs in my kids' rooms, an old iBook in my youngest daughter's room, my wife's Powerbook G4, and my MBP C2D.

I then configured the AEBS to assign a fixed IP to my old Netgear router and stuck it in a DMZ (e.g., open and unprotected by NAT) by using the NAT tab and selecting the "Enanble default host at:" box and entering that fixed IP address.

I then connected the Netgear router's Internet port directly to my laptop and logged into the configuration page. From there I created a new wireless network (Nadir), told it to accept an IP from it's internet port (which would later be connected to the AEBS), and told it to assign a fixed IP for my XBox360. I then told the router to assign that IP to its DMZ. I also enabled remote management which allows me to log into it from any other computer on my LAN through it's "Internet" port (the one connected to the AEBS).

Finally, I connected the Netgear's "Internet" port to the second ethernet jack on the AEBS. I then turned on the 360, setup the new network SSID and WEP password and ran the network tests. I got a perfect connection, even getting an "Open" result on the NAT tests through two different routers. Haven't played any online games, but I had no trouble connected to XBox Live and downloading an Arcade demo had excellent throughput.

So far, my mixed b/g/n network with the AEBS is working great and I can FINALLY use my Canon IP5000 printer without having to connect to it directly.

Wow, that's a lot of steps, but hey if it works that's all that matters. I was just lucky I hadn't told any of my friends that I would soon have an extra base station...now I can keep it.

I'm going to give this a try tomorrow...

I have an Airport Express (I use to use it in my old house because I had a machine 3 floors away). I'l just add that on to my Extreme 'N network until something gets fixed by Apple or Microsoft.

I let you know how I make out...

iMac G5, Powerbook G4 1.5 12 Mac OS X (10.4)

Great. I'll keep track of the post. If I can help I'll try.

Apple called me back today. The service rep wanted to confirm that I had tried to connect with security disabled (I had and it was successful). With that confirmation, he is now taking my case to the engineer and will call me back on Sunday with further details.

I did ask him if others had been calling in and if Apple was considering issuing a firmware update. He said it appeared that it was headed in that direction, but he couldn't confirm anything official at this point.

As a sidenote, this is my first experience with Apple Customer Service and I'm absolutely blown away at how dedicated they are to making sure I'm happy. So far, a big thumbs up from me.

Alternatively if you option-click on the transmit mode in the airport utility you can turn off the 'n' transmit and make just a g network like the old airport. I came across this in another post and while I don't know if the connection issues are solved that way I can verify the drop down give more options when option-click is used.