Airport Extreme Base signal knocked out by Linksys LinkExtender

After installing a new AE Base and configuring it, all the computers in the house connect fine with a strong signal, but when the Linksys Link Extender is plugged in to enable a computer in an adjacent building to get a stronger signal, the AE Base signal gets weaker, another network shows up (on AirTrafficControl) and some older Apple computers are dropped off the internet.
Is there some configuring that needs to be done to the Extender so it will not do this, or is there a better way to connect an older PC to this airport system?
Many thanks,
...Tom

(Extreme BS is early model two ethernet conns, I think renamed snow)
No. The dual Ethernet (aka snow) 802.11b AirPort base station (ABS) is completely different than a round 802.11b/g AirPort Extreme base station (AEBS).
Identifying AirPort hardware

Similar Messages

Does firmware update 7.1 break the Airport Extreme Base Station?

Does firmware update 7.1 break the Airport Extreme Base Station?
See Digg
http://www.jayhaynes.net/2007/04/donot_install.html
April 10, 2007
Do NOT install AirPort 802.11n Firmware 7.1
This Firmware 7.1 update for AirPort Extreme Base Station with 802.11n should definitely NOT be installed.
Here was my problem:
I used AirPort Utility 5.1 to install the update. It is automatic - launch the utility and it asks if you want to install the update. I said yes because I had problems getting two AirPort n base stations networking together to extend my range (I gave up finally and just used an AirPort Express to extend the range).
After the firmware update, some sites would not load at all (www.nytimes.com) and others took forever to load. And worse, I could not send any email from any of my IMAP accounts. It seemed to be a DNS problem.
I have two 802.11n AirPorts, so I finally went back to the other one (7.0) and everything worked fine. The Apple tech support guy offered to replace my broken (7.1) AirPort.
Foolishly, I wanted to make sure the problem was actually with the 7.1 update and not the AirPort itself. So I updated my second 802.11n base station with 7.1. And it casued the exact same problem (some sites not loading, no outgoing email).
The Apple tech (at this point I was speaking with a wireless specialist) put me on hold to test a few of his AirPorts to see if he could revert back to firmware 7.0 or (ii) install a clean version of 7.1 (in case the version on my drive was corrupted).
Unfotunately neither option was possible, which is a design flaw in AirPort Utility.
Apple is sending me two new AirPorts in 1-2 days, which is great service, but I will not be installing firmware update 7.1 again. Fool me once...
http://www.apple.com/support/downloads/airportextremebasestationwith80211nfirmwa re71.html
AirPort Extreme Base Station

Turns out that the firmware 7.1 does not render the AEBS useless.
My problem was resolved when I turned off my DSL modem, the AEBS and the computer. Then restarted in same order going to the next one after the first is compeletly up and running. I had no problems whatsoever after that.
Seems that the firmware update makes the IPs 'stick' somehow. I would think that even a reset of AEBS might have done it but I never got to that stage.
All my computers came alive in no time.
I suggest Smith tries this. Simply reset the whole network. Ah yes, my cable modem has an internal battery, I needed to disconnect this too. Only then did the modem go into the 'acquiring' or 'distribution' mode.

Connect to Linksys Cable Gateway via AirPort Extreme Base Station?

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

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

Airport Extreme base station vs. Linksys router

Hi all -- I have a tech choice to make and I'm soliciting advice and war stories from those who have been in my place.
I have a DSL connection, G5 Mac and a Windows laptop. I've been connecting to the Internet via a Linksys WRT54G router -- the Mac is connected to the router via Ethernet, and the Windows machine connects wirelessly -- and I've been happy with this setup. I have it on good authority that I'll be getting an Airport Express in my stocking this year; I had done a little research and found that it is possible to make the WRT54G and the Airport Express work together, and was planning on doing some hacking and fiddling to make that happen in the new year.
However, last night my WRT54G seems to have died a horrible death -- all its lights started blinking at once, the Internet connection went away, then all the lights went out except for the "diagnostic" light, and now no lights come on at all. No idea what happened, but it seems pretty kaput.
So! I'm in need of a new wireless base station. I could get an Airport Extreme base station, or I could get another Linksys (or another off-the-shelf 802.11 router, but we'll just use "Linksys" as the catch-all phrase here to mean "not an Airport Extreme base station"). The most obvious difference is price -- the Airport Extreme station is $200, while the Linksys is more like $65. Another thing that irks me about the AE station is that it only has one LAN port. I do like being able to plug in my laptop to the wired network to do some diagnostics once in a while and it'd be a pain to have to disconnect my Mac to do so. And then there's nagging worries that the AE base station might not work as well with my Windows laptop.
On the other hand, I'm sure that setting up the Airport Express would be much, much easier with the AE base station. And I do like the idea of the base station being able to dial up if my DSL goes down (as it does from time to time). Basically, I am tempted by the AE base station feature-wise, but I'm kind of balking at paying three times the price and not getting even a second LAN port. Any advice, particularly from people who have used both types of routers in a mixed network, would be appreciated.

Replace your Linksys with another WRT54G. Then you can hook up your anticipated AX as either a client (connected like a computer), a wireless access point (connected using ethernet with DHCP disabled on the AX), or using WDS:
http://discussions.apple.com/click.jspa?searchID=-1&messageID=607414

Very weak Airport Extreme Base Station signal...

Hi --
I've been searching the forums here for some solution but haven't been able to find anything. I'm trying to upgrade my parent's wireless network in their home and they've had an Airport Extreme base station for a couple of years now. I recently switched them to broadband which is much faster than the crappy DSL they used to have but the problem that still exists (one that they've always had) is an incredibly weak Airport Base Station signal.
I've tried using different laptops and computers on it, but all of them register the same weak signal. Having my laptop 12 inches from the base station only gives me three bars. From three feet away it drops to two and anything over six feet is a 1 bar or nothing and that's all int he same room. Trying to access it from an adjacent room is fruitless.
Like I said, it's like this for all computers I've tested. Anyone know what's up with this? Is the base station on the fritz? I have the latest software update for it as far as I know.
Thanks.

That's a good, helpful list but we don't really have any of those potential interfereces. Like I said, this signal is down to two bars from five feet away and only three bars from literally six inches away, so there's really not a lot of room for intererence from that distance anywat.
I've seen people wondering if the latest firmware update for Airport might be causing this, but I'm wondering if the Airport base station itself is maybe in the fritz. I guess I could try getting a new one. Anyone else out there have any other ideas?

Can't use my HP Deskjet F4580 Wireless Printer with the AirPort Extreme Base. The printer is NOT connected at the USB port of the AirPort Extreme, and is placed in another room. It worked just fine with my previous router (Linksys WRT54G). Help me!

Hey Guys!
I just got my AirPort Extreme Base, but I can't use my HP Deskjet F4580 wireless printer with it.
The printer is not connected to the AirPort Extreme's USB port. It is placed in another room, and I'd like to use it (the printer) wirelessly (not connected to the USB port os the AirPort Extreme), as I used to. There is no place for the printer close the AirPort Extreme. It worked just fine with my previous wireless router (Linksys WRT54G). I'm very disappointed with the AirPort Extreme Base Station because of that!...
Can you help me? Please?!
Thanks Folks!

This must be a tough one, no suggestions at all.

Cheapest way to repeat my Airport Extreme Base Station signal

Are there any other options to repeating my network throughout my house besides buying another Base Station , or express?

Steve, First welcome to the discussions.
I may be a little confused.
When you have an Internet connection in your house, it comes in at a single access point and from there can be distributed throughout your house to different areas in a couple of different ways.
If you choose it can be done with a wireless router, if your computers have wireless cards installed.
Or you can hard wire them, direct into a wired router, thus not needing wireless cards in your computers. They will connect with ethernet cables (Cat 5 or Cat 6).
There are a multitude of ways to connect throughout your house.
The easiest is Wireless, connecting from your Internet Service Providers Modem to your choice of Wireless Router which will enable the distribution of different IP addresses to multiable computers.
If you happen to have a real large house you can extend the range to cover remote areas that are out of the normal range of Airport Extreme Base if that happens to be your choice of Router.
Airport Express can be used to extend the range of Airport Extreme Base.
Cheers Don

Can I use the Airport Extreme Base Station with my already existing D-Link router to increase signal strength?

I already own a wireless router that I would like to keep. Could I use this Airport Extreme Base Station to improve that signal strangth to my room from the living room or to the basement? Would I have to hard-wire both the Base Station and my existing router? You probably have read this question more than once, and I have read some questions of this product too, but for some reason these Apple products I have some trouble with.

Could I use this Airport Extreme Base Station to improve that signal strangth to my room from the living room or to the basement?
Yes
Would I have to hard-wire both the Base Station and my existing router?
Yes

What is the most sensible way to extend a wifi signal. I am in a cinderblock house and I have to buy something that will give me a single network but added range from my airport extreme base station.

What is the most sensible way to extend a wifi signal. I am in a cinderblock house and I have to buy something that will give me a single network but added range from my airport extreme base station.

Use an Airport Express. Configure the AEBS to allow it's wireless network to be extended. This is a dropdown menu option under the Wireless tab. Configure the Airport Express to Extend an Existing Network also under it's Wireless tab. You will need to provide the name of your network used in the AEBS as well as the network's access password.

Is an updated version of the Apple Airport Extreme Base Station due to come out soon?

Is an updated version of the Apple Airport Extreme Base Station due to come out soon?

On a User to User Support Area, we are all users here, just like you.
No one here will know what a notoriously secretive company like Apple might plan to do, unless Apple has made an official announcement in that regard.
Anything else that you might have "heard", would be either rumor or speculation.
We try hard not to deal with either of these things on this support area.

Configure TC and Airport Extreme Base Stations with different channels

I had to do some serious workarounds to use the Airport Extreme Base Stations as an access point with the same wireless network name primarily due to channel overlap. I thought I would post my results here since I didnt' find a good article online.
Also, I found the Snow Leopard verison (5.4.2) of the Airport Setup Utility far superior to Lion's Airport Utility (6.x) in terms of advanced setup.
Setup is a 3 flloor house where the 3 wired network locations have wireless overlap. The problem was that the access points would not hand off the wireless signal because the channels for each airport/TC were automatically set to the same channel. In non-apple setups, this is how you force a wireless client to switch access points (since the wireless software on your client/mac/windows can detect which access point is stronger and moves to the alternate channel.
Using apple's "Extend this wireless network" option removes any ability to manually configure wireless channels. I am writing this from memory, so feel free to ask questions and I will track this topic:
Procedure
Setup time capsule as your base station. Do all the setup for your wireless and guest networks. Manually configure the network and change the wireless channel to a specific channel for a/b/g networks (e.g., 3) and n networks (e.g, 167).
Plug your first airport extreme/access point into your wired network. Do not plug it into the "internet" ethernet plug, use one of the 3 ethernet switch locations
Use the airport utility to first configure it to "extend" your wired network.
Then, go in and reconfigure it manually in the airport utility. Choose the option to setup a "new network" and name the network the same as the TC wireless network name, security, etc.
Change the channel from "auto" to a different channel than the TC (e.g., 6 and 137).
Now go to the top tab and click on the "internet" icon
Go to the DHCP tab and change it to "bridge mode." This will tell the AE to not give out IP addresses (the TC will do this for you). If you get an error that the IP ranges conflict, you have not done this
Note that if you have a guest network setup, you will need to set this up on the AE as well.
Now test your airport setup. Take your client (macbook, iOS device) and connect to your network. Move to a spot near the TC and pull up a web page. Keep an eye on the signal strength and beginv moving toward the AE. Refresh the page as you move around. You should at some point see the signal strength increase. Refresh your page again. You should be now connected to to the AE. I have found that Macbooks do a better job than iOS devices because you get an extra signal bar to measure strength, and they have larger antennas which allows you to better measure problems with handoff
Another test you can do is to start backing up on your TC and then test the move. The handoff will truly show you that the TC is handling the process but the AE is relaying to the TC for backup.
If you need to setup another AE, simply follow setups 3-10.
I hope this helps others. I've done this setup 100 times on Linksys devices and although they are cumbersome, they at least allow me to do this setup much more quickly and easily than the apple products.

I had to do some serious workarounds to use the Airport Extreme Base Stations as an access point with the same wireless network name primarily due to channel overlap. I thought I would post my results here since I didnt' find a good article online.
Also, I found the Snow Leopard verison (5.4.2) of the Airport Setup Utility far superior to Lion's Airport Utility (6.x) in terms of advanced setup.
Setup is a 3 flloor house where the 3 wired network locations have wireless overlap. The problem was that the access points would not hand off the wireless signal because the channels for each airport/TC were automatically set to the same channel. In non-apple setups, this is how you force a wireless client to switch access points (since the wireless software on your client/mac/windows can detect which access point is stronger and moves to the alternate channel.
Using apple's "Extend this wireless network" option removes any ability to manually configure wireless channels. I am writing this from memory, so feel free to ask questions and I will track this topic:
Procedure
Setup time capsule as your base station. Do all the setup for your wireless and guest networks. Manually configure the network and change the wireless channel to a specific channel for a/b/g networks (e.g., 3) and n networks (e.g, 167).
Plug your first airport extreme/access point into your wired network. Do not plug it into the "internet" ethernet plug, use one of the 3 ethernet switch locations
Use the airport utility to first configure it to "extend" your wired network.
Then, go in and reconfigure it manually in the airport utility. Choose the option to setup a "new network" and name the network the same as the TC wireless network name, security, etc.
Change the channel from "auto" to a different channel than the TC (e.g., 6 and 137).
Now go to the top tab and click on the "internet" icon
Go to the DHCP tab and change it to "bridge mode." This will tell the AE to not give out IP addresses (the TC will do this for you). If you get an error that the IP ranges conflict, you have not done this
Note that if you have a guest network setup, you will need to set this up on the AE as well.
Now test your airport setup. Take your client (macbook, iOS device) and connect to your network. Move to a spot near the TC and pull up a web page. Keep an eye on the signal strength and beginv moving toward the AE. Refresh the page as you move around. You should at some point see the signal strength increase. Refresh your page again. You should be now connected to to the AE. I have found that Macbooks do a better job than iOS devices because you get an extra signal bar to measure strength, and they have larger antennas which allows you to better measure problems with handoff
Another test you can do is to start backing up on your TC and then test the move. The handoff will truly show you that the TC is handling the process but the AE is relaying to the TC for backup.
If you need to setup another AE, simply follow setups 3-10.
I hope this helps others. I've done this setup 100 times on Linksys devices and although they are cumbersome, they at least allow me to do this setup much more quickly and easily than the apple products.

AirPort, older AirPort Extreme Base Station, AirPort Express, Newer AirPort Extreme Base Station

This may sound like a fairly dumb question, but here goes anyway:
I have a 27" iMac with the following AirPort Extreme card:
Card Type: AirPort Extreme (0x168C, 0x8F)
Firmware Version: Atheros 9280: 2.1.14.6
For a Base Station, I'm currently using a pretty long-in-the-tooth M8799LL/A AirPort Extreme Base Station (with modem and antenna port)
I recently bought an Airport Express:
AirPort Express MB321LL/A (A1264) to
A. Use AirTunes to send iTunes from my Man Cave on the first floor at one end of the house to the family room on the first floor at the other, where it will connect to an A/V setup, and, probably, one of my USB printers
B. Act as a repeater for the AirPort Extreme Base Station, which is physically closer to the Man Cave than to the family room. My wife and I use our ancient-but-hangin'-in-there iBook G4s in the family room (and upstairs) to check email, eBay, etc. Both in the family room and especially upstairs, we sometimes get only 2-3 bars on the AirPort signal strength indicator in the menu bar.
I see that I can get, from a well-known third-party retailer, an AirPort Extreme 802.11n A1143 (1st Generation), for an exceptionally reasonable price.
My question is, what would getting the AirPort Extreme 802.11n A1143 do for me, if anything? I know it would give me one more signal source in the repeater chain, and I could probably put the Auld Nyle M8799LL/A in the stairway or upstairs to boost the signal upstairs, and I could use the USB port in the AirPort Extreme A1143 for connecting another USB printer or USB external hard drive (would this drive be available to any Mac on the AirPort network?)
Any other configuration possibilities and suggestions greatly appreciated!
Peace & Love
Bart Brown

Thank you for the prompt reply and the very helpful links. I'm going through all the support docs right now, but from your explanation and what I've seen in the support docs so far, it would appear that the maximum bandwidth is achieved by a physically-connected "Roaming Network."
I'm so out of it, I'm afraid I'd never heard of "Powerline adapters," but I looked them up, and I guess this is the system that uses "Romex" - style standard house wiring to carry signal, which cuts down on each individual Base Station's power overhead (does it also affect bandwidth?).
I see a lot of names selling these adapters -- Western, D-Link, NETGEAR, ZyXEL, Monster, Sling Media, PowerNet, Cisco-Linksys, Actiontec, Medialink, Rosewill, TRENDnet -- and a lot of different configurations: 1 port, 2 ports, 4 ports. Basically I have one 27" iMac that doesn't go anywhere (it's not too portable!), a couple iBook G4s, and a point where I want to run 1/8" mini-jack-to-RCA L/R audio cable from the AirPort Express to an A/V receiver. I doubt this configuration is going to change, as I'm 63, and too lazy to lug stuff around if I don't have to. What do you think would be the best solution for me, considering I just ordered the AEBSn and I already have a brand-new AXn. Should the 27" iMac, since it ain't movin', be connected by ethernet/"Powerline adapter", rather than relying on the internal Airport Extreme card? I guess what I'm asking is, given what I want to do, how many of these Powerline adapters, what kind (do you recommend), with how many ethernet ports do I need?
Thank you again for your prompt and informed help.
Bart Brown

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

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

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

Solution to Airport Extreme Base Station + Airport Express networking probs

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

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

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

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

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

Airport Extreme Base signal knocked out by Linksys LinkExtender

Similar Messages

Maybe you are looking for