Password on Airport Extreme Base

I set up my Airport Extreme Base with a password so it will not allow anyone outside of my home to use my connection without the password. I had to enter the password once when I set the password and from then on I have not had to re-enter it again. I am automatically connected to the internet. I assumed I would have to enter the password everytime to connect.
Could someone tell me if this is correct?
Thanks!

What you are experiencing is correct. The Mac remembers the password so that you don't have to re-enter it.

Similar Messages

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

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

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!

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

Internet problem with New Airport Extreme base and new Macbook Pro

So I bought a Airport Extreme base station with my new Macbook pro.
My desktop system uses a DSL modem which is connected to my computer via an ethernet cable. It works flawless. I can also unhook the hard ethernet connection from the desktop and connect it to the Macbook Pro with no problems.
I then connected the ethernet cable from the DSL router to the WAN port on the Airport Base.
I have no problem gettiing the Macbook pro to set itself up on the Airport Network. I can NOT, though, access the internet. I even tried to type in the IP address for the DSL modem while connected to Airport base and can not connect to modem. Does anyone have any advice? Is there a bridging function in the Airport Base that has to be activated?
Another question. If I replace my current DSL Router with a wireless router, do I even need the airport base if all I want to do it connect to the internet with the laptop?
Thanks,
Danny

I have no problem gettiing the Macbook pro to set itself up on the Airport Network. I can NOT, though, access the internet. I even tried to type in the IP address for the DSL modem while connected to Airport base and can not connect to modem. Does anyone have any advice? Is there a bridging function in the Airport Base that has to be activated?
Make sure you perform a complete power recycle when switching network components.
Modem/Router Power ReCycling
- Power-off the DSL modem & AEBS. (Wait at least 30 minutes. If possible, leave the modem off overnight.)
- Power-on the DSL modem; Wait at least 30 minutes.
- Power-on the AEBS; Wait at least 5 minutes.
If that doesn't resolve the problem, and your DSL ISP requires PPPoE for connectivity, you will need to set that up on your AirPort Extreme Base Station (AEBS) as follows:
Connect your computer directly (using an Ethernet cable) to the LAN port of the AEBS, and then, using the AirPort Admin Utility, check these settings:
Internet tab
- Connect Using: PPP over Ethernet (PPPoE)
- Account Name: <ISP account name>
- Change password: <ISP password>
- Always stay connected (checked)
- WAN Ethernet Port: Automatic
Another question. If I replace my current DSL Router with a wireless router, do I even need the airport base if all I want to do it connect to the internet with the laptop?
No, the AEBS will no longer be required.

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.

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 not recognized anymore by Airport Utility software

Hello,
I just encountered the problem today.
I have old Airport Extreme base sation (mushroom design).Picture below.
I have iMac 24". About this Mac Picture below.
Obviously, Airport Utility has been updated recently and today my network is not valid anymore, as well as the mushroom is not managed by Aiport Utility softwrare anymore. The only way to get WiFi now is using my computer as an antenna via the sharing of internet trough its WiFi card: not satisfactory.
The message of the software led directly to this support community.
The picture with the base station icon says: "this version of Airport Utility does not support this base station. To know more, check the Sevice and Support Community."
I did reset the base station may times, without success. I can't rename the base sattion, i can't create rename my network, i can't set up password access, i can't use WiFi other than the default Airport Extreme network.
Since this is not my field of knowledge, would anyone come up with a brilliant solution other than .... :
"Did Apple just manage to make you buy a new Airport base station ?."
Thank you for your time.

Hello,
Thank you for your reply and exlpanation.
I just downloaded the Aiport Utility 5.6.1 from Apple site. Unfortunately the OS X version is not compatible with this Airport Utility.
I don't have Time Machine neither.
Below is the message I got:
"Airport Utility cannot be installed on this hard drive. The Mac OS X version on this drive is not supported"
Is there something inbetween: a correction to Airport Utility 6.2 plug in that would accept my base station and compatible with my iMac ?.
Thank you for your attention.

Connecting Airport Express to Airport Extreme Base Station

Hi Folks. I am at my wit's end.
I have an Airport Extreme Base Station (main hub) purchased in 2003. Just bought a new Airport Express and it just won't connect to the AEBS. I think I've tried everything. From automatic WDS set up (described here http://docs.info.apple.com/article.html?artnum=107454) to using the Airport Utility and/or Airport Admin to set up. Nothing.
I've looked through the discussions and found this http://discussions.apple.com/thread.jspa?messageID=7011490&#7011490 but the solution provided makes absolutely no sense to me.
All I end up getting after numerous attempts at connecting to the AEBS is error messages and then a flashing yellow (amber I guess) light. When I do a "hard reset" it just goes back to flashing amber and it seems a factory reset doesn't work because according to this http://docs.info.apple.com/article.html?artnum=108044 I'm supposed to see the green light flash four times after I hold the reset button and plug in but that never happens.
This is driving me crazy. Anyone have any ideas?
Thanks.

Hey John.
I did finally solve the issue but I'm not quite sure how it happened but this is what I did:
First, I did had hard reset on the AEBS and set it up all over again via AirPort Utility. I set it up to use a WPA/WPA2 personal password.
Next I did a hard reset (not a factory reset) (hard reset: while plugged in, use a paper clip and hold the reset button for 15-20 seconds) on the AirPort Express and then restarted my computer.
After restart, I opened AirPort Utility and set up the Express to join my AEBS network. When it got to the point where it asked me to choose the network to join, I chose my AEBS network and it magically knew the WPA password I had set earlier and then after that it was smooth sailing.
I had tried a number of variations of that process many times before (and failed) and for some reason this time, it worked.
Hope it works out for you.
Best,
Benjamin

Airport Extreme Base Station and 2wire Modem / Router

I have Yahoo DSL with a 2wire modem / wireless router combo. I have an iMac and a MacBook both running Leopard. I can't seem to get the Back to my Mac feature to work. I'm currently running the trial version of .Mac. I'd like to get a full .Mac account but I want to be sure I can utilize the Back to my Mac feature. If I were to bridge an Airport Extreme Base Station to the 2wire would that solve my issue with Back to my Mac. Additionally I like the idea of being able to plug a printer of external hard drive into the Airport Extreme.
Any advice is greatly appreciated.

I got it to work. I purchased the Airport Extreme Base Station and took the following steps which I found here http://forums.macosxhints.com/archive/index.php/t-68141.html
First connect directly to the 2Wire with the Ethernet cable.
Instructions from 2Wire:
1. Clear the HomePortal to Factory State –can be accomplished two ways
2. Go to http://homeportal/management
3. Click on Resets
4. Click on Reset to Factory State
5. Click Continue
6. Have customer press Hardware Reset button with paperclip (HG products only and BellSouth HWs)
7. Have customer unbend a paperclip
8. Have customer insert paperclip into recess for Hardware Reset button (outlined with Red circle) on back of HomePortal.
9. Hold paper clip in for ten (10) full seconds
Next steps:
1. Go to http://homeportal/management again
2. Click on Configure under Broadband Link
3. Enter VPI 0 and VCI 35
4. Click on Disable PVC Search
5. Set Connection Type to Direct IP
6. Click Submit/Save
7. Have cu go to http://homeportal/management
8. Click on Configure Services
9. Have cu Uncheck Enable Routing
10. Click Submit
Airport configuration:
1. Open the AirPort Admin Utility and select your Base Station.
2. Click Configure and enter your password.
3. Click the Internet tab.
4. Choose PPP over Ethernet (PPPoE) from the Connect using pop-up menu.
5. If required by your ISP, enter your user name, password and service name in the appropriate fields. ( Your name and password is you full email including the @sbcglobal.net part and your email password)
6. Click Update.
7. After the base station restarts itself, quit the AirPort Admin Utility.
If that doesn’t work call apple and they should be able to help with the airport configuration.
Back to My Mac now works. Hope this helps someone else.
Message was edited by: WalrusBoy

I have an Airport Extreme Base Station and have recently upgraded to Mountain Lion. Now airport utility won't work with my base station so I bought a Time Capsule. For the life of me I can't make the substitution work and only see a blinking amber light.

I have an Airport Extreme Base Station and have recently upgraded to Mountain Lion. Now airport utility won't work with my base station so I bought a Time Capsule. For the life of me I can't make the substitution work and only see a blinking amber light. Can anyone who has made this change offer some advice?

apikoros wrote:
The Utility transferred all of the AE's settings, so I still have to change the password, which leaves me with only 2 other questions, I think:
1) I assume it's just a matter of using the Utility, entering a stronger password and checking for it to be remembered in Keychain Access. But do I have to change the password for each individual unit-- the TC, the Extreme and both Expresses-- or will changing it just for the TC alone work for the entire network?
Resetting the password you will need to do for each device... the utility cannot even see those old units.
So you will have to do it for each one.. think it through.. because as you change passwords the others will lose connection.. so start from the express which are wireless extending .. change those first.. and go back up the chain.. as each one changes it will drop off the network.. until you reach extreme and change that. Then you might need to reboot the whole network to get everything talking again. If something goes wrong.. just pluck that one out of the mix and plug in ethernet.. reset and redo the setup. That is my preferred method anyway.. do everything in isolation one by one. By ethernet and then nothing goes wrong.
2) Who's the treasonous SOB who spilled the beans to you about the ICBM in my back yard?!?
N.Korean hackers.
[Edit] Whoops-- one more question: I want to partition the TC's disk, but Disk Utility doesn't see it. What do I need to do?
You cannot partition a network disk. And apple provided no tools for it in the TC itself. You can pull the disk out and partition it but that voids your warranty. (although done with care who is to know).
Look at Q3 here.
http://pondini.org/TM/Time_Capsule.html
Mixing TM and data on the TC is worth planning carefully. They don't necessarily sit happily together.

Can't get PC laptop to connect to Airport Extreme base station. Help!

I've spent a lot of quality time on the phone with support staff at Apple, Earthlink, and Netgear. Now I turn to you fine folks.
I have an Airport Extreme base station. My G4 is connected to the base station via ethernet, and that works fine. My problem is with the wireless networking with our Dell laptop running Windows XP SP2. Wireless card is a Netgear WG511 with updated firmware. I've configured the network on the PC end using the Netgear Smart Wizard, rather than Windows (I don't know if that makes any difference).
Smart Wizard says the PC is connected to the network, and says that signal strength is excellent. However, there is no connection. I've tried pinging, but get no reply.
The status bar in the Smart Wizard window switches every 2 seconds from "Connected" with excellent signal to "Searching" with virtually no signal. The log shows that it's constantly connecting to and disconnecting from the network.
I've gone over IP and MAC addresses and whatever other settings I could check with all of the respective phone support people. I'm using WPA/WPA2 Personal security, and have double-checked the 13-digit password on both ends. I'm connecting using PPPoE, per Earthlink's settings.
This is maddening! Any suggestions? I'd really appreciate it.
G4 Mac OS X (10.4.10)

See if iFelix's suggestions work for you.
http://www.ifelix.co.uk/tech/1000.html
Remember all the smart wizard stuff is strickley for PC Hadrware and Software and does you no good at all with a Mac.
Don

Connect to Linksys Cable Gateway via AirPort Extreme Base Station?

Thank you in advance for any replies.
I have the following new setup:
A G3 Blue tower running OS X 10.4.10 is successfully connected to the internet via a Linksys WCG200 Cable Gateway connected to RCN's cable internet service. The WCG200 unit has wireless capacity though it's connected to the G3 tower via ethernet cable.
A second Mac (G3 iMac DV running OS X 10.4.10) is in another room in the office. I'd like to set it up with internet by wirelessly connecting with the existing WCG200 unit using an Airport Extreme Base Station (AEBS) I've recently acquired. To ensure a smooth process, I reset the AEBS to factory settings and installed the AEBS software (version 4.2) onto the iMac DV. Finally I plugged in the AEBS into the iMac DV using an ethernet cable plugged into the AEBS's WAN port (AirPort Admin Utility advised me to do so).
That's the hardware configuration. Working out the software and configuration details is proving 'niggly'.
First, I used the AirPort Setup Assistant to configure the AEBS. I told it to Set up a new Base Station, then to set it up as connecting to the internet using a Cable modem (the top option of two—the second was to set it up with internet through a LAN). I set up the name and passwords for the Base Station and had the utility configure the AEBS accordingly.
No internet connection occurred. I tried using the Internet Connect utility in the Applications folder, but no button or visible option for connecting via AirPort appeared, as the Setup Guide indicated it should, only a button for a VPN appeared.
I called Apple and asked whether it was even possible to connect to the internet using the AEBS talking wirelessly to the WCG200 unit. A tech told me it could be done by going into the AirPort Administration Utility, going into Configuration, clicking on the WDS tab and inputting the MAC address for the WCG200 unit, then going into the Airport tab and typing in the channel that the WCG200 is using. Note that the WCG200 unit has 3 MAC addresses listed; one each for “modem MAC address,” “WAN-MAN MAC address,” and “WAN-DATA MAC address”. I used the “modem MAC address.
The Apple tech added that it might need further tweaking, but that Apple couldn’t provide this tweaking and that I might check various forums if need be.
I followed the Tech’s advice, at which point the utility informed me that it couldn't use DHCP or NAT with this setup’ and to make sure that the "Distribute IP Addresses" checkbox was deselected under the Internet tab. This I did, but it was already deselected. I told the utility to update the AEBS accordingly, and restarted everything, including the 2 Macs and the WCG200.
Result:
No connection.
Tried it again with the Ethernet plugged into the AEBSs LAN port, still no connection.
Help! Can’t I get the AEBS to even see the WCG200? I know wireless is properly functioning in the WCG200 because another user with a Windows laptop connects to it wirelessly. The Mac Tech also mentioned that this could be relatively easy with an AirPort Express piece of hardware (Card? Base station?) but that it would be difficult with the Airport Extreme Base Station.
At this point we’re willing to spend $100 on getting this up. What would be our best option in terms of equipment, or can connectivity be accomplished with what we have?
Thanks again,
skyheart

skyheart, Welcome to the discussion area!
In theory using WDS would provide what you need.
In reality the Linksys device is not compatible with Apple's WDS and therefore this will not work.

Password on Airport Extreme Base

Similar Messages

Maybe you are looking for