Extreme Base Station - green lights flashing in back, no light on front
My Apple Extreme Base Station isn't broadcasting a WiFi signal and isn't creating a network for ethernet. The green lights on the back by each port are flashing about every second, but the front indicator doesn't show a light (no green, no amber, no nothin'). The base station doesn't show up on AirPort Utility, even though it's connected via Ethernet cable.
I tried doing a hard reset (turning off station for a couple minutes, holding in reset button - plugging in power - and continuing to hold reset button) but nothing seems to be working.
Is this dead? Or is there another solution to bring it back to life. Thanks if you have a fix!
An internal power supply has failed on the AirPort Extreme. Unfortunately, Apple does not offer repairs or repair parts, so not much that you can do other than replace the device.
The A1143 was discontinued in March 2009, so the device is at least 5+ years old, likely older. Unfortunately, 5 years....on average.....is about all that you can expect from routers designed for home use.
Similar Messages
-
Currently use Airport Express -1st Generation-to access internet -purchased 2014 Airport Extreme base station -can I import Express back up configuration to keep current settings . Or is it best to do new Airport Extreme as a new Network .
Just spoke with Cisco about the router. They said the router is compatible with the E1500. They suggested that I contact Apple to see if their default IP address was that same as the router (192.168.1.1). They told me I would have to change it if that was the case. How would I do that?
-
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. -
Have 2 airport extreme base stations connected in chain. Airport utility shows slave unit without power. However, power is on slave unit, but status lights do not show up at all. Small green lights at each back port blink. Anyone have any ideas?
Unfortunately, you are describing the symptoms of an AirPort Extreme with a failing (or failed) internal power supply.
As a last resort, try a Factory Default Reset on the AirPort Extreme as follows:
Power off the AirPort by pulling the power cord
Wait a minute or two
Hold in the reset button first, and keep holding it in for an additional 8-10 seconds while you simultaneously plug the power back into the AirPort
Release the reset button and allow a full minute for the AirPort to restart
Now try to configure the AirPort again. If you continue to see the same symptoms as before, the AirPort will need to be replaced. -
Brand new Airport Extreme Base Station flashing Amber light
hi
I know this question had been addressed before , but i couldnt find satisfying answer yet
I bought this Brand new airport extreme base station, I hooked up my ethernet cable into WAN Port as per the manual.
I installed airport utility 5.1 on my windows xp SP 2 laptop
and then I powered on the base station
The light in front was Solid Amber and then it turned Flashig Amber .
I tried resetting the base station and Cable modem. but no luck with Flashing Amber Light
Any Help for beginner Apple user?
thanks
Airport Extreme Base Station ( 802.11n) Windows XP SP2Here is another post that addresses your question:
http://discussions.apple.com/thread.jspa?threadID=1005682&tstart=15 -
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. -
How can I get Time Machine to back up an external hard drive (iPhotos) that is attached to airport extreme base station. Note: Time machine is usb to macbook pro and external drive with iphotos is usb to airport extreme base station. Help please. Thanks!
Once you have the drive connected to your Mac, click System Preferences (gear icon) on the dock
Click Time Machine
Click Options
Be default, the hard drive will be Excluded from backups. Click the drive to highlight it, then click the "-" (minus) button at the bottom of the list to remove the drive from Excluded items.
The drive will be backed up on the next Time Machine pass
Everything above assumes that the hard drive has been formatted in Mac OS Extended (Journaled) as Time Machine will only backup drives in that format. -
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 -
Thanks in advance for any help you folks can offer. I'm a newb here and will try to offer as much detail as I can about the dilemma at hand.
Scenario: Home network has been recently set up for wireless internet access via NEW Airport Extreme Base Station (purchased September 2011). Units accessing the network include: 2011 Macbook Pro, 2011 Macbook Air, 2007 Macbook, 2009 Macbook Pro, 2 iPhone 3GSs, and a 1st-gen iPad (and a partridge in a pear tree AEBS is configured to run WPA2 encrypted network, as well as a WPA2 guest network. I am attempting to yoke a BROTHER HL5370DW wireless B or G/ ethernet / usb-capable printer to the main network such that any and all units can print wirelessly or its equivalent (i.e., via printer hooked to AEBS through USB hub)
Problem: Despite configuring the Brother printer to recognize the main WPA2 network I created, I am unable to get wireless printing to work. My workaround was to physically connect Brother printer to AEBS via USB, specifically using a Belkin USB hub (after all, I wanted access to usb drives, as well as the printer). This workaround works ONLY SOME OF THE TIME. Generally, after a fresh boot of any computer or after a restart of the AEBS, any given computer will be able to print (i.e., any computer wirelessly connected to the main WPA2 network recognizes the printer). HOWEVER, at random times, printer access is gone (as is access to USB drives connected to AEBS's usb hub). Wireless networks are still up and running when that happens. IS THERE A WAY TO GET THE USB HUB's devices (i.e., printer and usb drives) to ALWAYS REMAIN AVAILABLE AS LONG AS THEY STAY CONNECTED TO THE AEBS? In other words, what accounts for the intermittent loss of the usb peripherals?
Sometimes, I just shut the airport off on whatever computer is having this problem, and the problem goes away. Sometimes, the problem is present across all computers in the house, sometimes only a few are affected. I can ALWAYS see the AEBS in the Airport Utility if the AEBS is connected to the particular computer via ETHERNET CABLE.
My theories:
- true wireless printing (i.e., without usb hub workaround) doesn't work because the N network somehow isn't backwards compatible with the Brother printer, which, i believe, is B/G. Although...isn't Wireless N networking supposed to work with BG devices? I did find a thread (https://discussions.apple.com/thread/2570774?start=0&tstart=0 ) that explains some of the particulars of WPA2 encryption and Wireless B/G issues, but it was beyond my level of comprehension (I'm a psychologist, but not an Apple Genius
- The usb workaround is only intermittently viable because of some flaw in the Airport or Airport Utility that causes dropouts to happen when a Macbook Pro or Air's lid gets closed or one gets opened after having been at a different network (e.g., at my office).
QUESTIONS:
- Should I try to use my old router (7 year old Linksys WRT54G) as an access point and connect the Brother printer to that G-router? How do I do that?
- I wouldn't mind just relying on the usb hub method if I could just insure more consistency (i.e., no random dropouts of peripherals). How could I do this?
Rule out:
- wireless printing works on my printer - it was being recognized back before the AEBS. I had the Linksys router running a WEP network and had the wireless printer talking with no cables to the router and the computers. (I just don't want to revert to using WEP encryption given its lack of security and my trying to protect HiPAA related health information on behalf of patients)
Any help will be greatly appreciated.
Thanks in advance!13 ASCII characters = 104 (aka 128)-bit WEP
encryption
If turning off WEP works, then you just need to
provide the cameras with the "Equivalent Network Password".
One of the problems with WEP is that the actual
standard relies on a 10 character HEX key for 40bit
WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier, vendors use certain
algorithms to convert simple alphanumeric passwords
(or passphrases) into HEX keys, thus enabling the use
of simple easy to remember WEP password rather than
lengthy HEX keys. The problem is that different
vendors use different algorithms to generate the HEX
key and therefore a ASCII password on an AEBS will be
hashed differently on a non-Apple client and vice
versa.
You may find the following article helpful:
- Apple article, especially the part about
"Third-party client to Airport".
Brilliant idea about trying the system with No encryption on... that DID solve the problem... almost.. once I turned off the encryption option, and restarted the Airport, I got a dialog box showing that the "Base station needs attention" but it didn't indicate WHAT kind of "assistance" it needed. Nonetheless, I closed out of the Airport program only to find that the indicator light, which had been Green, was now, flashing Yellow and I could not connect anything, including my computer. I opened the Airport program again and found the ONLY way I could get the Green light on was to select some sort of encryption option... then the light would go Green again but my cameras would not hook up again, and when I went back in and ONLY changed the option to NO encryption, I got the yellow flashing light and the "this base unit needs attention" warning...
I think your suggestions are almost on the mark... is there any way of reconciling the WEP coding between the cameras and the Airport??? Or turning off the encryption option and STILL have Airport work?
Thanks again for your help and suggestions... I really appreciate it.
geoff -
Solution to Airport Extreme Base Station + Airport Express networking probs
I've been investigating this for 3 straight days after inadvertently destabilizing my network. There are tons of posts discussing a variety of issues, all of which seem related. My goal here is to provide links to other relevant posts and explain what I ended up doing to get things to work.
First, the background. You can skip below to SOLUTION if you don't really care... However, I highly recommend you take the time to read everything, as you'll get other useful information in the BACKGROUND section. I'm guessing many of you have similar, related problems so BACKGROUND might help provide context (and solutions) to some things you are seeing...
MY SETUP:
AirPort Extreme Base Station (AEBS) of type b/g (round one, not square one), connects to the cable modem, and creates a WDS network that is then shared across two standard AirPort Express (AEX) units (100megabit, not the gigabit ones). One AEX serves as a relay unit that accepts clients, the other serves as a remote unit that also accepts clients. The intent is to show a single network throughout the house and let users log on to one network and move between networking units without having to switch from network to network.
I have a variety of networked devices throughout the house all running on the same network (2 Mac Pros, a Powerbook G4, a Mac Mini, an Apple TV, a Windows XP laptop, two iPhones, two wifi printers, and a 5-unit Sonos system, plus the AEBS and two AEXs). Yeah, I'm a geek.
The Mac Pros are both running 10.4.11, and the Powerbook is running 10.5.2.
AEBS is running firmware 5.7
AEXs are running firmware 6.3
All Macs were initially accessing configs via the recently released AirPort Utility 5.3.1. More on that later.
BACKGROUND:
I've had this network setup working for about a year now. Recently, I've been having poor network performance problems and came to the conclusion it was a LAN problem (ie. problem with my home network, as opposed to with my ISP). Upon initial investigation, I began by looking at my networking logs (via AirPort Utility 5.3.1). You get to those by selecting the unit in question, choosing "Manual Configuration", the selecting the "Advanced" tab up top with the "Logging and SNMP" sub-tab. Click the "Logs and Statistics" button therein for log details from that unit.
The first thing I noticed was "Administrative access denied to ff80::xxxxxxxxx" messages - a lot of them. I didn't recognize the ff80:: address in question, and so became concerned it was someone outside the network trying to hack one (or all) of the AEBS/AEX units. You can see threads discussing that investigation here:
"Hack or panic?" - http://discussions.apple.com/thread.jspa?threadID=1438486
"Administrative access denied" - http://discussions.apple.com/thread.jspa?threadID=1438865
Long and short of it is that the recent AirPort Utility 5.3.1 release (current as of March 13) seems to have problems (keychain) when attempting to access the AEBS and AEX units. The "Administrative access denied" logs actually refer to the client machine you are using when you try to read the logs. The ff80::xxxxxx address is simply the IPv6 address for the machine you are using; if you turn off IPv6 on your client machine, that address should switch over to begin showing a regular IP address instead (something like 10.0.1.xxx), which makes it easier to associate the IP to the machine. I explain how to deactivate IPv6 on both Tiger (10.4.x) and Leopard (1.5.x) here:
http://discussions.apple.com/thread.jspa?messageID=6814978#6814978
Anyway, in the process of investigating the "Administrative access denied" problem, I began tinkering with my AEX settings. Specifically, I ended up performing a hard factory reset (unplug unit, plug back in while holding down the little button with paper click/pen for ~10-15 seconds until light flashes green 4x then reverts to amber/yellow/orange). I began reconfiguring my entire WDS network using the newly updated AirPort Utility 5.3.1, and that's when the trouble started.
(If you are having problems seeing either your AirPort Extreme Base Station or AirPort Express, read this:)
In short, each time I thought I had properly configured things and then confirmed settings (kicking off a reboot on the AEX unit) the unit would restart with new settings but not properly join the WDS and not show up in the AirPort Utility list of units. More specifically, I would start with a "wiped" AEX and see both the AEBS and the AEX in my AirPort Utility list, but upon confirm/reboot the AEX would disappear and the AEBS would remain. However, that's not 100% correct. It seems that sometimes I would end up with the AEX and NOT the AEBS. Because both the AEX and AEBS were theoretically "hosting" the same network name (remember, WDS shares the network name across units) my auto-login feature for my client computer's wifi seemed to "jump on" whichever unit it first saw hosting the default network name for my house. In other words, it seems what was really happening was that I was ending up with two separate networks in my house, both with the same name but not talking to each other (as opposed to two units sharing the same network name and internet connection). The AEX would continue to blink orange/amber/yellow (whichever color it is to your eyes ) because it could not grab an internet connection -- and if I was on the network through that AEX unit I would not get internet. But if i was connected through the AEBS I would continue to have internet access. As far as my client computer (my Mac Pro) was concerned, I was on the home wifi network even if I was on the AEX rather than the AEBS -- it would show the home wifi network name as the name of the network it had connected to. But when I opened the AirPort Utility 5.3.1 I would see only the AEX (if I was connected through it) or the AEBS (if connected through it) -- a clear indication that the units were not truly sharing the same network.
I tried rebooting and reconfiguring the AEBS and AEX about 50 times (literally). I even tracked down an older version of the AirPort Utility 5.2.1 via this thread (see Tesserax post):
http://discussions.apple.com/thread.jspa?threadID=1067565
One interesting thing re: 5.2.1 is that the "Administrative access denied" errors summarized above disappeared. As explained in a post reference above, the going theory is that this a permissions/keychain problem new and unique to AirPort Utility 5.3.1. However, even though 5.2.1 does have a slightly different interface with different settings, I still couldn't get the WDS to work.
EVENTUALLY, I came across this post:
http://discussions.apple.com/thread.jspa?threadID=1422527
MuaddibOfArrakis walks through setting up a WDS from scratch, and the workflow is different than what is possible with either AirPort Utility 5.3.1 or 5.2.1. He's doing it with the old version of AirPort Admin Utility, which I fortunately saved a copy of many moons ago when I had somewhat-related problems with my WDS (since forgotten). In fact, it's a lot easier. What's nice about this older app is that it literally does the heavy lifting of "connecting" the AEBS and AEX units during the configuration -- it reboots both at the same time as the config is happening, and lets you choose from a list of available units to "add" to your WDS network. In short, it's a FAR SUPERIOR workflow even though some of the GUI isn't as intuitive as the newer AirPort Utilities that were designed to replace it.
SOLUTION:
If still have a copy of the AirPort Admin Utility follow the instructions from MuaddibOfArrakis here:
http://discussions.apple.com/thread.jspa?threadID=1422527
If not, try setting up your WDS network using AirPort Utility (hereafter AU), with these configs (take from my now-working network), as viewed through AirPort Utility 5.3.1.
I. Configure your AEBS.
Select the AEBS from AU, and choose "Manual Setup"
1. Under the AirPort tab up top:
a. Under "Base Station" sub-tab:
i.) assign a name for that specific unit, so you can later identify the specific unit from the list of units -- this is the name that will show up beside the unit in the AU list of configurable units. You can name it something like "kitchen", or "office". I have mine numbered, so XXXXXv1, XXXXXv2 etc where the XXXXX is the name of the shared network and the numbers help me tell the units apart. Just be sure you name each uniquely, and if you have several you might write the name on the unit itself.
ii.) pick a password for logging into that unit. This is different from the network password, its a security check to get in and change the configs on this unit later. Be sure to remember it in your keychain for the sake of simplicity, and write it down somewhere secure.
iii.) if you choose to set time automatically, pick a location that you will use consistently across all your units. I use time.apple.com.
iv.) uncheck "Allow configuration over Ethernet WAN port" unless you want to be able to remotely mess with settings -- which you almost certainly do not need to do.
v.) I left the "Options" button alone - no settings there.
b. Under the "Wireless" sub-tab:
i.) Wireless Mode: "Participate in a WDS network"
ii.) Network Name: this will be the name of your wifi network shared by all units, so be sure to remember what you pick. If you are already connected to this AEBS via wifi while you are making these changes, then you can use the same wifi name you already have set up -- you don't have to change it. Note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
iii.) pick a Radio Mode. I'm using b/g compatible. You'll want to do the same, unless you are on the new gigabit AEX. I'm pretty sure about this, but not 100% -- others post if I'm wrong.
iv.) choose a Channel. This can be a more complicated procedure, but for now just pick something consistent across all your units. If you get everything working and find that you're having intermittent network problems, you could later try changing your Channel -- it can pick up interference from phones, microwaves, etc and changing it can help.
v.) I have wireless security set to WPA/WPA2 Personal.
vi.) Wireless Password is the password for access to your wifi network (not your unit itself). If you are connecting to your AEBS via wifi while doing this config, then you can use the same password you have already set up. Pick a good one unless you want other folks jumping on your wifi and stealing your bandwidth and/or credit card numbers . Remember it in your keychain and write it down someplace secure, because you'll need it for the other units too. As noted above, note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
vii.) Click the "Wireless Options" button. I have my multicast rate set to 2mbps, transmit at 100%, timeout at 1 hour, and i have checked the "Create a closed network". This last step keeps your network from advertising itself to the outside world. Users can only find it by explicitly typing the network name into their wifi settings (e.g. AirPort -> Other... then enter Network Name, Security and Password). I leave interference robustness unchecked.
c. Under the "WDS" sub-tab:
i.) the AEBS should have it's WDS Mode set to "WDS main".
ii.) Check the "allow wireless clients" box on the AEBS; this lets you connect client machines to it directly too.
iii.) hit the plus button to add the Remote system (AEX). There are two types of configs for the AEX's - "remote" and "relay". Assuming you have 3 units like me (2 AEX and 1 AEBS) the key question is whether you will place each AEX within direct reach of the AEBS (remotes), or if you will have one AEX in the middle connecting to an AEBS on one side and an AEX on the other -- where the furthest AEX is out of reach from the AEBS (remote) and connects only to the AEX in the middle (relay). I'm using a relay setup. If you are using relay, you can still set up the AEX relay to serve client computers too -- it doesnt have to JUST relay. More on that later. For now, you want to add only AEX units that will talk DIRECTLY to the AEBS. So if you have a setup like mine, just add one (the one in the middle - the relay). If you have two remotes connecting directly to the AEBS, you will add them both here. When you hit the '+' button it will ask for both an ID and description. For description I use the name I'm assigning to each unique unit (as above, "kitchen" or XXXXXv1 or whatever you use). For AirPort ID, use the number listed on the AEX unit itself (not the number for "Ethernet", also on the AEX unit).
d. Under the "Access" sub-tab:
i.) I have it set to "Not Enabled". I'd suggest you start that way too, and you can go change it later if you get everything working correctly.
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: Ethernet
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Share a public IP address
b. Under the "DHCP" sub-tab:
i.) DHCP Beginning Address: 10.0 . 1 . 2
ii.) DHCP Ending Address: 10.0.1.200
DHCP Lease: 4 hours
c. Under the "NAT" sub-tab:
i.) nothing should be checked;
ii.) nothing under Port Mappings either
3. Under the "Printers and Advanced" tabs up top:
Nothing special needs to be configured there.
THAT'S IT.
=============
I. Configure your AEX(s)
Select the AEX from AU, and choose "Manual Setup"
1. Under the "AirPort" tab up top:
a. Under "Base Station" sub-tab:
i.) pick a unique name for this unit, same logic as for AEBS
ii.) pick a password specific for accessing this unit, same logic as for AEBS
iii.) Set time automatically: be sure to use the same settings used on your AEBS
iv.) Options: no need to set any
b. Under "Wireless" sub-tab:
i.) Wireless Mode: Participate in a WDS network
ii.) Network Name: same name used for AEBS, this is the name of your wifi network
iii.) Channel: same as AEBS
iv.) All settings here (those above, plus Security and Password & in Options button) should be the same as for AEBS settings on this tab
c. Under the "WDS" sub-tab:
...if AEX is "in the middle" (as described above):
i.) WDS Mode: WDS relay
ii.) Allow wireless clients: check (unless you only want to bridge between the edges without letting folks connect on this AEX in the middle)
iii.) WDS Main: set to the AirPort ID (aka MAC address) for the AEBS. You can find it on the bottom of the AEBS, either labeled as such or at the bottom beside the logo of a wireless signal (square logo, with semi-circles mimicing a radio signal).
iv.) WDS Remotes: click the '+' to add any AEX's that will connect to this relay rather than directly to the AEBS. Same deal as above, use the name in the description and use the AirPort ID from the side of the AEX (not the Ethernet ID).
.....if AEX is connecting to a relay ("on the end", as above) or if there is no relay and AEX connects directly to the AEBS:
i.) WDS Model: WDS remote
ii.) Allow wireless clients: checked
iii.) WDS Main: if connected to a relay, use the AirPort ID of the relay AEX. If connected to the AEBS directly, use the AirPort ID of the AEBS
d. Under the "Access" sub-tab:
i.) MAC Address Access Control: Not Enabled (for now, you can change later)
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: AirPort (WDS) -- should be selected and gray'ed out.
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Off (Bridge Mode)
3. Under the Music, Printers and Advanced tabs up top:
Nothing special needs to be configured there. You can worry about AirTunes settings later...
That should be it. I'd recommend setting up the AEBS first, then the relay (if applicable), then the remotes. Initially, you can bring each unit in the same room with you for configuring. After configured and restarted the AEX should blink then turn solid green. If it turns green you should be good to go.
HOPE THIS HELPS. As noted above, I did not config through AirPort Utility 5.3.1 so I haven't tested this procedure through that app. However, after getting my network to work I went back and transposed all settings into this post to help others. Please provide feedback on whether or not this is working, so we can collectively try to move towards a setup procedure that works for everyone....
Good luck!
Message was edited by: b.byrdI'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. -
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� 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 -
Unable to access internet via my airport extreme base station
I have an AirPort Extreme Base Station which is hard wired to a Mac and which communicates wirelessly to a Mac in another room. My internet access is via comcast. Direct connection from this computer to my modem works fine, but not if I go through the AirPort. The LED lights of the AirPort indicate normal network activity, (flashing/on/flashing). I have tried disconnecting and reconnecting everything and rebooting the computer. The system has been working normally through the AirPort until today.
I would recommend that you do the following as a minimum:
Power-down the modem, AirPort base station, and computer(s).
(OPTIONAL) Disconnect the AirPort base station from the Internet broadband modem.
(OPTIONAL) While all of the devices are powered-down, perform a "factory default" reset on the base station. This will get it back to its "out-of-the-box" configuration and make setting it up much easier, especially if you use the "Assist me" process within the AirPort Utility. (ref: Resetting an AirPort Base Station or Time Capsule)
(OPTIONAL) After the base station resets, go ahead and power it back down.
(OPTIONAL) Reconnect the AirPort base station to the Internet broadband modem. For the Extreme and Time Capsule, be sure to connect the cable to the base station's WAN (circle-of-dots) port.
Power-up the modem; wait at least 10-15 minutes to allow it adequate time to initialize.
Power-up the AirPort base station; wait at least 5-10 minutes. Note: The AirPort's status light may continue to flash amber after it has intialized. That is because, there may be some additional configuration items necessary, like setting up wireless security, before the overall setup is completed to get a green status.
Power-up your computer(s).
In this basic configuration, the AirPort base station will broadcast an unsecured wireless network with a Network Name (SSID) of Apple Network NNNNNN. Network clients, connected to the base station either by wire or wireless, should now be able to access the Internet through the ISP's modem. Once Internet connectivity has been verified, you can use the AirPort Utility to configure the base station for wireless security and any other desired options. Please post back your results. -
Airport Extreme Base Station N adjusts time, then drops WDS
I have a WDS network with a +Time Capsule+ (TC = WDS Main) and an +Airport Extreme Base Station with 802.11n+ (AEBSn = WDS Remote). Everything works great - except when it doesn't. The AEBSn will suddenly drop the connection, and instead of a normal IP address (10.0.1.11) it will get a self-assigned one (e.g. 169.254.130.58). I have pawed through a number of log files, and I see that at the point that things go south, I get a whacky net-time update; for example:
Jul 31 20:25:21 Severity:5 Internet Configuration leased -- host <10.0.1.11/255.255.255.0> gateway <10.0.1.1> dns <10.0.1.1> wins lease <14400> domain <dclient.lsne.ch>
Jul 31 19:54:15 Severity:5 Clock synchronized to network time server time.euro.apple.com (adjusted -3606 seconds).
Jul 31 20:55:35 Severity:3 No Address for NTP server time.euro.apple.com.
Note the 1-hour backwards time adjustment; after that, the AEBSn has dropped the connection. Note that there was no user traffic on the network at the time - no one was home.
Sometimes the status light on the AEBSn will go yellow, sometimes it stays green - I haven't been able to detect a pattern to that. The TC is zen: he's green no matter what happens. I thought he was supposed to be a caring master?
I thought this was perhaps related to interference from other wireless networks - I live in the city and there are a bunch around me - so I moved to the least-used primary frequency band: no change.
Help!!! This is driving me bananas. Thanks in advance.Bob,
Thanks for the response, and sorry for taking so long to get back. I think I found how to fix the problem of the dropped WDS connections, and I wanted to give it a while to make sure the problem was really fixed.
The drops got to be more and more frequent, until finally the WDS connection would drop pretty much immediately. At that point, the TC (the master in my setup) for the first time started showing signs of being unhappy: the status light would briefly flash orange at irregular intervals (I could see nothing relevant in the log file, though). I had always assumed the problem was at the AEBS end, and had always restarted him, but this time I tried restarting the TC - and bingo presto, everything started working, and has been working for over a month now, without ever restarting the AEBS.
I would guess that there's something in the WDS implementation (at least on the TC) that gradually degrades over the period of many months - memory leak or fragmentation or similar.
Thanks for the suggestion about the "extend a wireless network" option. When I read the manual, I got the impression that was just an automated way of setting up WDS; I didn't realize that it affects the band used. I now realize that the title of the section, "Extending the Range *of an 802.11n Network*," is not totally anodyne. Anyway, I just now set it up as you suggested, and so far, so good.
Thanks again,
-- Philip -
New iPhone &iPad 2 working with Extreme Base Station Model A1034
iPad 2 worked with Extreme Base Station Model A1034. Now new iPhone and now neither can connect to the Base Station. What could be the reason for the iPad 2 to stop working with the Base Station and why can't the iPhone use the Base Station? Thank you!
At this point are you saying that none of your wireless clients can connect to the AirPort? If so, then I would recommend that you do the following:
I would recommend that you do the following as a minimum:
Power-down the modem, AirPort base station, and computer(s).
Power-up the modem; wait at least 10-15 minutes to allow it adequate time to initialize.
Power-up the AirPort base station; wait at least 5-10 minutes. Note: The AirPort's status light may continue to flash amber after it has intialized. That is because, there may be some additional configuration items necessary, like setting up wireless security, before the overall setup is completed to get a green status.
Power-up your computer(s).
If the above steps do not solve the problem, start over with step 1 above, but then perform the next steps between steps 1 & 2. above.
Disconnect the AirPort base station from the Internet broadband modem.
While all of the devices are powered-down, perform a "factory default" reset on the base station. This will get it back to its "out-of-the-box" configuration and make setting it up much easier, especially if you use the "Assist me" process within the AirPort Utility. (ref:Resetting an AirPort Base Station or Time Capsule)
After the base station resets, go ahead and power it back down.
Reconnect the AirPort base station to the Internet broadband modem. For the Extreme and Time Capsule, be sure to connect the cable to the base station's WAN (circle-of-dots) port.
Continue with step 2 in the first set of steps.
In this basic configuration, the AirPort base station will broadcast an unsecured wireless network with a Network Name (SSID) of Apple Network NNNNNN. Network clients, connected to the base station either by wire or wireless, should now be able to access the Internet through the ISP's modem. Once Internet connectivity has been verified, you can use the AirPort Utility to configure the base station for wireless security and any other desired options. Please post back your results. -
Airport Extreme Base station cannot connect to Westell C90-36R516-01 DSL modem
Hi,
I just purchased a new Airport Extreme Base station for my 15" Macbook Pro. I set everything up this morning per the docs (all cables are connected properly) but the Airport Extreme is flashing an amber LED, which means it cannot establish communication to the network/Internet.
I'm using an old Westell C90-36R516-01 DSL modem that has been working fine up until now. I've tried switching out the Ethernet cables and different powering on/off combos but nothing appears to work. When I connect the Ethernet cable directly into my laptop, I have to power down the DSL modem, power it back on, and then do several refreshes before I finally get an Internet connection.
I read a previous post about unplugging the modem overnight and then plugging it in the next morning to wipe out the MAC address setting. I will be trying that tonight, but I was wondering if there was anything else I could try in the meantime? Or, is it simply a matter of having to get a newer modem from Verizon because this one is 7-8 years old?
Thanks for any help you can provide.
Solved!
Go to Solution.Hi Max,
Let's start from the beginning,
The ethernet from the modem should be wired to the Wan port of the Airport...
On page 28 of the users manual it says if the light flashes amber you should unplug the power of the modem, wait a few seconds and power up the modem.
I presume you installed the Airport utility from the disk that came with the Airport?
For more information about the reason the light flashes
Open AirPort Utility, select your base station, and then choose Manual Setup from the Base Station menu. ClickBase Station Status to display information about the flashing light
Here is a link to the Manual CLICK HERE
I was hoping to find out more about the Airport utility to see what's it's capable of doing...
Maybe you are looking for
-
ITunes will not add files to my Library
Greetings. My iTunes will not add my recent downloads to my library. I have tried adding the entire folder to the library and adding each song individually with no success. Please help if you can. Thanks for reading.
-
Problem with accounting in group currency ( tbb1 )
Dear all, to use the group currency, we created a new valuation area. In case of a new exchange rate we need to account transactions in the correct way; to do this we applied sap notes: - 1526242 u2013 TBB1: Incorrect amount in valuation -
-
How to resolve the problem of "Update was terminated" when posting
hello, please give me a favor. I met a big problem when running FB01, the system give me the error message: Express document "Update was terminated" received from author. I test all clients, all of them have the same problem, how to resolve. I use SA
-
How to make Safari automatically open .ram sound clips?
When I click on, say a a sound clip to preview music, Safari just downloads the file but does not automatically play it, so I have to click on the file for it to be played by RealPlayer instead of this happening automatically after the download. The
-
Error in importing purchase invoice.
I am using sap business one 2005.I have imported items,bom and business partners.When I import purchase invoice it gave me following error- Exchange rate not updated [PCH1.RG23Part2][line:1],'USD' Application-defined or object defined error 65171. Th