Adding an Airport Express to an Extreme Base Station
I have an Airport Extreme Base Station and it has been operating for several months, I decided to add an Airport Express to extend the range and it appeared that it was a simple process. NOT. The Express instructions indicated that when downloading the software to follow the instructions on setting up a network but it will not get that far in that I get an error message telling me I have a newer version of I Tunes and it stops the install. I have gone through the tech support pages here and am at a loss on how to get this connected. Can anyone help provide me a step by step method to do this? Thanks
On this same topic;
We have a new Extreme base station that connects 1 MBP, (wirelessly), 1 HP Laptop (wirelessly) and 2 PC (via ethernet) to the internet.
All of the computers can see and use the Extreme base station and the printer connected to it via USB.
We also have an Airport Express that the two laptops can see. This has a printer connected to it as well via USB. (both are new Canon printers and all of the software for each, and their drivers are loaded on all computers).
Both the Extreme and Express have a steady green light, their own names and are set up on the same network.
Though my MBP can see both the Extreme and Express, neither "see" each other as far as I can tell. And, the printer connected to the Express cannot be seen in either Bonjour Printers, or anywhere else.
Also, in order to "attempt" to find the printer connected to the Express, I have to disconnect from the Extreme Base Station and connect to the Express.
How can I get the printer (connected to the Express) to show up in my pick list of printers WITHOUT having to disconnect from the Extreme and connect to the Express. Also, how can we get the Express to be connected to the internet via the Extreme?
All searches here and documents I have poured though do not address this issue and we'd really like to get this straightened out. I am willing to take a lot of time to do this, but do it right.
Can someone please help me with this?
Thank you in advance,
~ J
Similar Messages
-
I bought a new airport time capsule 3tb to be used to save to file all my pictures. Can I use it as network client and the airport express as the
Primary base station?To my opinion this looks a bit like what I'm looking for.
At the moment I have an Imac that is wireless connected to a 2TB time capsule (TC1).
To this time capsule I have another 2TB time capsule (TC2) connected via a upt wire connection.
At the moment there is a backup made via time machine from the Imac to the time capsule TC1 (the second TC is not used)
I'm not so technical so I hope you understand the configuration.
What do I want to achieve :
copy all my data from the Imac to TC1 so that the information can be accessed by more users.
create an automatic backup from TC1 to TC2 (mirror or raid system) for security.
give access to some users on the network to access TC1 to read and write data.
TC2 only serves as backup from TC1 and no direct access is needed to this disk.
If there is a solution, thanks for explaining it in 'IT kindergarden style' so that I can understand and use the info.
Many thanks in advance. -
Extending network with Airport Express from Time Capsule Base Station
I have a working Time Capsule wireless base station that's setup and working successfully. I want to extend my network and connect to my stereo for playing via iTunes. I've spent hours trying to get the Airport Express to connect.
What's the correct basic approach? Time Capsule base and adding the AE to the network? Setting up WDS? If anyone has the proper settings for both the TC and the AE I would be very appreciative.I still say this needs to be addressed by Apple on why there isn't 2 different forums for the old Express or the new Express.... Just like the Extreme Base Station. A lot of time is wasted on the forum on which Express a person has.....
1. Old Express with "g" ????
2. New Express with "n" ????
If you have the old Express, you need to set it up using WDS along with the TC.
If you have a new Express, then you can just check the TC settings for "allow this network to be extended" and set the Express to extend the network. This is much easier than setting up a WDS.
Good Luck
Joseph Kriz -
Remote administration of Express in an Extreme Base Station network
I am a newb administrator of a small network of an AEBS with 2 Expresses in "extend a network" mode. I can access the Base Station over the internet but I haven't figured out how I can do the same with the Expresses.
Also, I understand that MAC filtering is unavailable for the Expresses in "ext a net" mode. Is this correct? It seems to be operational for the Base Station but even restricted MAC addys can access the network through the ExpressesOn this same topic;
We have a new Extreme base station that connects 1 MBP, (wirelessly), 1 HP Laptop (wirelessly) and 2 PC (via ethernet) to the internet.
All of the computers can see and use the Extreme base station and the printer connected to it via USB.
We also have an Airport Express that the two laptops can see. This has a printer connected to it as well via USB. (both are new Canon printers and all of the software for each, and their drivers are loaded on all computers).
Both the Extreme and Express have a steady green light, their own names and are set up on the same network.
Though my MBP can see both the Extreme and Express, neither "see" each other as far as I can tell. And, the printer connected to the Express cannot be seen in either Bonjour Printers, or anywhere else.
Also, in order to "attempt" to find the printer connected to the Express, I have to disconnect from the Extreme Base Station and connect to the Express.
How can I get the printer (connected to the Express) to show up in my pick list of printers WITHOUT having to disconnect from the Extreme and connect to the Express. Also, how can we get the Express to be connected to the internet via the Extreme?
All searches here and documents I have poured though do not address this issue and we'd really like to get this straightened out. I am willing to take a lot of time to do this, but do it right.
Can someone please help me with this?
Thank you in advance,
~ J -
Set up existing expresses with new extreme base station
We just replaced our old extreme base station with the new fast one. It works good so far except that now my two existing airport expresses- one I use for airtunes and the other to relay the wireless signal to a far corner of the house- don't work. What do I need to do to set them up with the new station? I tried a reset but it didn't help.
Either connect them with ethernet to configure the Expresses or find them wirelessly(you can use Airport Utility or the older Airport Admin Utility). The bottom line is to get the Express selected in Airport ie the icon on the top file menu then use the Utility. If your nearwork is not visible to select then use the preferred drop down menu found in Network pane of system preferences. You may need to type in the network name or use the + button.
-
Airport Express Can't See Base Station
I have an airport extreme base station that has two computers normally connected to my network wirelessly (iMac G4 and Powerbook G4) which have worked fine for months. After completing an apple security update this evening on both computers the Powerbook G4 did not automatically connect to the network upon restart as it normally does. The iMac G4 started up fine and is how I am posting this note. The powerbook on the toolbar shows the network I want to join but when I select it (and and see the check mark next to it) I still cannot access the internet. When I run the Airport admin utility it cannot see any base stations (despite the iMac sitting 1 foot away and working perfectly). When I manually give it the IP address and password it says "unable to read the configuation of the selected base station." When I try the Airport Setup Assistant it also lists my network as one that I can choose but when I click on the "continue" button it says "unable to establish a network connection" and that my computer could not connect to the internet. Help!!! I have tried every angle I can thing of to get the Powerbook to connect like it did a few hours ago.
I have just discovered the same problem. After downloading the latest security update my Powerbook G4 [10.3.9] can not "see" any base station or express and/or connect to my network. The G5 running 10.4.5 works fine and sees all. Everything had been working just fine before the update then... Have tried all the work arounds I can think of and wasted a great deal of time. Any answers out there?
G5Tower / G4Powerbook Mac OS X (10.4.5) G4Powerbook OS 10.3.9 -
OS X 10.2 w/ Airport Card Connecting to Extreme Base Station
Hey--
I'm on a G3 Powerbook (w/Firewire) running OS X 10.2 and I installed an Airport Card and I'm trying to connect to a new Extreme Base Station-- and PB can't see the Base station in the Airport Utility. Although my PB does receive the signal from the base station.
I've tried:
- Resetting the base station
- Loaded Airport 2.1.1 software update
- a million configurations
- yelling at it...
The airport card does work, because it connected on another wireless system.
Can someone help me with the definative fix?
MikeWelcome to the discussion area, stacidesign!
First, you have verified that the PC can connect to another wireless network, correct? If it can, then that tells you that the wireless card is functioning correctly.
You'll have better luck connecting to a newer wireless router if you are able to update the PC to Windows XP SP3. Have you tried this?
It's also possible that the wireless card in the PC can connect to a 802.11 "b" or "g" network, but not to an "n" network. To check that out, you need to use AirPort Utility - Manual Setup to make a change in the radio mode of the AirPort Extreme.
Click the Wireless tab below the row of icons
Hold down the option key on your Mac while you click on the Radio Mode selection box
Write down your current settings so you can return to them later if needed
Select this Radio Mode...+802.11n only (5 GHz) -- 802.11 b/g+
Keep the Wireless Security set to "None" temporarily
Update to save changes and allow 30-40 seconds for the AirPort Extreme to restart
Restart the PC
See if the PC can connect now
Please post back on your results
Message was edited by: Bob Timmons -
Airport Express used to be base station, now want to use only for AirTunes
After I moved to to different neighborhood, ATT informed me I had to upgrade from my former "elite" DSL to UVerse, which has wireless router. Want to use my Airport Express for AirTunes in a different part of the house, but I have repeatedly screwed up my network trying to reconfigure AE. Anybody have experience with this? Help!!
Thanks, Bob, for your quick response. Bit of a long story - I am talking about my place in the city where I live to work, about 6 hours away from where I am now; I am heading back there shortly. But, here's something like the whole story (as much as I can recall without the scratchy notes I have down there):
When I moved from apartment to house I bought 2 weeks ago, everything seemed fine - Uverse was installed and I used the AE to run powered speakers while I moved in. But then I noticed that my iPhone, and my friends' smart phones, would not connect to my home network. It was after I spoke to ATT support the first time, and they had me change security from WAN to WEP that my Airport problems started. My messing around trying to figure it out crashed my network at least once and caused another hour-long session with very helpful ATT support person re-setting my network.
So, Uverse security is WEP. My newish MacBook Pro runs 10.7.4. I was very frustrated by Airport Utility 6.1 not showing the AE, or only doing so if I made it my "base". I see from my older iMac here at home that I possibly need an older Airport Utility to detect the AE. But beyond that, I am gun-shy to try anything else with the AE without some advice. -
Airport Express loses connection to base station
Airport Express second gen loses connection to base station, has to be reset.
Roger that. Late 2013 MBP 2.5 i5 4mb ram, 10.9.1 Mavericks, formatted and hand loaded after questionable upgrade load. Fast, flawless, no issues.
Airport Express configured to wirelessly extend existing network for the express purpose of supplying an analog
input to a stereo amplifier via airplay. No other devices are connected to the AE.
The WAP is a Century Link Actiontec C1000A VDSL2 physically located 6 feet from the AE with no obstructions.
There are no existing proximal fortuitous distortion or RF interference sources. Other 802.X networks near are
on non-conflicting channels. The WAP is less than six months old and has no issues.
The WAP is configured for MAC filtering with the SSID turned off. In the allow list are two iphones, a printer, two more MBPs and the Airport Express. One of the iphones is loaded with the Remote Ap which functions
flawlessly when the AE is connected.
The AE connects properly in the Extend Existing Network mode and performs as advertised as long as Air Play
and/or itunes is active.
Some time after music has ended, the MBP has gone to sleep, or been shut down ... the Airport Express loses its connection to the wireless network, with its amber light flashing.
Performing a reset and reconnecting is necesssary, and all works as advertised after. Subsequently,
sleep, inactivity, or shutdown will cause loss of connection again.
I am aware the AE can be connected with CAT6, but that is unnaceptable. If I had wanted to use wire I
would have plugged the MBP into the amplifier and saved $100.
My speculation is some sort of TCPIP flub in the design ... as in the AE does not natively transmit keep-alive
packets when it stops getting data from the Air Play computer. It would be easy to decide whether to fix
the problem or return an inadequately designed product ... if there were any information about it. No schematics, no operation description however leaves me only to say thank you for your time and hope
you have the solution. -
Airport express-can't find base station
I've tried everything I can think of-I've reset my ae several times and still utility is not finding the base station-help!
I am having the exact same thing. I saw it once, and made some setting changes, now it's gone. I bought the bloody thing because although my modem has Upnp the mac claimed it wasn't working, so I though ok (back to my mac - only been trying to get it running for about a year: zero success) I'll get a base station, that supports NAT for BTMM, but the one time I did access the base station its error was double NAT, so the mac and the base station seem to be reporting two different things regarding the modem. It is driving me ballistic!!!!
-
I'm trying to extend the range of an Airport Extreme 802.11g by adding an Airport Express 802.11n. I set the Express up to join the existing network, but it does not make any difference in the range of the network. What's wrong?
Let me see if I can help you with the basic WDS configuration steps:
Note: To help facilitate the setup, temporarily connect the AXn directly to the AEBS LAN port using an Ethernet cable. Once the setup is complete, you can move the AXn to the desired location. For all configuration steps you will be using the AirPort Utility. Before starting, be sure to jot down the AppleIDs for both base stations.
802.11g AirPort Extreme Base Station (AEBS) Configuration
AirPort Utility > Select the AEBS > Manual Setup > Wireless tab
Wireless Mode: Participate in a WDS network
Manual Setup > WDS tab
WDS Mode: WDS main
Allow wireless clients (checked)
WDS Remotes: <enter the AppleID for the AXn here>
Click on Update and allow the base station to restart.
802.11n AirPort Express Base Station (AXn) Configuration
AirPort Utility > Select the AXn > Manual Setup > Wireless tab
Wireless Mode: Participate in a WDS network (Note: You may have to hold down the Option (Mac) or Control (PC) key to see this option in the list.)
Manual Setup > WDS tab
WDS Mode: WDS remote
Allow wireless clients (checked)
WDS Main: <enter the AppleID for the AEBS here>
Click on Update and allow the base station to restart. -
How to extend the range of my Airport Extreme network by adding an Airport Express
How to extend the range of my Airport Extreme network by adding an Airport Express?
You have to make sure that the AirPort Express is in Factory Default Settings. If it is straight out of the box, it is ready to be configured.
The instructions that I will provide are for using AirPort Utility 6.0, which you have.
Locate the Express in the same room as the AirPort Extreme for the configuration. Power it up and allow a full minute for the Express to display a blinking amber light.
Make sure that the wireless is turned on your Mac
Open AirPort Utility 6.0 and look at the small rectangle in the upper left hand corner of the display. It should now read something like "Other AirPort Base Stations (1)"
Click on the rectangle, and then click on the AirPort Express xxxxxx listing
AirPort Utility will take a minute or two to analyze the settings on your network and then suggest that the Express be configured to "Extend" your wireless network.
Edit the Base Station name to your liking, then click Next in the lower right hand corner
Allow a full minute or two let AirPort Utility do its work
When you see Setup Complete, click Done at the lower right of the window.
Now move the AirPort Express to a location that is approximately half way between the AirPort Extreme and the area that needs more wireless coverage.
You should be in business. -
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.
-
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. -
Can I buy an Airport Express plug-in wifi signal booster to connect to a Cisco wireless router, or do I have to buy an Airport Extreme base station to make the Airport Express plug-in work?
You would need either an AirPort Extreme or an AirPort Express connected to the Cisco router, with a permanent Ethernet cable connection.
Configure the Extreme or Express that is connected to the Cisco router to "create a wireless network".
Then, you could add an AirPort Express to "extend a wireless network" to provide more wireless coverage for the network that the Extreme or Express would be creating.
Remember that the Express can only "extend" the quality of signal that it receives, so it must be located where it can receive a strong signal from the "main" AirPort.
If you don't need the Cisco wireless signal, you could turn it off.....or use that network for guests or something similar.
The bottom line here......you always need two Apple routers if you want to extend the network wirelessly.
Maybe you are looking for
-
Same container, different ear files, remote lookup failing!
I'm having severe problems with my ears! I used to have all my EJBs in one ear file and everything worked hunky dory. Now I have separated out various components into their own ear files as they may be deployed into a separate box and also this eases
-
Inactive items without purchase as well Sales particular period
Dear Expert, I want list of Item master which doesnu2019t have transaction in Sales and Purchase as from the following documents Purchase Order GRPO A/P Invoice A/P Down payment Sales Order Delivery A/R Invoice A/R Down payment For a particular perio
-
RSCRM_BAPI removing filters of View for File Extract execution.
Hi folks, I m working on BI 7.0. I have a view , which has poor performance, as query based on DSO , I want to execute the view in background with a variant. I created an extract using a variant In RSCRM_BAPI. But in output i can see only those value
-
Is there an Adobe server issue right now? We can't use an active Adobe ID to authorize a tablet.
Can't authorize an Asus tablet with an Adobe ID in the Overdrive app.
-
I have ACS 3.2 and a bunch of TACACS configured Cisco devices. I want to give a limited set of access to techs the environment to modify VLAN assignments of ports. So they would need to be able to access privileged mode, but only execute things like: