Windoze Ad-hoc networks killing Airport Extreme Base Station

After having a horrible experience with an Orinoco base station sometime ago at his coffee shop, a client of mine asked me to install a new Wi-Fi access point to replace it. Since I'd never had a problem with my graphite Airport Base Station, I selected recommended that he try the Airport Extreme. Everything was been fine for over a year and half, with only the occasional interference problem, and even that easily fixed by a restart on the base station. Lately that has changed. We're in Baton Rouge, and since Hurricane Katrina, our population in our city has doubled (that's not an exaggeration), and the number of customers using the network in his coffee shop has increased as well - although it's still well below the maximum. The problem is that there are is large number of students from Loyola, UNO and Tulane who are now attending LSU, right across the street. And a significant fraction of those have ad-hoc networks set up on their Windoze notebooks, apparently unintentionally. When they come into the coffee shop their ad-hoc networks seems to cause the Airport Extreme to die, and not recover, until it is reset. This happens many times per day, sometimes more than once in an hour.
It had been configured to automatically select a channel, but I re-configured to use a specific channel (and have been experimenting with the particular channel). It seems to reduce the problem for a time, but then we'll have the problem back in force within a few days.
I have verified (using iStumbler) that there are no other "managed" networks near-by, and I have noticed that the problem ALWAYS happens when there is are ad-hoc networks, and after politely asking customers if I can check their settings, (it's scary how many people will let you poke around on their computer, if you seem like you know what you're doing) I've also seen compelling evidence that it is Windoze users, not Mac users, who tend to cause the problem. Incidentally at this particular coffee shop the Windoze:Mac ration is something like 60:40. What can I say, it attracts discerning customers. Since some of them have "lsuwireless" set up as an ad-hoc network (and as I said, LSU is across the street), my guess is that somehow these get set up, not on purpose, but accidentally, while trying to connect to the university's wireless network. Apparently the process is not so straight forward for Windoze users as for Mac users.
I have upgraded the Airport Base Station software to the latest available as of last week. Though I don't have that version number available at the moment.
So I have several questions:
1) Is this really the same radio interference problem that I've read about elsewhere on this discussion board?
2) Would an external antenna on the base station help? How about a powered one?
3) Aside from "Use Interference Robustness" and trying different channels, is there some configuration setting that I might be missing that could enhance the base station's reliability?
4) Does anyone have a suggestion for a permanent fix - preferably without switching to a different access point, although at this point, that's a viable alternative. After a year and a half of stable operation though, we're loathe to switch again unless it can't be avoided, because the Orinoco access point we used before had behaved exactly like this, but even worse, and without necessarily having ad-hoc networks being present to cause the problem.
5) Failing any other good solution, can anyone suggest a way to determine which computers are causing the problem without having to interrupt each customer to poke around on his computer?

I have an Intel based iMac and a MacBook Pro. Both
are (well until tonight) connected to the internet
wirelessly through the Airport Extreme Base station.
I've had no trouble up until now. Tonight for some
odd reason the MacBook Pro Airport card fails to
detect the Airport Extreme Base Station. It detects
OTHER wireless networks around the building, just
not the one it's supposed to connect to. Opening up
Airport Utility doesn't even show the Airport
Extreme Base Station being present. I know the Base
Station is not at fault - it works fine with the
iMac. Tried setting the Sharing mode on but that
didn't help either (not that I changed any of the
settings to begin with).
Can anyone help? I'm really at a loss here.
Any one? Any suggestions?

Similar Messages

  • Networking with AirPort Extreme Base Station

    I am connected to the Internet with an SBC dsl modem, which I have had for a couple of years with few problems. However, I have been having issues networking my Mac G5, 1.8 Mhz machine since I purchased it some time ago.
    In the beginning (before the Mac or -- BM as I like to call it) I was using a D-Link DI-614+ router and running a desktop PC and a laptop PC wirelessly with success. Then I bought my Mac (which I dearly love) and introduced it into my wireless network. At first it seemed to work OK. Gradually and occassionally it would lock up while trying to access an Internet site. Often the problem was resolved by rebooting the DSL modem, the D-Link router and all the computers. This would give me up to several days with no problems, but then things would rapidly deteriorate and I would have connection problems again.
    I thought that if I bought an Airport Extreme base station, that would solve the problems but again, at first things were fine, then rapidly went downhill. I have worked exensively with SBC dsl techs and we have determined that the problem is not with the SBC network or with their dsl modem.
    As it stands now I only get a maximum of a couple of hours of time before the slowing down of the network begins. Some of the error messages I get seem to indicate that there is a problem with the distribution of IP addresses. TCP/IP is set to use DHCP, and I connect by setting PPPoE to my SBC connections settings. "Connect using PPPoE" is unchecked. Location is currently "Automatic" although I have used the connection assistant a number of times in an attempt to get the system up and running.
    I have the same problems in interconnecting the Mac with the two PCs that are on my system. In fact this is even more erratic than connecting to the Internet.
    I have spent many hours with my limited knowledge of these things trying to resolve these issues but have had no success. I have scoured .Mac and other Internet sources and cannot find any specific solution to this problem. I am at a real loss as to where to go next. I am hoping someone here can help or point me in a direction where I might find a solution.
    Thanks,
    Don
    Power Mac G5   Mac OS X (10.4.7)  

    Thank you very much for your response. Yes, the Mac is set to use PPPoE and the SBC information is stored there.
    Just to clean things up, I removed the PPPoE configuration on the Mac and left it unchecked.
    Here is other information about how the system is set up.
    Note: + means item is checked, - means item is unchecked
    Apple Base Station V5.7
    WAN Ethernet Port: Automatic (Default)
    +Enable SNMP Access
    +Enable Remote Configuration
    -Enable Default Host at
    +Enable Remote Printer Access
    -Enable NAT Port Mapping Protocol
    Internet:
    Connect Using: PPP over Ethernet (PPPoE)
    +always stay connected
    Network:
    +Distribute IP addresses
    Airport client computers:
    +Share a single IP address (using DHCP and NAT)
    ((Use 10.0.1.1 addressing))
    Power Mac G5   Mac OS X (10.4.7)  

  • Can't create a working Wireless Network using Airport Extreme Base Station

    I don't know what I'm doing wrong...
    I've got the cable from the modem going to the base station. I follow ALL on screen instructions. I select "Using DHCP" because when I plug the ethernet cable into my MBP it automatically does everything for me, and has that as its setting as well.
    I get to the stage where it asks whether or not I'd like it to share an IP or go into bridge mode, I'm not sure what either of these two mean...I've tried both and both result in no wireless internet.
    On several occasions I get to the end, and after I do the "final" update is comes back with one problem - internet connection, saying the router doesn't have a valid IP.
    I'm totally lost on what to do here...
    If you need more information just ask...please...

    The below procedure is described in your AirPort setup manual, but it can be a little confusing. Here is my step-by-step procedure for an AEB setup for the system you describe:
    A. Setup the 'Main' Base Station:
    1. Do a factory reset of your AEB (main), then turnoff the DSL Modem and the AEB (main).
    2. Check ethernet cable connections:
    - DSL Modem > AEB (main) WAN port;
    - AEB (main) > Mac computer running OS X 10.5.x.
    3. Power-on DSL Modem and wait for it to initialise.
    4. Power-on the AEB (main) and start your Mac computer.
    5. Open AirPort Utility and select the AEB (main) in the LH pane. Click 'Continue' and give the AEB (main) a name and an admin password (twice). Click 'Continue'.
    6. Select 'I don't have a wireless network and I want to create one', click Continue.
    7. Give your network a name, select WPA/WPA2 Personal and insert the wireless network password (twice) - use 13 alpha/numeric characters for password. Tick 'Remember this password in my keychain'. Click 'Continue'.
    8. Select 'I connect to the Internet with a DSL or cable modem using DHCP. Click 'Continue'.
    9. Click 'Update' and wait for the AEB (main) to restart.
    10. Disconnect the ethernet cable between your Mac and the AEB (main).
    B. Setup Client computer
    1. Open System Preferences/Network/AirPort.
    2. Against 'Network Name:' select your network (the name you gave it at A7).
    3. Click 'Advanced' and select TCP/IP. Against 'Configure IPv4:' select 'Using DHCP', then click 'OK'.
    4. Click 'Apply' and exit System Preferences.

  • Airport extreme base station no longer recognizes password

    Away from house for a week. Came back and none of our iPhones, iPads can connect to wifi network. Airport Extreme base station will no recognize my network password to check settings. Airport Epress will not join network either.

    Hi danny_A1A!
    I have a couple of articles here that should be able to help you troubleshoot this issue. The first is a quick assist article pertaining to Wi-Fi issues and can be found here:
    Wi-Fi Quick Assist
    http://support.apple.com/kb/ht1145
    We also have another article on troubleshooting Wi-Fi connectivity, and it can be found here:
    Wi-Fi: How to troubleshoot Wi-Fi connectivity
    http://support.apple.com/kb/HT4628
    Take care, and thanks for visiting the Apple Support Communities.
    -Braden

  • 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.

  • How do I set up a wireless network with an AirPort Extreme base station and two airport extreme but between apple devices either by ethernet

    How do I set up a wireless network with an AirPort Extreme base station and two airport extreme but between apple devices either by ethernet

    This Apple support document provides good general information on configuring different types of neworks using multiple AirPort routers.
    http://support.apple.com/kb/HT4145
    In particular, you would want to focus on the information regarding a "Roaming Network"

  • I have an airport extreme base station and have no clue how to set up a private wireless network instead ton open one i have now.

    I have an airport extreme base station and have no clue how to change to a pawword type network from the network i have now that is free to the neighbor hood.

    Which version of the AirPort Utility are you using?

  • HT4259 How do I set up an Airport Extreme Base Station (v. 7.6.1) to allow wireless network extension?

    I have an Airport Extreme Base station (purchased in 2009) and an Airport Express base station (purchased in 2011 - the model that plugs directly into the electrical outlet) (both version 7.6.1 according to the Airport Utility info).  I want to use the Airport Express to extend my wireless network.  Using Airport utility setup I have a software option on the Airport Express to set it up to extend the network but I do not have an option on the Airport Extreme wireless setup screen that I can check to allow my wireless network to be extended. 
    All of the documentation I can find on Apple Support states that I should have an option I can check to allow the wireless network to be extended while in the wireles setup section for the Airport Extreme in Airport Utility; but, that check option isn't there.  Is this a case of my Airport Extreme base station being too old to offer that option?  Incidentally, when I try to select the extend wireless network option on the Airport Express from the Airport Utility wireless setup menu I get an error message (no details - just an error message).  The same Airport Express sets up fine if I select join a network (not what I want to do).  Am I just dealing with outdated equipment or does anyone have a suggestion?  Thanks.

    Close AirPort Utility if it is open.
    Temporarily, move the Express to the same general area as your AirPort Extreme and power it up and wait a minute.
    Hold in the reset button on the Express for 9-10 seconds and then release. Give the Express a full minute to restart to a slow, blinking amber light.
    Click the AirPort icon at the top of the Mac's screen and wait a few seconds for a listing of New AirPort Base Station to appear
    Click on AirPort Express just below that and AirPort Utility will automatically open
    Wait a minute while AirPort Utility analyzes the network and announces that the Express will be configured to "Extend" the AirPort Extreme network.
    Enter a device name for the AirPort Express and click Next
    Wait another minute to allow the configuration to occur.
    When you see the Setup Complete message, click Done.
    Now move the Express to a location that is approximately half the distance from the AirPort Extreme and the general area that needs more wireless coverage
    Power up the Express and you are all set.  Trash those old instructions.

  • How do I configure an Airport Extreme base station to receive and distribute a wi-fi network from a broadband wireless router?

    I have recenly upgraded my broadband service and now have a wireless router. My old network configuration was a router connected by ethernet cable to an Airport Extreme base station which then broadcast my wireless network (I also had an Airport Express base staion set up as a wi-fi booster elswhere in the house).
    I now have two networks (my original network and the new network from the wireless router) and wish to amalgamate these into one.
    Ideally I wish to use the Airport Extreme base station as the "remote" booster (I have purchased Powerline adapters for this purpose) but don't know how to configure the Airport Extreme base station in order to to this.
    Can you advise on the best set up for this please?
    My Mac is running OS X 10.8.2 and the Aiport untility is version 6.1.
    Thanks in anticipation.

    The AirPort Extreme should be configured to "create a wireless network" with the same WiFi network name, security type (usually WPA2 Personal) and password as your existing router. It should be configured as connection type Ethernet and be in bridge mode.

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

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

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

  • Multipmultiple Airport Extreme Base Stations: WDS Or "Extend Wireless Network" To Have Wired -- Wireless Bridge?

    Hello there!
    I've been looking for this info, but have as yet been unable to find it. Here's my scenario:
    I have two Airport Extreme Base Stations (both are dual band) and 3 airport expresses. The main internet connection in my house is in one room, where I have an AEBS as the main wireless router. In another room, I have a bunch of ethernet-only devices. I'd like to use the 2nd AEBS in this room, plug the ethernet devices into it and have the 2nd AEBS act as a wired <--> wireless bridge (connected to the same wireless network as the 1st AEBS). I've attempted this via "extend a wireless network," but the ethernet devices don't get past the AEBS they're plugged into. Should I instead be implementing WDS?
    I mention the airport expresses as I'd like to have airtunes & wireless signal in other areas, but would like to keep the set-up as simple as possible (i.e., not config the AXes for WDS unless it's required).
    Thanks in advance for any help!

    Unlike the 802.11n AirPort Express Base Station (AXn), the 802.11n AirPort Extreme Base Station (AEBSn) cannot be configured as a wireless Ethernet bridge.
    However, there are at least two ways to configure it to provide wired clients access:
    Connect the second AEBSn back to the first by Ethernet; reconfigure the second AEBSn as a bridge and disable its wireless radios, or
    Reconfigure both AEBSns into an extended wireless network. For 802.11n AirPorts, this would be called a dynamic WDS. The AEBSn, connected to the Internet would be the "main" base station and it would only require that you enable the "Allow this network to be extended" option in the AirPort Utility. The extending AEBSn would need to be configured with the option, Wireless Mode = Extend a wireless network, enabled.
    In both configurations, the second AEBSn's Ethernet ports would be enabled for wired clients.

  • Airport utility no longer recognizes my Airport Extreme Base Station, which had been set up to extend a wifi network

    Hi.  In November I set up my airport extreme base station (5th generation I believe) to wirelessly extend the wifi network we use at home to see if it would increase download speeds.  Before doing that, I did a factory reset of my airport extreme, and the owner of the airport extreme to which the ethernet cable is attached made changes to his network to allow it to be extended.  I folllowed all the directions from the apple support pages, and finally got it to work.  I could even access a portable hard drive which I attached to the airport extreme base station being used as the extension.  Then a week or so ago I noticed that my laptop would no longer connect to my base station.  I did not have time to look into it until this week.  Airport utility, either on my Mac or iphone no longer recognizes my base station.  My mac is running OS X 10.10.1  and my iPhone is running iOS 8.1.2  I have tried both hard, soft and factory resets of my base station to no avail.  The only thing that has changed after doing that, is that when I do a soft reset of my base station, a neighbors airport express appears when it never did before.  I can't actually connect to it, but it does try.  Then after approximately 5 minutes, it disappears from my list.
    Today I went and pulled out my OLD AIRPORT EXTREME base station... you know, the one that looks like a space ship and is running wifi 802.1 b/c?  airport utility DOES locate and display that, but airport utility returns a message stating that it cannot be set up by this software.  I am attaching an image of that.
    Thank you,
    John
      Does this have anything to do with the fact that 'Back to My Mac' is probably enabled?

    I think the initial problem is that your iPhone was connected to an open network that wasn't yours.
    Go to Settings > WiFi and "Forget" the network created by that AirPort Extreme, it's older than dirt. Forget your neighbor's network also.
    Perform the equivalent actions with your Mac: System Preferences > Network > Wi-Fi > Advanced... Delete every network that appears, including your own.
    Then, connect to your own network on all your devices, after which you ought to be able to use any of them and configure your Extreme without any difficulty. You may need to start over with a "hard reset" on both the main AirPort Extreme and the one extending its network.
    Does this have anything to do with the fact that 'Back to My Mac' is probably enabled?
    Not exactly, but using iCloud Keychain will populate all your devices with the names of preferred networks that any of them connect to, no matter where they are. I don't know why Apple considers that a beneficial feature.

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

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

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

  • How to get this Airport Extreme base station to produce a wireless network?

    I had this Airport Extreme base station working fine at the house that I moved from a couple of days ago.
    After my house move, however, it seems that the AE base station isn't producing a wireless network. My wireless laptop isn't detecting a wireless network. Also, the left hand side light on the AE base station is not lit.
    The AE base station was softly cushioned during house the move.
    Regarding configuration:
    My non-wireless iMac (running 10.3.9) connects to the AE base station via an ethernet cable.
    Before my house-move, I regularly connected wirelessly via the AE base station from a couple of wireless-equipped laptop computers.
    I was using AE software version 5.6. (In desperation, I have just updated to version 5.7 - but that hasn't improved or changed situation.)
    At the new house, I found that I had to reset the AE base station back to factory settings before I could successfully connect to the internet through the AE base station from the (non-wireless) iMac.
    Since resetting the AE base station at the new house, I can also print via a USB printer that's plugged into the AE base station.
    I just cannot pick up any sign of a wireless network from the AE base station.
    G4 Powerbook   Mac OS X (10.3.9)   Problem started while I had Airport Extreme software v5.6. No improvement/change after v5.7 update.

    Sorry for my delay in closing this issue.
    I got the wireless network running again - though I'm not sure which of a "litany" of separate actions (which I gleaned from dialogs in several similar postings for similar issues to mine) was the solution. I suspect it was one of the following two actions, which have stuck in memory:
    1) I relocated a nearby cordless phone cradle/charger/base-station from alongside the Airport Extreme base station to about seven feet (two meters) away. However, the cordless phone is about eight years old, and I believe its radio frequency is far out of the range that I have read (in similar postings) can interfere with the Airport Extreme base station.
    2) I re-set the Airport Extreme base station, (a) by depressing the tiny reset button at the rear of the base station for more than 5 seconds (until the led started blinking), (b) from Utilities/AirPort Admin Utility/Configure/Restart. However, I had reset the Airport Extreme base station those ways previously without that restoring the wireless network. Also, I didn't record the sequence of the multiple resets and the configurations at the times of the resets.

  • Power Mac G3 Pismo with Airport wireless card in Mac OS X 10.4 won't connect to wireless network  with  newest Airport Extreme Base Station set at WPA Personal/WPA 2 Personal encryption.

    My Power Book G3 Pismo with an Airport wireless card  running Mac OS X 10.4.11 will not connect to my new Airport
    Extreme Base Station using WPA Personal/WPA 2 Person encryption.  The Airport firmware is version 9.52.  From
    posts I've read online at different places indicates the Airport card should support the WPA encryption.  Perhaps the problem
    is the Base Station is using a combination setting and the fault is in the base station?
    Thanks for any suggestions

    Perhaps an inexpensive usb wireless adapter would work as well?
    This is probably the simplest way to get the G3 connected to the wireless network.
    I'll have to read up on getting an express and using it as a wireless bridge as I am unfamiliar with the concept.
    The new AirPort Extreme is broadcasting a wireless signal.
    A new AirPort Express could be located close to the G3. The Express will pick up the wireless signal from the AirPort Extreme, then provide an Ethernet connection to the G3 though a short Ethernet cable. 
    This can work very well......IF.....you keep the G3 at a fixed location, since it will always be connected to the AriPort Express using an Ethernet cable.
    I do have an old Linksys Wireless G router.  I wonder if that would work?
    In theory, yes. But it would have to use much older WEP "security", which is easily cracked in minutes using free tools available on the Internet. So, anyone who really wanted to get on the network could do so. It's an option, but not a very good one.

Maybe you are looking for

  • I have no audio what so ever i have seen in one of the tables where it was deleted how can you fix this i tried everything i know

    == Issue == I have another kind of problem with Firefox == Description == i have been trying to get the audio to play for 3 days now i did see where it had been deleted this is a used comp i haven't had it long can you fix this i'm at my wits end ==

  • Oracle 8.0.5 on SUSE-Beta 6.0

    just install and run it - no more patches etc required for snmpd comes "no rule to make....." its just great and fast F.Gassauer null

  • External Monitor with Bootcamp

    I am running Bootcamp on my MBP (Leopard 10.5.2). Is it possible to run a second monitor in the Windows partition? I am running XP Pro, SP2. I tried plugging in a monitor, but it didn't seem to recognize that it was there. Am I doing something wrong,

  • XML SQL Utility - settagcase - all tags are upper or lower

    I am using the XML SQL Utility (XSU) for PL/SQL to generate a xml document from some tables and objects. Is it possible to have the xml elements start and end tags appear in the case of the objects I have defined (i.e. CamelCase)? I can either have t

  • BEx Query Execution problem

    Hi, I got a problem when I click Execute button in Query Designer to run a query. It popup a IE windows with a URL like below http:///irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.pct!2fplatform_add_ons!2fcom.sap.ip.bi!2fiViews!2fcom.