When was my airport extreme base station built

Can you tell me when my AirPort Extreme Base Station was built? Its serial number is 6F706F6SVZC. I figure this will help me determine a number of tech items about this model, including what generation it is. Thanks!

It is an express not extreme.. at least according to this.
Serial Number: 6F706F6SVZC
Model:
- AirPort Express (802.11n)
Codename:
- No codename assigned.
Build Country:
- This unit was built in China.
Build Year:
- This unit was built in 2007.
Build Week
- Your device was built in week 6 of that year (February).
Production Nr.:
- This unit was number 1250 to be built that week.

Similar Messages

Airport Utility 5.4.2 was unable to find Airport Extreme base station.

I downloaded the new Airport Utility 5.4.2 to my 2009 24" iMac with Snow Leopard. Now it is unable to find my Airport Extreme base station or Airport Express. My iMac is connected to the network via the Airport Extreme base station but the Airport Utility cannot find it. All I get is this message "Airport Utility was unable to find any Apply wireless devices. Make sure the Apple wireless device you want to set up is plugged in and in range of your computer and then click rescan to try again". I clicked rescan numerous time with no luck. I even downloaded the Airport Utility 5.4.2 again with no luck. What is wrong??? Everything was working fine until I downloaded the Airport Utility 5.4.2.

Thanks for the info.
Following your same steps exactly, I am able to save the configuration file to the desktop, or navigate to another folder to save it at that location.
I was able to do this previously with 10.5.x and with current Snow Leopard. Notice that you list 10.4.x as your operating system. If you are still running this OS, it could be that 10.4.x does not allow this feature with 5.4.2?
Not sure if downloading another copy of 5.4.2 would be worth the pain, as I'm inclined to believe that it probably would not help solve your issue. If you decide to do this, please post back with your results.

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.

Certain web address not available when using Airport Extreme Base Station

Hello. To access my "secure" account at the local library, I must use a web address that contains a colon followed by a number. I believe that this is a port number, but I confess that all the discussions here regarding ports are going well over my head, and I may be incorrect with this assumption.
My problem is that while I CAN access this site by connecting to my DSL router directly via ethernet cable from my iMac G5, I cannot access the site when connecting to the internet in the mode: iMac Airport to Airport Extreme Base Station to DSL router via ethernet.
The format of the web address is: http://xxxx.yyyy.net:####/zzzzz/, where #### is the number I guess may be specifying a port and causing my problem.
Can anyone advise me, in simple terms, how to get to this address when in the Airport--internet connection mode? Will the solution have any adverse side effects?
Regards and Thanks
iMac G5, 2.5 year old AEBS Mac OS X (10.3.9) Westell 327W 4-port DSL Modem, not using wireless feature.

Very likely the embedded firewall that comes with your AirPort blocks the port you are trying to use.
In order to solve this, best way is to modify the AirPort settings (open the AirPort maintenance app):
Click at the tab "port forwarding" and add the desired port as "public port" to the list. "private IP" is the IP of your Mac and for "private port" type in the port number again.
If you are unsure about the IP of your Mac, look at the network maintenance application.
Well, one side-effect is that you have an open port in your configuration which could cause security issues... but only if you are paranoid So there is nothing to care about (note that without the AirPort inbetween your Mac and your modem, this port would be not blocked and freely accessible

I told my wireless network to forget two airport expresses so that I could rename them. Now the network does not see them even when plugged in about 10 feet away from the airport extreme base station. Does "forget" mean forever? How to reset?

I told my wireless network to forget two airport expresses 1 1st gen, 1 2nd gen so that I could rename them. Now the network does not see them even when plugged in about 10 feet away from the airport extreme base station. The network does recognize a totally new 2nd gen express. Does "forget" mean forever? How to reset?

The network does recognize a totally new 2nd gen express.
Then, it sounds like you have already reset the 2nd Gen Express, and now you need to set it up again, like you did the first time. Only, this time, assign the device name that you want to the AirPort Express.
Do NOT use the name that Apple suggests.....which will be something goofy like........Sueswimsf's Red Apple AirPort Express
Assign a simple name.....something like 2ndGenExpress

AirPort Extreme base station as bridge - is WPA allowed?

Hello,
I have an AirPort Extreme base station that is connected to the Internet via an older Linksys wired router. The Linksys is connected to a cable modem and acts as a router (so it's the DHCP host), while the AirPort acts as a bridge between wireless computers and the Linksys (so "Distribute IP addresses" is unchecked).
When using WEP or no security, everything works great. However, when using WPA, my laptop constantly cycles as it tries to get an IP address without any real success. I've tried all combinations of open/closed networks, different wireless channels, and wireless security types, but WPA just won't work. It's definitely supported by the wireless card and I've entered the password correctly, but no dice.
Does anyone know if WPA is supposed to work in this configuration? I noticed that another post recommended connecting cable modem -> AirPort -> wired router, but other posts recommend cable modem -> wired router -> AirPort. Not sure if it matters or not.
Thanks for any advice!

Hi Felix, thanks for your reply.
I have a Linksys wireless card (which I cannot find right now) and an Airnet AWN154 wireless card. When the Linksys didn't work, I purchased the Airnet, which also didn't work. This is on several Windows laptops.
To answer your other question, I don't think I've ever successfully gotten WPA to work with these cards, but of course I only have my own base station to test against. My fiance's laptop (with built-in wireless) worked briefly, but was very slow and every couple minutes the connection would drop.
The reason I originally asked if WPA is possible in this configuration is because I ran across some articles indicating that WPA might not work across bridged networks, although that was for different hardware than my Airport Extreme base station.
Jeff

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

Mac Book pro can't connect to Internet through Apple airport extreme base station

I had problems connecting to the internet in the past with my macbook pro. One day it suddenly started working again but then I bought a second apple TV I lost connectivity. I have tried changing the IP address manually and while it shows me connected to the wifi I am still with out internet. When I hooked up the new Apple TV that I bought it booted my computer from it's ip address. The apple TV though wouldn't work and now nor would my computer. I ended up setting the Apple TV's ip address manually and now it works fine. My computer on the other hand does not no matter if I set it manually or not. Even if I plug in the ethernet cable from the base station it doesn't work. It show that it has a self assigned IP address. After I set it manually it shows that I am connected both via wifi and the ethernet cable but I can't connect to the internet. If I plug the modem directly into the computer bypassing the base station I get internet and it is using the IP address that worked originally.
It has something to do with the connection from the base station to my computer but this is odd considering every other device I have: iPhone 4, apple tv, apple tv, apple mini with retina display all work perfectly via wifi (newest apple tv had to be set manually as I stated above but now works fine). When I check the ip of the base station itself it seems to be different from the ip of the computer when the computer was connected directly to the router. I don't understand why my computer now can't connect to the internet via the base station whether it be wifi or by ethernet. Can you please help me trouble shoot this?
I have an AirPort Extreme base station which allows up to 50 users and a 30 meg connection speed.
I have a MacBook Pro (17-inch Early 2009), OS X Mavericks (10.9.2)

It has something to do with the connection from the base station to my computer
I don't think so..
I just posted a reply which totally vanished.. strange strange website now.
Please post some screenshots of your AE setup from the airport utility.. I want to see the summary page, then the network and internet tab.
Please tell us what modem you use.. is it a router??
If you have satellite or 3G wimax etc service they often are limited to 5 IP addresses... the AE takes one and then 4 more devices can join .. no more.
You need to also give us the screenshot of the IP you are getting in a computer that works.
EDIT
Sorry this is half double post.. the previous page refused to display.. now it has returned..

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.

Ghost Drives on my Airport Extreme Base Station.

I have connected 4 external hard drives to my Airport Extreme Base Station via a powered USB Hub. The drives are recognized under he Airport in my sidebar, and I can double click on them and they mount to my desktop. The problem is that none of my data shows up. They appear to be blank. However, when I disconnect the hub from the airport, and plug it directly into an open USB port on my laptop, all the drives come up and mount automatically, and all data is accounted for. Now I'm not a wirless network guru by any stretch, but I assumed it was sharing preferences. I went through and enabled to share connected drives via accounts and entered all required criteria and updated the settings to my Airport. Still to no avail. Also, just for kicks, I opted to Connect to Server from the Go menu in Finder, and attained the network address by mounting the drives individually and gettting info on them, copying the address and entering them into the Server Address, clicking to add them as favorite Servers. Still same result. They mount as an Airdisk, but no content is shown. I know it's an easy fix, but I just do not know what I'm missing???? Any thoughts would be greatly appreciated.
P.S.- MAC for President 2012!

What troubleshooting steps have you already performed?
For example, If you do not connect the powered USB hub to the AirPort and connect only a single drive to the USB port on the AirPort, what happens?
If the drive works, then add the powered hub back in to the setup and connect the drive again. What happens?
If the drive works, add another drive. What happens?
If the drive does not work when you plug in into the powered hub...but it does work when you plug it in to the USB port on the AirPort directly, then you likely have a bad hub. They do fail. Some cheap USB calbles will work, others won't.
If you plug the hard drive directly into the USB port on the AirPort and you still cannot "see" the drive, that suggests a problem with the USB port electronics. Have the AirPort checked out at the Apple store or a servicer.

Define static IP for both LAN and W-LAN devices with an Airport Extreme Base Station

Hey guys,
I have a lot of different devices connected to my Airport Extreme Base Station (5th Gen) either wirelessly or via ethernet cable. Since I control some of them via VNC and currently have to find the corresponding IP-addresses through trial-and-error, I'd like to define static IP-addresses for the computers in question. My network consists of a cable modem connected to a TP-Link WR1043ND router in the basement, from which an ethernet cable leads to the WAN-port of the aforementioned Airport Extreme Base Station on the 2nd floor. Two of the devices I want to remote-access are wired to a D-Link DES-1005D switch, which in turn is connected to the 1st ethernet port of the Airport Base Station. The remaining 3 remote clients are connected over 802.11n. All computers run Windows.
My problem now is that even though I was able to define static IP-addresses employing the "DHCP only" router mode, this didn't seem to work for the two computers connected via ethernet. Not only did I lose any internet connectivity with those, I even lost the ability to remote-connect to them using the VNC-viewer.
The question now is: how do I specify static IP-addresses for my ethernet devices correctly?
I hope you can help me.

My network consists of a cable modem connected to a TP-Link WR1043ND router in the basement, from which an ethernet cable leads to the WAN-port of the aforementioned Airport Extreme Base Station on the 2nd floor.
If you read the information in the other post, my answer would be the same here.
The Router Mode of DHCP Only is rarely used, and would only really be appropriate if your ISP was providing you with a fixed bank of multiple fixed or static IP addresses to use. This does not appear to be the case in your post.
If this were the case, the first IP address would be used as a Static IP address for your connection, and other devices on your network would receive the other fixed IP addresses.
99%+ of the time, you would use the Router Mode setting of DHCP and NAT on a network when you want the AirPort to perform as the main router for the network.
But......your post also indicates that you have another router upstream on your network from the AirPort Extreme. You would not want to run two routers in series on a network. That explains the problems that you are having.
The AirPort Extreme needs to be configured in Bridge Mode. It cannot be the "main" router on your network when you already have another router on the network. That is a fundamental networking rule.

How can I extend a wireless network with my AirPort Extreme Base Station?

Today I purchased a brand new, dual-band base station to replace my Belkin N router, as I have had a handful of firewall, coverage, and other networking problems in my house lately. First off, I really like this router and it was very easy to setup. My MacBook Pro could use both bands and established a 300 Mbit/s link very quickly. After tweaking various settings to my liking, I was also able to maximize the connections on many of my non-Apple machines and devices. I noticed that the range of its network was better than my Belkin's, but unfortunately, it failed to completely saturate the area sufficiently. Since the Belkin still works well enough, I was hoping I could bridge them together one way or the other.
The Belkin router does not support any bridge mode that I know of, but the AirPort Extreme should be able to join a wireless network and then extend that over WiFi and Ethernet, correct? I would like to place them at opposite ends of my home so I can get strong WiFi signals everywhere inside. However, when I try to get the base station to connect to my preexisting WiFi connection, it tells me that I can't extend the network and fails to join.
So is this possible? And if it is, how would I go about setting it up? I know it would probably be easier if I had a simple range booster such as an AirPort Express, but I didn't buy one while I was at Fry's since I hoped I could make use of the older Belkin. This is its product page, if needed. Thanks for any suggestions.
-MacUser

The Belkin router does not support any bridge mode that I know of, but the AirPort Extreme should be able to join a wireless network and then extend that over WiFi and Ethernet, correct?
Sorry, but no. The AirPort Extreme Base Station cannot "join" a network like the AirPort Express or Time Capsule, but you wouldn't want to do this anyway because in this configuration these devices will only perform as wireless clients ... not routers.
Instead, the AirPort Extreme can either be extended or can extend another 802.11g or 802.11n AirPort ... or a very very few non-AirPort devices.
One option for your Belkin would be to connect it to the AirPort Extreme by Ethernet but this may not meet your requirements or be a desirable situation. Otherwise, you would need to get another AirPort to extend your current one.

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.

2 airport extreme base stations later and still no internet connection-

Sorry - yet another beginner with internet connection troubles! (I have read all the posts I could find relating, but without any help).
I have had a Demon broadband account now for about a month (I’m in the UK) and in that time I have purchased a D-Link DSL-300T Ethernet modem and an Airport Extreme Base Station. I got wireless internet working relatively easily – with a powerful range over the whole house and garden, but then one Sunday night, the internet connection via the base station suddenly ‘died’.
I spent the following 3 days scrutinising all of my settings of both the Modem and the Base station, re-setting both, and bought new Ethernet cables / micro filters etc but with no luck. (I’ll point out at this stage that my broadband account is still active, and if I connect the Ethernet modem directly to my iBook [wired] I can still get my broadband connection. Alternatively, I tried daisy chaining the modem to the base station and then via an Ethernet cable to an iBook, but no connection could be made).
When wireless, Airport Admin recognises there is a modem there, and under preferences > network under Airport it states I am connected to the internet – but I’m not.
I then phoned D-Link and they confirmed my firmware was up-to-date for use with Apple products and talked me through all of the modem settings and tweaked a few things, but there was still no connection to the base station. I then phoned Apple. They were incredibly helpful (as ever) and after 35 min. came to the conclusion the base station might not be re-setting itself properly. The replacement one came yesterday, and again I spent a number of hours trying to get it connected to the internet, but there is still no internet connection via airport and I can confirm this from both my eMac and iBook.
Reading through the forums on here, I understand that my particular modem is problematic with the base station, but I can’t work out why it use to work and now it doesn’t! One theory I have investigated is that the firmware of the base station is two advance for the modem following an update, but after reinstalling the original firmware I started with, I still have no luck.
- The eMac is running 10.3.9 / iBook is running 10.4.3. The base station is reinstalled with the latest firmware via system update. The first base station and the modem were delivered to me 31/10/05.
Any help or suggestions would be really appreciated if anyone has any ideas
Thanks for your time
Will.
UK.

http://discussions.apple.com/thread.jspa?threadID=2316
78&tstart=0
I think if you follow the instructions I gave in this
link you will be fine.
Remember, If you for any reason loose your
connection, it is normally always a Power Issue..Your
ISP is down for service ..or some other anomoly, If
you were good before your settings will still be
good...Good Luck...Don
Hi Don,
Thanks for you quick response. I printed off the instructions you posted on the support forum before, and ran through your procedue exactly, (twice) but I'm sorry to inform you that I haven't been able to re-establish my wireless internet connection. Would it be safe for me to assume at this stage that my modem is indeed fualty? It contines to work fine independantly, (I'm using it right now) but it can't seem to make contact with the basestation.
Will.

When was my airport extreme base station built

Similar Messages

Maybe you are looking for