Airport Extreme Base Station doesnt work anymore?

Hi, I'm new here, a novice when it comes to technology, and I desperately need help... My internet connection use to work, now it doesnt. I had my DSL modem connected via ethernet cable to my AEBS and from my AEBS, I had an ethernet cable connected to my desktop pc. I was able to go wireless with my macbook and other laptops but now the only way I can access or use the internet is when the desktop pc is connected directly to the DSL modem via ethernet. I cant use my macbook or other laptops wireless. I tried rebooting the airport and calling my network provider (which said it was due to faulty ethernet cable which was not true as it works fine) so they didnt help. I am receiving full bars on my airport senor but am unable to use safari or firefox on my macbook (its says that I'm not connected to the internet). I dont know what to do and have searched forums online with no avail, can someone please help me...

Kakko,
Since it was working, the first thing I would do is to power down your AEBS (I assume you mean the new 802.11n) and then power down the cable modem. Let them sit a while - probably at least 30 minutes. Then power them back up in the opposite order that you powered them down.
One important thing to make sure is that you plugged the input from your cable modem into the WAN port of the AEBS not one of the LAN ports.
Also have you launched Airport Utility (if you have the 802.11n do not use Airport Admin Utility). See if your AEBS comes up when the utility scans for base stations and expresses.
You didn't say what the color of the light on your AEBS is.
Also up on the top left of the page go to the Airport Symbol and see if your network shows up.

Similar Messages

HT1218 Airport Extreme base station is working, but not visible on network?

My Airport Extreme base station is working: all devices are able to connect to the internet, but Airport Utility shows no connection. Only one computer even shows the device-- greyed out-- saying "Device not Found." The airport utility shows version 6.2; OS X version 10.8.3. How do I update the base station to version 7 if the device can't be found? And how do the devices connect to the internet without "seeing" the device?

Thanks for checking. This model should be visible in AirPort Utility in Mountain Lion.
If you have not already done so, I suggest that you perform a complete power cycle on the entire network as folllows:
Power off every network device....in any order you want
Wait a minute or two
Start the modem first, and let it run a few minutes by itself
Start the AirPort Extreme next, the same way
Continue starting devices one at a time about a minute apart until everything is powered back up
Check the network again using AirPort Utility
You can also temporarily connect an Ethernet cable from your Mac to one of the LAN <-> ports on the AirPort Extreme to see if a connection is established that way.
If still no luck, try another Mac if you one handy. After that, all that I can suggest is that you perform a Factory Default Reset on the AirPort Extreme and configure it again.

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.

HT3546 Does the Airport Extreme Base Station not work with the OS X Lion?

Ever since updated to OSX Lion can't get our airport station to work. Is it too old and won't work with this upgrade so do we need a newer airport?

Suggest that you download and install AirPort Utility 5.6 for Mac OS X Lion which should work with your older AirPort Extreme.
You can keep both AirPort Utility 6.1 and 5.6 on your Mac and use the one that you want or need at the time.

I have a Cisco wireless router. Can I buy an Airport Express plug in booster for a distant part of my house or do I need an Airport Extreme base station instead to make the Airport Express plug in booster work?

Can I buy an Airport Express plug-in wifi signal booster to connect to a Cisco wireless router, or do I have to buy an Airport Extreme base station to make the Airport Express plug-in work?

You would need either an AirPort Extreme or an AirPort Express connected to the Cisco router, with a permanent Ethernet cable connection.
Configure the Extreme or Express that is connected to the Cisco router to "create a wireless network".
Then, you could add an AirPort Express to "extend a wireless network" to provide more wireless coverage for the network that the Extreme or Express would be creating.
Remember that the Express can only "extend" the quality of signal that it receives, so it must be located where it can receive a strong signal from the "main" AirPort.
If you don't need the Cisco wireless signal, you could turn it off.....or use that network for guests or something similar.
The bottom line here......you always need two Apple routers if you want to extend the network wirelessly.

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.

I have a MacBook ProDo I have to have the Airport Extreme Base Station for my Airport Express to work?

I cannot get the darn Airport Express to work! It just keeps blinking Amber. I know it must be something silly I am over looking. And I do not have the Airport Extreme Base Station.
Thank you for any help!!!
Elizabeth

Thanks,
This is the rear of your modem/router:
Connect a Cat5e or Cat6 cable from any of the 4 Ethernet Lan ports to the (single) socket on the Express, then go to Airport Utility (Applications>Utilities>Airport Utility) and select create a new network.
You will need to turn the wireless transmiter in the Netgear off, here is a link to the Netgear Manual in case you need to refer to it.
Netgear Manual

Setting Up Comcast to Work with the AirPort Extreme Base Station

I just set up Comcast high-speed internet through the cable modem and ethernet connection and it works fine. What I need is a step by step instruction on how to set up the connection through my AEBS. I've tried to configure using the Admin Utility, the AirPort Set-Up Assistant, the Network panel---all with no success. I'm not sure what to enter in the boxes or what to check. I've read the "Designing AirPort Networks" PDF and it wasn't much help.
The AirPort Network was working fine with the dial-up connection I had before.

Voila! NOT!!!
I'm having the same problem trying to set up a friend's "new" Macs, and I cannot get them connected to the internet. I've also followed the same steps. I tried the resetting trick (unpluging, waiting, repluging the modem first, then the Airport Extreme Base Station.)
The DSL ISP is SBCGlobal. Their dsl modem is SpeedStream 5100. The AirportEBS is the about 4 year old white base station with the phone jack, and a WAN and a LAN ethernet ports. I'm trying to connect two iBooks and a MacMini.
Everything did fine for the past year with the modem in "regular" mode and only ONE Mac connected. When the new Macs were recently acquired, SBC techs said that the modem needed to be put into PPPoE mode so that multiple Macs could be connected at the same time. This was done. [The techs said in regular moden the modem does the authentication; in PPPoE mode the modem acts as a bridge and the AirportEBS is the router and provides the authentication. I am assuming the techs are coreect, but I don't know for sure.] The CAT5 ethernet cable from the modem goes into the WAN port on the AEBS. The computers all see the local wireless network set up by the AEBS.
However, when any of the Macs try to connect to the internet, the error message returns "No PPPoE server available." Resetting the modem and base station has not cured this. [n.b. Bypassing the AEBS completely by connecting the CAT5 cable from the modem directly to the Mac will provide internet connection.] Any other ideas? Sounds like both of us are having the same sort of problem.

Airport Extreme Base Station and IPv6 -- It just works!!!!

I have a new Airport Extreme Base Station --- in poking around and learning about the features I was astounded to see that I was accessing IPv6 sites ... yes-it supports IPv6 (native and via teredo) --- GREAT JOB APPLE!!!!

Curious, though. Were you able to make it work with DMZ turned on?
I have not tested it with the new 7.2.1 firmware but will do it later.

Help - Kodak 5300 printer doesn't work w/ Airport Extreme Base Station

Hi All,
Running a MacBook on OS 10.4.11 (airport extreme card) and an I-Book on 10.3.9 (airport card) - just bought an airport extreme base station and a Kodak 5300 all-in-one printer. Base station works fantastic with internet and both CPUs. Kodak printer works great when directly connected to laptops by USB. When printer connected to USB port on Base station it recognizes printer but wont print. Set-up printer with Bonjour settings - but printer won't print with WiFi. "Printer not responding" window appears. Have phoned Kodak support. They tell me the printer should work on Wi-fi but I should contact Apple. Have phoned Apple support - they're stumped. Kodak website recommends using a Silex wireless router with this printer and claims it is compatible - so it can handle wireless set-ups.
Has anyone out there had success with the Kodak 5300 and the Airport Extreme Base Station? It's a great printer that uses very little ink (inexpensive cartridge replacement). I really don't want to fall back on my old Epson.
Thanks for any thoughts/solutions.

Hi Ron! Thanks for checking inside Kodak. I agree as a first printer from kodak it's a good one, and I certainly appreciate the attempt to buck the industry-standard of milking the customers on ink.
However, I'm not willing to go buy a silex device, when I already HAVE a device: the apple airport. I also got a reply from kodak support indicating that they didn't want to comment on future products, etc etc. Maybe I'm misreading this by assuming product == hardware, but I'm certainly not willing to ditch my current printer for a newer model for what I consider to be a DRIVER issue (I could be wrong of course). Maybe a firmware issue, but certainly not a hardware issue.
What I expect from Kodak is a new driver and/or firmware that would make this work with the apple airport. On the one hand I can understand not wanting to divulge company secrets and upcoming "products", but for a newer driver, I would expect to hear a "we're aware of the problem and are working on a fix". That would go MILES towards making me more patient and less irritated with Kodak. Telling me to wait for newer "products" or go buy a silex is a good way to loose customers.
So if you have any internal clout (or a message board), be sure to raise cain there for them to do the right thing.
jan
P.S. At the current time of writing, the silex website is not operational ("This site is temporarily unavailable. Please notify the System Administrator"). Way to go silex!

Printer that works with Airport Extreme Base Station

Hi. We are very new to Macs (2 weeks). Have a Mac Book and AEBS. Both work fine. Our HP printers, however, only work if connected directly to the Mac Book. I'm informed that we need to get a printer that works with the AEBS if we wish to have wireless printing. If anyone can recommend a printer that works with AEBS, we'd be grateful. Thanks.

Hello Jungle-cat. Welcome to the Apple Discussions!
Check out the following iFelix site to see which printers are known to work (not not) with the new 802.11n AirPort Extreme Base Station (AEBSn).

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.

AirPort Extreme Base Station Failing to Power On

I have an AirPort Extreme Base Station that suddenly stopped showing a power light. I've had this device for less than a year. Is it likely that the power supply has gone bad this quickly? This is a model A 1408 unit. Any history of this?

I've had this device for less than a year. Is it likely that the power supply has gone bad this quickly? This is a model A 1408 unit. Any history of this?
Just take it back to apple.. yes the internal or external power supply can fail.. but if less than 12months old it is under warranty.. Apple wiil simply replace it.
It does happen .. not often but it is reported occasionally.
I have this problem too! I have a model A 1521 and I bought this mid august this year.It's depending between 2 or 5 days that my airport extreme stopped working and have no supply anymore.I need to pull out the plug and plug it back before it works again.
This is much more common.. return to apple for replacement.. try using it with a protected power board or even UPS and people say they work better.. the power supply shuts down with the slightest dip in power.. so it seems to be a design fault in certain batches.. there is a long thread..
My Airport Extreme intermittently shuts down completely.

Comcast HSI, AirPort Extreme Base Station issues

Recently, I've been having some connection issues with my Comcast High-Speed Internet and my AirPort Extreme Base Station. I'll be connected fine one minute, and the next my AirPort monitor drops to 2 bars of signal and nothing will connect. Resetting the base station and the modem works about 50% of the time, while just sitting here "dealing with it" works the other half of the time.
I rent my cable modem from Comcast, and I believe it is the Terayon TJ715. I went to the Apple Store San Francisco and had my base station replaced, thinking it was the culprit, but alas, the problem is continuing, only less frequently.
I've replaced all my ethernet cables, tried it with my AirPort Express (which works more often, yet has the same problem occasionally), yet my connection uptime and signal still drops to 2 bars and essentially disconnects.
Even stranger, the computer I have connected to the LAN port seems to work fine even when the computers connecting wirelessly are having issues.
I'm going down to a Comcast Support Center on Friday to (hopefully) replace my modem with a newer model (someone told me that older Comcast modems "kill" AirPort Base Stations), but other than that, any ideas? Anyone have this type of issue with Comcast in the past?
The 3 machines im running are:
Dual-Core 2.3Ghz Power Mac G5 via AirPort
867MHz PowerBook G4 (Titanium) via AirPort
800MHz iMac G4 (Flat-Panel) via Ethernet
Thanks,
Alexis
Dual-Core 2.3GHz Power Mac G5 Mac OS X (10.4.3)

Don,
Thank you for the link. However, it did not seem to solve my issue.
It's not that I haven't been able to connect to the internet at all using wireless. I will be connected fine (all 3 computers connecting to the internet simultaniously) when suddenly, any machine connected via AirPort (specifically my Dual-Core Power Mac G5) will receive two bars of signal and will no longer connect to the internet. The only remedy I've found is to reset both the cable modem and AirPort Extreme Base Station, and this only works about 50% of the time.
I am going to have Comcast replace the modem (and in the meantime, get new Ethernet cables) tomorrow, so hopefully I won't be having this issue anymore, but I'm more curious what may be causing the issue. Have you heard anything about older Comcast modems causing latency issues with AirPort Extreme Base Stations?
Thanks again,
Alexis

How do I open the same ports on an Airport Extreme Base Station for multiple computers at the same time?

As the title suggests...
I have a mix of five Mac and PC's at home using an Airport Extreme Base Station as the router.   I need many ports opened on the AEBS for all of the computers- not just one computer. (for example: three people want to play TF2 on Steam at the same time; each machine needs the correct ports open on the router).   Port forwarding only allows me to forward a given port to a single IP, yet I need that port open for five differnt IP's, all at the same time.
How do I do that on an AEBS?
In the same way, I have a small office of four iMacs using an old airport with the same exact issue.   I would like to be able to connect to all of them remotely with Apple Remote Desktop, but the port forwarding on the airport only allows a port to forward to a single IP.   I want to be able to tunnel into the office network and log onto any machine behind the Airport extreme... not just a single IP.    I currently have it set up where I can tunnel into the office from my house, I can find the one machine that the port forwarding has been assigned to, I can log on and everything is just fine... with one machine.    How do I open the firewall for the other machines?
TL,DR version: How do you open ports on an Airport Extreme Base Station instead of forwarding ports?   Forwarding ports doesn't work for multiple IP's.

You can open a single or multiple ports to a single device or different ports to different devices, but you cannot open the same port to multiple devices via the AirPort Utility for the Apple routers.

Airport Extreme Base Station doesnt work anymore?

Similar Messages

Maybe you are looking for