Airport extreme base station no longer recognizes password

Away from house for a week. Came back and none of our iPhones, iPads can connect to wifi network. Airport Extreme base station will no recognize my network password to check settings. Airport Epress will not join network either.

Hi danny_A1A!
I have a couple of articles here that should be able to help you troubleshoot this issue. The first is a quick assist article pertaining to Wi-Fi issues and can be found here:
Wi-Fi Quick Assist
http://support.apple.com/kb/ht1145
We also have another article on troubleshooting Wi-Fi connectivity, and it can be found here:
Wi-Fi: How to troubleshoot Wi-Fi connectivity
http://support.apple.com/kb/HT4628
Take care, and thanks for visiting the Apple Support Communities.
-Braden

Similar Messages

Airport Extreme base station no longer playing nice with Mac Pro

This is a strange problem...
I have an Airport Extreme base station (purchased in 2004) that I use with verizon DSL to get a wireless network going in my house, and I connect three computers wirelessly.
I have an ipod touch and toshiba PC laptop that are both able to connect to the network and run just fine. But lately (past 2 weeks or so) when I try to connect with my MacPro desktop I can go to a few sites, but after a few minutes the airport locks up. At that point none of my computers will connect and I have to unplug and then replug the airport. At that point the network will start up again and if I do not try to get on with Mac Pro then things run fine, but when I try to connect with desktop again, after another few minutes the same thing happens.
I know the problem is with the airport and my Mac Pro - I have done numerous connection experiments and have narrowed the problem down to that.
Is it possible that my MacPro might be drawing more power and causing the airport to overheat? (it is rather hot in the room with DSL connection)
Or should I accept that the current base it old, and bite the bullet and get a new base?
Any thoughts?

Could you post what you did in order to resolve the issue. I'm having a problem with the base station in that I cannot connect to the internet with my laptops (a mac and pc) while I can connect wirelessly to my network with my desktop (G4). The base station is not detected in the base statin admin utility or the aiport setup utility. If anyone else has a solution I would be much obliged to read it.
Thanks!

Airport utility no longer recognizes my Airport Extreme Base Station, which had been set up to extend a wifi network

Hi. In November I set up my airport extreme base station (5th generation I believe) to wirelessly extend the wifi network we use at home to see if it would increase download speeds. Before doing that, I did a factory reset of my airport extreme, and the owner of the airport extreme to which the ethernet cable is attached made changes to his network to allow it to be extended. I folllowed all the directions from the apple support pages, and finally got it to work. I could even access a portable hard drive which I attached to the airport extreme base station being used as the extension. Then a week or so ago I noticed that my laptop would no longer connect to my base station. I did not have time to look into it until this week. Airport utility, either on my Mac or iphone no longer recognizes my base station. My mac is running OS X 10.10.1 and my iPhone is running iOS 8.1.2 I have tried both hard, soft and factory resets of my base station to no avail. The only thing that has changed after doing that, is that when I do a soft reset of my base station, a neighbors airport express appears when it never did before. I can't actually connect to it, but it does try. Then after approximately 5 minutes, it disappears from my list.
Today I went and pulled out my OLD AIRPORT EXTREME base station... you know, the one that looks like a space ship and is running wifi 802.1 b/c? airport utility DOES locate and display that, but airport utility returns a message stating that it cannot be set up by this software. I am attaching an image of that.
Thank you,
John
Does this have anything to do with the fact that 'Back to My Mac' is probably enabled?

I think the initial problem is that your iPhone was connected to an open network that wasn't yours.
Go to Settings > WiFi and "Forget" the network created by that AirPort Extreme, it's older than dirt. Forget your neighbor's network also.
Perform the equivalent actions with your Mac: System Preferences > Network > Wi-Fi > Advanced... Delete every network that appears, including your own.
Then, connect to your own network on all your devices, after which you ought to be able to use any of them and configure your Extreme without any difficulty. You may need to start over with a "hard reset" on both the main AirPort Extreme and the one extending its network.
Does this have anything to do with the fact that 'Back to My Mac' is probably enabled?
Not exactly, but using iCloud Keychain will populate all your devices with the names of preferred networks that any of them connect to, no matter where they are. I don't know why Apple considers that a beneficial feature.

HT1218 After a recent iTunes update attempt iTunes no longer functions and the airport extreme base station is not accessable on our computer. We still have wifi but cannot access the base station software.

After a recent iTunes update attempt iTunes no longer functions and the airport extreme base station is not accessable on our computer. We still have wifi but cannot access the base station software.

Thanks for the reply. I appreciate the response. I tried that approach this evening and it didn't work for me. (Technically it worked for me, when I was hardwired into my base station, but would not work for me wirelessly, which is my main issue.)
Again, using the approach you recommended works only if I have my ethernet cable attached to the LAN port so my computer is communicating directly to the base station through the hard wire. I am able to scan for my base station and make setting adjustments normally this way too.
As soon as I disconnect from the LAN port and try to go wireless is where I run into problems. The Base Station's wireless network I created is available to choose in the top right corner of the monitor with all of the other available wireless devices/networks -- but the network I created does not have access to the internet. I am also unable to configure my Base Station wirelessly. When my Airport Utility tries to scan for the Base Station and Network, it cannot find any Apple Wireless Device. It's like the Wireless Network in my base station is not sending out a signal.
Is there a way to resolve this issue?

Why can I no longer print from my Windows XP computers to my Bonjour connected Canon printer thru an Airport Extreme Base Station (f/w 7.6.4, model A1301)?

Something has changed recently and I haven't figured it out. My 2 Windows XP computers are no longer able to print via Bonjour. I have tried removing and reinstalling Bonjour. Upgrading the firmware on the AIrport Extreme Base Station and comparing Port settings from an able to print Windows Vista laptop. Port settings match and Bonjour says it sees the printer...but the communication is not happening between the computer and the networked printer, it times out and produces an error in the print que. Both XP computers have no problem using the internet via the Base Station. One is wired and one is wireless. Thoughts?

Sounds a bit like a problem being discussed in this thread:
http://discussions.apple.com/thread.jspa?threadID=2651093&tstart=0
I suspect some kind of update is at fault. Like you, my printer/base station setup had been working fine until recently.

I have a airport extreme base station and i reset it and now the wifi connection is open to everyone... so how do i get a password back on it so everyone cant use it

i have a airport extreme base station and i reset it and now the wifi connection is open to everyone... so how do i get a password back on it so everyone cant use it

Read the user guide:
http://support.apple.com/manuals/#airport

Problem consistently printing via new (summer 2011) AIRPORT EXTREME BASE STATION and Brother wireless printer (model HL5370DW). What am I doing wrong?

Thanks in advance for any help you folks can offer. I'm a newb here and will try to offer as much detail as I can about the dilemma at hand.
Scenario: Home network has been recently set up for wireless internet access via NEW Airport Extreme Base Station (purchased September 2011). Units accessing the network include: 2011 Macbook Pro, 2011 Macbook Air, 2007 Macbook, 2009 Macbook Pro, 2 iPhone 3GSs, and a 1st-gen iPad (and a partridge in a pear tree AEBS is configured to run WPA2 encrypted network, as well as a WPA2 guest network. I am attempting to yoke a BROTHER HL5370DW wireless B or G/ ethernet / usb-capable printer to the main network such that any and all units can print wirelessly or its equivalent (i.e., via printer hooked to AEBS through USB hub)
Problem: Despite configuring the Brother printer to recognize the main WPA2 network I created, I am unable to get wireless printing to work. My workaround was to physically connect Brother printer to AEBS via USB, specifically using a Belkin USB hub (after all, I wanted access to usb drives, as well as the printer). This workaround works ONLY SOME OF THE TIME. Generally, after a fresh boot of any computer or after a restart of the AEBS, any given computer will be able to print (i.e., any computer wirelessly connected to the main WPA2 network recognizes the printer). HOWEVER, at random times, printer access is gone (as is access to USB drives connected to AEBS's usb hub). Wireless networks are still up and running when that happens. IS THERE A WAY TO GET THE USB HUB's devices (i.e., printer and usb drives) to ALWAYS REMAIN AVAILABLE AS LONG AS THEY STAY CONNECTED TO THE AEBS? In other words, what accounts for the intermittent loss of the usb peripherals?
Sometimes, I just shut the airport off on whatever computer is having this problem, and the problem goes away. Sometimes, the problem is present across all computers in the house, sometimes only a few are affected. I can ALWAYS see the AEBS in the Airport Utility if the AEBS is connected to the particular computer via ETHERNET CABLE.
My theories:
- true wireless printing (i.e., without usb hub workaround) doesn't work because the N network somehow isn't backwards compatible with the Brother printer, which, i believe, is B/G. Although...isn't Wireless N networking supposed to work with BG devices? I did find a thread (https://discussions.apple.com/thread/2570774?start=0&tstart=0 ) that explains some of the particulars of WPA2 encryption and Wireless B/G issues, but it was beyond my level of comprehension (I'm a psychologist, but not an Apple Genius
- The usb workaround is only intermittently viable because of some flaw in the Airport or Airport Utility that causes dropouts to happen when a Macbook Pro or Air's lid gets closed or one gets opened after having been at a different network (e.g., at my office).
QUESTIONS:
- Should I try to use my old router (7 year old Linksys WRT54G) as an access point and connect the Brother printer to that G-router? How do I do that?
- I wouldn't mind just relying on the usb hub method if I could just insure more consistency (i.e., no random dropouts of peripherals). How could I do this?
Rule out:
- wireless printing works on my printer - it was being recognized back before the AEBS. I had the Linksys router running a WEP network and had the wireless printer talking with no cables to the router and the computers. (I just don't want to revert to using WEP encryption given its lack of security and my trying to protect HiPAA related health information on behalf of patients)
Any help will be greatly appreciated.
Thanks in advance!

13 ASCII characters = 104 (aka 128)-bit WEP
encryption
If turning off WEP works, then you just need to
provide the cameras with the "Equivalent Network Password".
One of the problems with WEP is that the actual
standard relies on a 10 character HEX key for 40bit
WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier, vendors use certain
algorithms to convert simple alphanumeric passwords
(or passphrases) into HEX keys, thus enabling the use
of simple easy to remember WEP password rather than
lengthy HEX keys. The problem is that different
vendors use different algorithms to generate the HEX
key and therefore a ASCII password on an AEBS will be
hashed differently on a non-Apple client and vice
versa.
You may find the following article helpful:
- Apple article, especially the part about
"Third-party client to Airport".
Brilliant idea about trying the system with No encryption on... that DID solve the problem... almost.. once I turned off the encryption option, and restarted the Airport, I got a dialog box showing that the "Base station needs attention" but it didn't indicate WHAT kind of "assistance" it needed. Nonetheless, I closed out of the Airport program only to find that the indicator light, which had been Green, was now, flashing Yellow and I could not connect anything, including my computer. I opened the Airport program again and found the ONLY way I could get the Green light on was to select some sort of encryption option... then the light would go Green again but my cameras would not hook up again, and when I went back in and ONLY changed the option to NO encryption, I got the yellow flashing light and the "this base unit needs attention" warning...
I think your suggestions are almost on the mark... is there any way of reconciling the WEP coding between the cameras and the Airport??? Or turning off the encryption option and STILL have Airport work?
Thanks again for your help and suggestions... I really appreciate it.
geoff

Solution to Airport Extreme Base Station + Airport Express networking probs

I've been investigating this for 3 straight days after inadvertently destabilizing my network. There are tons of posts discussing a variety of issues, all of which seem related. My goal here is to provide links to other relevant posts and explain what I ended up doing to get things to work.
First, the background. You can skip below to SOLUTION if you don't really care... However, I highly recommend you take the time to read everything, as you'll get other useful information in the BACKGROUND section. I'm guessing many of you have similar, related problems so BACKGROUND might help provide context (and solutions) to some things you are seeing...
MY SETUP:
AirPort Extreme Base Station (AEBS) of type b/g (round one, not square one), connects to the cable modem, and creates a WDS network that is then shared across two standard AirPort Express (AEX) units (100megabit, not the gigabit ones). One AEX serves as a relay unit that accepts clients, the other serves as a remote unit that also accepts clients. The intent is to show a single network throughout the house and let users log on to one network and move between networking units without having to switch from network to network.
I have a variety of networked devices throughout the house all running on the same network (2 Mac Pros, a Powerbook G4, a Mac Mini, an Apple TV, a Windows XP laptop, two iPhones, two wifi printers, and a 5-unit Sonos system, plus the AEBS and two AEXs). Yeah, I'm a geek.
The Mac Pros are both running 10.4.11, and the Powerbook is running 10.5.2.
AEBS is running firmware 5.7
AEXs are running firmware 6.3
All Macs were initially accessing configs via the recently released AirPort Utility 5.3.1. More on that later.
BACKGROUND:
I've had this network setup working for about a year now. Recently, I've been having poor network performance problems and came to the conclusion it was a LAN problem (ie. problem with my home network, as opposed to with my ISP). Upon initial investigation, I began by looking at my networking logs (via AirPort Utility 5.3.1). You get to those by selecting the unit in question, choosing "Manual Configuration", the selecting the "Advanced" tab up top with the "Logging and SNMP" sub-tab. Click the "Logs and Statistics" button therein for log details from that unit.
The first thing I noticed was "Administrative access denied to ff80::xxxxxxxxx" messages - a lot of them. I didn't recognize the ff80:: address in question, and so became concerned it was someone outside the network trying to hack one (or all) of the AEBS/AEX units. You can see threads discussing that investigation here:
"Hack or panic?" - http://discussions.apple.com/thread.jspa?threadID=1438486
"Administrative access denied" - http://discussions.apple.com/thread.jspa?threadID=1438865
Long and short of it is that the recent AirPort Utility 5.3.1 release (current as of March 13) seems to have problems (keychain) when attempting to access the AEBS and AEX units. The "Administrative access denied" logs actually refer to the client machine you are using when you try to read the logs. The ff80::xxxxxx address is simply the IPv6 address for the machine you are using; if you turn off IPv6 on your client machine, that address should switch over to begin showing a regular IP address instead (something like 10.0.1.xxx), which makes it easier to associate the IP to the machine. I explain how to deactivate IPv6 on both Tiger (10.4.x) and Leopard (1.5.x) here:
http://discussions.apple.com/thread.jspa?messageID=6814978#6814978
Anyway, in the process of investigating the "Administrative access denied" problem, I began tinkering with my AEX settings. Specifically, I ended up performing a hard factory reset (unplug unit, plug back in while holding down the little button with paper click/pen for ~10-15 seconds until light flashes green 4x then reverts to amber/yellow/orange). I began reconfiguring my entire WDS network using the newly updated AirPort Utility 5.3.1, and that's when the trouble started.
(If you are having problems seeing either your AirPort Extreme Base Station or AirPort Express, read this:)
In short, each time I thought I had properly configured things and then confirmed settings (kicking off a reboot on the AEX unit) the unit would restart with new settings but not properly join the WDS and not show up in the AirPort Utility list of units. More specifically, I would start with a "wiped" AEX and see both the AEBS and the AEX in my AirPort Utility list, but upon confirm/reboot the AEX would disappear and the AEBS would remain. However, that's not 100% correct. It seems that sometimes I would end up with the AEX and NOT the AEBS. Because both the AEX and AEBS were theoretically "hosting" the same network name (remember, WDS shares the network name across units) my auto-login feature for my client computer's wifi seemed to "jump on" whichever unit it first saw hosting the default network name for my house. In other words, it seems what was really happening was that I was ending up with two separate networks in my house, both with the same name but not talking to each other (as opposed to two units sharing the same network name and internet connection). The AEX would continue to blink orange/amber/yellow (whichever color it is to your eyes ) because it could not grab an internet connection -- and if I was on the network through that AEX unit I would not get internet. But if i was connected through the AEBS I would continue to have internet access. As far as my client computer (my Mac Pro) was concerned, I was on the home wifi network even if I was on the AEX rather than the AEBS -- it would show the home wifi network name as the name of the network it had connected to. But when I opened the AirPort Utility 5.3.1 I would see only the AEX (if I was connected through it) or the AEBS (if connected through it) -- a clear indication that the units were not truly sharing the same network.
I tried rebooting and reconfiguring the AEBS and AEX about 50 times (literally). I even tracked down an older version of the AirPort Utility 5.2.1 via this thread (see Tesserax post):
http://discussions.apple.com/thread.jspa?threadID=1067565
One interesting thing re: 5.2.1 is that the "Administrative access denied" errors summarized above disappeared. As explained in a post reference above, the going theory is that this a permissions/keychain problem new and unique to AirPort Utility 5.3.1. However, even though 5.2.1 does have a slightly different interface with different settings, I still couldn't get the WDS to work.
EVENTUALLY, I came across this post:
http://discussions.apple.com/thread.jspa?threadID=1422527
MuaddibOfArrakis walks through setting up a WDS from scratch, and the workflow is different than what is possible with either AirPort Utility 5.3.1 or 5.2.1. He's doing it with the old version of AirPort Admin Utility, which I fortunately saved a copy of many moons ago when I had somewhat-related problems with my WDS (since forgotten). In fact, it's a lot easier. What's nice about this older app is that it literally does the heavy lifting of "connecting" the AEBS and AEX units during the configuration -- it reboots both at the same time as the config is happening, and lets you choose from a list of available units to "add" to your WDS network. In short, it's a FAR SUPERIOR workflow even though some of the GUI isn't as intuitive as the newer AirPort Utilities that were designed to replace it.
SOLUTION:
If still have a copy of the AirPort Admin Utility follow the instructions from MuaddibOfArrakis here:
http://discussions.apple.com/thread.jspa?threadID=1422527
If not, try setting up your WDS network using AirPort Utility (hereafter AU), with these configs (take from my now-working network), as viewed through AirPort Utility 5.3.1.
I. Configure your AEBS.
Select the AEBS from AU, and choose "Manual Setup"
1. Under the AirPort tab up top:
a. Under "Base Station" sub-tab:
i.) assign a name for that specific unit, so you can later identify the specific unit from the list of units -- this is the name that will show up beside the unit in the AU list of configurable units. You can name it something like "kitchen", or "office". I have mine numbered, so XXXXXv1, XXXXXv2 etc where the XXXXX is the name of the shared network and the numbers help me tell the units apart. Just be sure you name each uniquely, and if you have several you might write the name on the unit itself.
ii.) pick a password for logging into that unit. This is different from the network password, its a security check to get in and change the configs on this unit later. Be sure to remember it in your keychain for the sake of simplicity, and write it down somewhere secure.
iii.) if you choose to set time automatically, pick a location that you will use consistently across all your units. I use time.apple.com.
iv.) uncheck "Allow configuration over Ethernet WAN port" unless you want to be able to remotely mess with settings -- which you almost certainly do not need to do.
v.) I left the "Options" button alone - no settings there.
b. Under the "Wireless" sub-tab:
i.) Wireless Mode: "Participate in a WDS network"
ii.) Network Name: this will be the name of your wifi network shared by all units, so be sure to remember what you pick. If you are already connected to this AEBS via wifi while you are making these changes, then you can use the same wifi name you already have set up -- you don't have to change it. Note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
iii.) pick a Radio Mode. I'm using b/g compatible. You'll want to do the same, unless you are on the new gigabit AEX. I'm pretty sure about this, but not 100% -- others post if I'm wrong.
iv.) choose a Channel. This can be a more complicated procedure, but for now just pick something consistent across all your units. If you get everything working and find that you're having intermittent network problems, you could later try changing your Channel -- it can pick up interference from phones, microwaves, etc and changing it can help.
v.) I have wireless security set to WPA/WPA2 Personal.
vi.) Wireless Password is the password for access to your wifi network (not your unit itself). If you are connecting to your AEBS via wifi while doing this config, then you can use the same password you have already set up. Pick a good one unless you want other folks jumping on your wifi and stealing your bandwidth and/or credit card numbers . Remember it in your keychain and write it down someplace secure, because you'll need it for the other units too. As noted above, note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
vii.) Click the "Wireless Options" button. I have my multicast rate set to 2mbps, transmit at 100%, timeout at 1 hour, and i have checked the "Create a closed network". This last step keeps your network from advertising itself to the outside world. Users can only find it by explicitly typing the network name into their wifi settings (e.g. AirPort -> Other... then enter Network Name, Security and Password). I leave interference robustness unchecked.
c. Under the "WDS" sub-tab:
i.) the AEBS should have it's WDS Mode set to "WDS main".
ii.) Check the "allow wireless clients" box on the AEBS; this lets you connect client machines to it directly too.
iii.) hit the plus button to add the Remote system (AEX). There are two types of configs for the AEX's - "remote" and "relay". Assuming you have 3 units like me (2 AEX and 1 AEBS) the key question is whether you will place each AEX within direct reach of the AEBS (remotes), or if you will have one AEX in the middle connecting to an AEBS on one side and an AEX on the other -- where the furthest AEX is out of reach from the AEBS (remote) and connects only to the AEX in the middle (relay). I'm using a relay setup. If you are using relay, you can still set up the AEX relay to serve client computers too -- it doesnt have to JUST relay. More on that later. For now, you want to add only AEX units that will talk DIRECTLY to the AEBS. So if you have a setup like mine, just add one (the one in the middle - the relay). If you have two remotes connecting directly to the AEBS, you will add them both here. When you hit the '+' button it will ask for both an ID and description. For description I use the name I'm assigning to each unique unit (as above, "kitchen" or XXXXXv1 or whatever you use). For AirPort ID, use the number listed on the AEX unit itself (not the number for "Ethernet", also on the AEX unit).
d. Under the "Access" sub-tab:
i.) I have it set to "Not Enabled". I'd suggest you start that way too, and you can go change it later if you get everything working correctly.
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: Ethernet
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Share a public IP address
b. Under the "DHCP" sub-tab:
i.) DHCP Beginning Address: 10.0 . 1 . 2
ii.) DHCP Ending Address: 10.0.1.200
DHCP Lease: 4 hours
c. Under the "NAT" sub-tab:
i.) nothing should be checked;
ii.) nothing under Port Mappings either
3. Under the "Printers and Advanced" tabs up top:
Nothing special needs to be configured there.
THAT'S IT.
=============
I. Configure your AEX(s)
Select the AEX from AU, and choose "Manual Setup"
1. Under the "AirPort" tab up top:
a. Under "Base Station" sub-tab:
i.) pick a unique name for this unit, same logic as for AEBS
ii.) pick a password specific for accessing this unit, same logic as for AEBS
iii.) Set time automatically: be sure to use the same settings used on your AEBS
iv.) Options: no need to set any
b. Under "Wireless" sub-tab:
i.) Wireless Mode: Participate in a WDS network
ii.) Network Name: same name used for AEBS, this is the name of your wifi network
iii.) Channel: same as AEBS
iv.) All settings here (those above, plus Security and Password & in Options button) should be the same as for AEBS settings on this tab
c. Under the "WDS" sub-tab:
...if AEX is "in the middle" (as described above):
i.) WDS Mode: WDS relay
ii.) Allow wireless clients: check (unless you only want to bridge between the edges without letting folks connect on this AEX in the middle)
iii.) WDS Main: set to the AirPort ID (aka MAC address) for the AEBS. You can find it on the bottom of the AEBS, either labeled as such or at the bottom beside the logo of a wireless signal (square logo, with semi-circles mimicing a radio signal).
iv.) WDS Remotes: click the '+' to add any AEX's that will connect to this relay rather than directly to the AEBS. Same deal as above, use the name in the description and use the AirPort ID from the side of the AEX (not the Ethernet ID).
.....if AEX is connecting to a relay ("on the end", as above) or if there is no relay and AEX connects directly to the AEBS:
i.) WDS Model: WDS remote
ii.) Allow wireless clients: checked
iii.) WDS Main: if connected to a relay, use the AirPort ID of the relay AEX. If connected to the AEBS directly, use the AirPort ID of the AEBS
d. Under the "Access" sub-tab:
i.) MAC Address Access Control: Not Enabled (for now, you can change later)
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: AirPort (WDS) -- should be selected and gray'ed out.
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Off (Bridge Mode)
3. Under the Music, Printers and Advanced tabs up top:
Nothing special needs to be configured there. You can worry about AirTunes settings later...
That should be it. I'd recommend setting up the AEBS first, then the relay (if applicable), then the remotes. Initially, you can bring each unit in the same room with you for configuring. After configured and restarted the AEX should blink then turn solid green. If it turns green you should be good to go.
HOPE THIS HELPS. As noted above, I did not config through AirPort Utility 5.3.1 so I haven't tested this procedure through that app. However, after getting my network to work I went back and transposed all settings into this post to help others. Please provide feedback on whether or not this is working, so we can collectively try to move towards a setup procedure that works for everyone....
Good luck!
Message was edited by: b.byrd

I'm not convinced that the problem lies in Airport Utility. This same thing was happening to me, nearly exactly as you describe it. The thing is that with me, the problems clearly started when I updated the firmware in my Airport Express (n). That's when all the wacky stuff started happening. Sometimes it would show up in AU, sometimes it didn't and even if it didn't, I could still access the internet through it.
But as you said, the problems got really bad when another Express (b/g) was put on the network with it. Even when it did work, the (b/g) would make it impossibly slow.
You know more about this than me, and clearly have more patience if you've restarted the network fifty times. I gave up at about ten.
In any case, your solution is more of a work around and if you're still having that slow connection problem, I'm not sure you've got it. But thanks for your reporting of this. At least I know I'm not crazy.

Third party Device connection to Airport Extreme Base Station

I have a new Airport Extreme Base Station (AEBS) that my iMac is wirelessly connected too. I cannot connect my HP wireless printer to the AEBS. The printer recognizes the SSID and WEP password, but does not have a connection & does not print.
I also, cannot connect a Netgear Wireless Bridge for (xBox) to the AEBS. The xBox does not see the SSID at all. What do I do??? I purchased the AEBS because the salesman said it would be the easiest wireless network ever, but I only have problems ! ! ! ! ! ! !
Aaron
iMac G5 Mac OS X (10.3.9)

Very likely a WEP issue.
If you turn off WEP can you now connect and print?
One of the problems with WEP is that the actual standard relies on a 10 character HEX key for 40bit WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier for people, vendors use certain algorithms to convert simple alphanumeric passwords (or passphrases) into HEX keys, thus enabling people to use simple memorable WEP password rather than lengthy HEX keys.
The problem is that different vendors use different algorithms to generate the HEX key and therefore a ASCII password on an AEBS will be hashed differently on a Netgear client and vice versa.
One thing is a 13 character 128 bit WEP password will be hashed by all vendors in the same way (if you use 40bit WEP then a 5 character password is required).
Though sometimes not even that works and the HEX key must be used regardless.
AirPort: Joining an encrypted wireless network
http://docs.info.apple.com/article.html?artnum=106424
Choosing a password for networks that use Wired Equivalent Privacy (WEP)
http://docs.info.apple.com/article.html?artnum=108058
iFelix

Airport Extreme Base Station as Extender to Airport Extreme Time Machine

I have tried this a few times, but to no avail: Tonight I purchased an Airport Extreme Base Station (AE) to set up as an extender to my Airport Extreme Time Capsule (AETC). The Airport Utility finds the router and goes through set-up seemingly fine, with green lights on both. Then shortly after (within a minute) the AE reboots on it's own, followed by the AETC rebooting (again, on it's own) and this occurs repeatedly. I reset the AE completely and run through the set-up and the same thing occurs. I've also done soft resets to the AETC. Long and short of it - the restarting discontinues once I unplug the power cord from the AE. Then the AETC resumes as it has - providing fine wifi and speed. It appears the AE rebooting on its own makes the AETC reboot. Any ideas? Thanks!

howto - extending airport 802.11n networks
Pre-Requistites
1) Ensure all have most recent firmware - 7.7.3 for AC devices, 7.6.4 for 802.11n devices
2) Have most recent Airport Utility (OS X 10.7 thru 10.9, use 6.3.2, IOS6/7 use 1.3.3)
3) Only have the Primary Airport/TimeCapsule powered on for now
Set up the Primary/Anchor Airport Base Station
1) Do this over ethernet - ensure that the Modem and TimeCapsule/Airport is connected on the WAN port
2) You'll be prompted by Airport Utility to name the Network and the Base Station
Network is the SSID of the Wireless LAN
BaseStation is the name of the Airport/TimeCapsule
3) You'll be prompted for a password - this will be for both the WLAN and the Base Station on initial setup
Note here - there are at least three passwords to worry about post setup
a) BaseStation Management - in this how-to, this will be carried thru to the extended basestations
b) WLAN Access
c) Disk Access for TimeCapsule and AirDisk
They can be same or unique, up to you...
Configure the Airport/TimeCapsule for WiFi/Network
4) Select the named BS in Airport Utility - click the 'edit' button
5) Review 'Base Station' Tab
5a) BaseStation Name
5b) BaseStation Password - you can change this now if desired, this does not affect WLAN password
6) Review Internet Tab
6a) set as appropriate for your network - e.g DHCP or other depending on needs
6aa) focus here is getting the primary BS set up first
6b) Click Internet Options - this is IPV6 setup - for now...
6ba) Set to Link-Local Only, click save, you can go back and change this later if needed
7) Go to Wireless Tab
7a) Set Network Mode to "Create a wireless network"
7b) Check Wireless Network Name
7c) Wireless Security - recommend WPA2 Personal - this is important as you'll need this later
7d) Wireless Password - the password entered in step 5b above is what is used here, feel free to modify or not - if so, note this
7e) disregard Enable Guest Network for now
7f) Click Wireless Options
7g) ensure 5Ghz network name is unselected
7h) Country as appropriate - since I'm in California, I choose United States
7i) Leave 2.4Ghz and 5Ghz Channels as "Automatic" for now, click save if needed
8) Click Network Tab
8a) if this is your primary router - use DHCP and NAT
8b) Click Network Options
8c) DHCP Lease - I use 12 hours
8d) IPv4 DHCP Range - every here is a bit different, but my recommendation for most folks
192.168.1.100 to 150
Use what works for you, keeping in mind that the AP Extreme, TimeCapsule, and 2012 Airport Express can handle 50 clients, max
8e) Ensure that Enable NAT Port Mapping Protocol is selected
8f) can worry about Enable default host at: [] later, this is the DMZ'ed host
8g) can choose to enable IGMP Snooping or not - doesn't affect the primary setup
8h) click save
TimeCapsule Only - for Airport Extreme, worry about AirDisk later
This is TimeMachine support, along with FileShares
9) Select Disks - you should see a partitiion named "Data"
9a) ensure that Enable file sharing is selected
9b) ensure that Share disks over WAN is unchecked for now
9c) Secure Shared Disks:
Choices here -
device password - noted in step 5b above
disk password - this will be for all LAN clients that can see the Data Partitiion
accounts - you can set up separate users and passwords - this is beyond scope of this how-to
Recommendation if using as TimeMachine only, use a disk password - note this as you'll need it for timemachine on the clients
Save Settings to the Airport/TimeCapsule
10) Click the "update' button
The Airport/TimeCapsule will restart
Everything now should show green and shiny - open a web browser and attempt to go to Apple/Google/Yahoo, to ensure that you've got network connectivity
Reviewing things in the Airport 6.3 utility, you should see your base station and the Internet - both with green status
Once done here, let's extend the Wireless Network
Note - again, it helps to be connected to the primary base station on ethernet, wireless makes things, erm, challenging
11) with another decive - Mac/iPad/iPhone/iPod Touch or PC, ensure that Wireless LAN is working on the primary AP/Basestation
Once this is done, then proceed to the next step
Enable the "Extended" Airport - can be another TimeCapsule, Airport Express or Airport Extreme
For purposes of this discussion - assume all ore 802.11n capable at a minimum, so this applies towards more recent gear
a) Airport Extreme AC (2013)
b) Airport TimeCapsule AC (2013)
c) Airport Express 2012 Dual-Band (Looks like AppleTV)
d) Airport Extreme 802.11n 5th Gen, TimeCapsule 4th Gen
e) Airport Express 802.11n - similar to the 802.11g variant, looks like a MacBook Pro power adapter
Assumptions here is that the extended airport is factory defaults - see link below for more info:
http://support.apple.com/kb/HT3728
Once this is done, plug in the Airport that is intended for extending the wireless network
after about a minute or so, you should see a blinking orange light, this is normal...
In Airport Utility, you should see in the upper left hand, "Other Wi-Fi Devices (1)" - click this, if you don't see this, exit and restart Airport Utility
12) clicking on the button, you should see an entry menu as "Airport Extreme xxxxxx", select this
13) Once selected, you'll see "This Airport Extreme/Express/TimeCapsule will be set up to extend "Primary Base Station"
14) Enter the name for this base station - it should be unique from the name of the Primary noted in step 5a
15) Click "next"
16) Should see "setting up this base station to wirelessly extend..."
you'll see some progress messages.. this is the two basestations handshaking....
If successful, you'll see the BaseStation named in step 14 as "is now wireless extending "base station named in (step 5a)"
STOP - the Airport is now extended, repeat steps 11 thru 16 for each addtional Airport
For advanced features - such as port forwarding, DMZ, IPv6 Tunnels, Back to my Mac, etc - perform this only on the Primary Base station outlined in steps 1 thru 8h
Good Luck!

Airport Utility does not see Airport Extreme Base Station

Purchased Airport Extreme yesterday at Apple Store to replace old Netgear Router. Wanted wireless network to work with 2 identical HP Laptops running XP with SP3 and 2 iPod touches, and possible future purchases of iPad 2 and Apple TV. Installed Airport Utility software from CD on Dell Studio running Windows 7. Connected Airport Extreme to cable modem and Dell Studio. Ran Airport Utility software to configure Base Station but it did not recognize the Base Station. Base Station had blinking amber light. Did have internet connectivity on Dell Studio, and wireless internet connectivity on 2 iPod touches, and on one HP Laptop. No wireless internet on other HP Laptop. But wireless internet connection was unsecured and Airport Utility did not see Airport Extreme so could not configure it to make it secure. Contacted Apple Customer support. After 30-40 minutes of attempting several different possible fixes only able to use Airport Utility to configure Airport Extreme remotely, wirelessly, from one HP Laptop, not the Dell Studio that is directly connected to the base station. Now that the base station is configured the network is secure. However, second HP Laptop cannot connect to primary wireless network. I created password protected "Guest" network using Airport Utility, and laptop is able to connect to this Guest network. From reviewing forums am now able to configure Airport Extreme with Airport Utility by using "Configure other" on Dell computer. But utility cannot find device by scanning. Would like to find way to (1) have Airport Utility on Windows 7 Dell see Airport Extreme by scanning and not using "configure other," and (2) have 2nd HP Laptop connect to primary network and not "guest' network. Any assistance would be greatly appreciated. Thanks.

Bob - Thanks so much for your quick reply. I followed your suggestions and, to go into perhaps unnecessary detail, I'll write what I did. I completely disconnected the Airport Extreme Base Station (AEBS) from my computer. I disabled Windows Firewall, uninstalled my anti-virus program, and uninstalled Airport Utility and Bonjour, recycled by cable modem (took out the battery and unplugged it for about 20 seconds), then restarted my computer. After the computer booted up, I verified that windows firewall was disabled, reinstalled Airport Utility and Bonjour, then reconnected the cable connecting the AEBS to the computer (to one of the three ethernet ports, and I tried each of them in case one was faulty) but not to the cable modem as my firewall was disabled and had no anti-virus software. I also reconnected the AEBS power chord. I opened the newly reinstalled Airport Utility software and it did not find the base station. Only when I used "configure other" was I able to access the AEBS. I recycled the modem again, but that did not help. I turned on the firewall, installed anti-virus software, connected the AEBS to the modem, the light turned green, and I was able to access the internet on the primary computer and the wireless network gave me internet access on my laptops. But I was still not able to have my main computer, the one directly connected to the AEBS able to see it, and configure it, without utilizing "configure other."
Also, any idea why one of my laptops can only access the "guest" network? When it attempts to connect to the primary network it will stay on "acquiring network address" for what seems a few minutes, then switch to the "guest" network and connect immediately.
Any help would be greatly appreciated.

Error on Airport Express when using to extend Airport Extreme Base Station

I have had continual problems trying to get my Airport Express (n) to extend my Airport Extreme Base Station. The signal it is receiving is "good". The settings are correct (as far as I can tell) and it was working for a brief period of a month or so.
Now it is not working and I have a red 1 in a circle (like an update is needed... but it will not take me to an update) on the Sirport Express in my Airport Utility.
Under "Status", it says "Extended Network" with a green crcle, but the main circle on by the name is flashing green, and will not send a signal.
Also in "Status", it says this: "This AirPort base station was unable to extend the wireless network. Make sure the wireless network you're trying to extend was set up and is working correctly, that you entered a matching wireless network password into this device, and that this device is in range of the wireless network."
I have done all of those and yet..... STILL not working. Ugh.
Any thoughts? Procedures?
Thanks in advance.

At this point, I would suggest that you perform a "factory default" reset on the AirPort Express. In its default mode, the Express will broadcast an unsecured wireless network with a network name of something like: Apple Network NNNNNN.
Your Mac should recognize that there is a "new" AirPort Express present. You will find this on the dropdown menu from the AirPort icon on the OS X menu bar. Select the Express from the dropdown menu and the AirPort Utility should automatically start up to allow you to configure it.

How do I find a hard drive connected to Airport Extreme Base Station?

*Apple Says:* "If your base station supports it, you can connect a USB hard disk to the USB port on your base station and computers on your network (both wired and wireless) can connect to it to access, share, and store files and data."
Cool. So I followed the instructions. The drive is recognized by the base station and listed in the Airport Utility. It looks like it's ready to go...
So... How do I access the drive? I don't see it on my desktop, it's not under network. I've tried "Connect to server..." and browsing, I can't see the drive, anywhere. Yeah, I've searched the crap out of this issue on google and this message board as well as apple support knowledge base. I'm sure this is a simple issue and I'm just missing the obvious. Help me out.

Hello Timothy Uhl. Welcome to the Apple Discussions!
Try the following to mount the disk...
o Click on the Desktop to enter Finder
o Go > Connect to Server...
o Enter 10.0.1.1 for the server
o Enter Disk Password
o Connect
If this still doesn't solve the problem, let's double-check your disk sharing settings...
AirPort Extreme Base Station (AEBSn) - File Sharing Setup
Either connect to the AEBSn's wireless network or temporarily connect your computer directly (using an Ethernet cable) to one of the LAN ports of the AEBSn, and then, using the AirPort Utility in Manual Mode, check these settings:
Disks - File Sharing
o Secure Shared Disks: <With disk password | With base station password | With accounts >
(Note: Choose "With a disk password," or "With base station password" if you want to secure the shared disk with a password, or choose "With accounts" if you want to secure the disk using accounts.
If you choose to use accounts, click Configure Accounts, click the Add "+" button, and then enter a name and password for each user that will access the disk.)
o Guest Access: <Not allowed | Read only | Read and write>
o Share disks over Ethernet WAN port: (unchecked)
(Note: Select the "Share disks over Ethernet WAN port" checkbox if you want to provide remote access to the disk over the WAN port.)
o Advertise disks globally using Bonjour: (unchecked)
o Workgroup: <Windows workgroup name>
o WINS server: <WINS server IP address>

Setting up airport extreme base station with Mac and PC

I have an '02 iBook with an airport card installed and an airport extreme base station. my roommate has a PC and has the DSL connection in her room. i want to wirelessly network my iBook via the airport base. how do i do this? (my base was given to me without any manuals/disks etc)

Your Netgear wireless router is your network's base station. Your parent's PC will not be "serving as a base station" - its presence on the network isn't at all relevant to what you want to do.
To connect your G5 to the Netgear wireless router's network - click on your Mac's Airport menu, click on the name of your Netgear wireless router's network (it will appear in the list when you click on the Airport menu), and enter the wireless network password (if applicable) when prompted by the MacOS. That's is - you are connected!

How do I configure an Airport Extreme base station to receive and distribute a wi-fi network from a broadband wireless router?

I have recenly upgraded my broadband service and now have a wireless router. My old network configuration was a router connected by ethernet cable to an Airport Extreme base station which then broadcast my wireless network (I also had an Airport Express base staion set up as a wi-fi booster elswhere in the house).
I now have two networks (my original network and the new network from the wireless router) and wish to amalgamate these into one.
Ideally I wish to use the Airport Extreme base station as the "remote" booster (I have purchased Powerline adapters for this purpose) but don't know how to configure the Airport Extreme base station in order to to this.
Can you advise on the best set up for this please?
My Mac is running OS X 10.8.2 and the Aiport untility is version 6.1.
Thanks in anticipation.

The AirPort Extreme should be configured to "create a wireless network" with the same WiFi network name, security type (usually WPA2 Personal) and password as your existing router. It should be configured as connection type Ethernet and be in bridge mode.

Airport extreme base station no longer recognizes password

Similar Messages

Maybe you are looking for