Airport extreme base station detecting someone elses network but not mine.

Sorry if this subject has already been discussed but I couldn't see it anywhere.
I have an airport extreme base station set up and it works fine but this morning i noticed that I had very little signal which has never happened before so upon further investigation I noticed that my computer was hooked up to a Netgear network amd not my own usual airport "home" network.
I got my own network back again and my signal is now full strength. The worrying thing is that my computer couldn't seem to find my airport "home" network when I searched for it. I had to start again from scratch and reset it.
Is there a way I can tell my computer to use only my airport network and no other? Someone obviously has an open network nearby.
Message was edited by: lispiers

Try the steps indicated in Mac OS X 10.4 Help: Choosing preferred AirPort networks.

Similar Messages

  • Can I use two airport extreme base station on the same network

    Can I use two airport extreme base station on the same network

    Here is my network setup:
    D-Link DCM-202 simple cable modem (DOCSIS 2.0 compliant)
    attached via ethernet to
    5th generation AirPort Extreme Base Station - Main (Bought last week)
    attached via ethernet to
    4th generation AirPort Extreme Base Station - Remote (Bought about 11 months ago)
    The main AEBS is set to:
    AirPort Section:
    Base Station Tab -> Allow setup over WAN is CHECKED
    Wireless Tab -> Wireless Mode: Creat a Wireless Network, Radio Mode: 802.11a/n - 802.11b/g, Radio Channel Selection: Automatic, Wireless Security: WPA2 Personal
    Internet Section:
    Internet Connection Tab -> Connect Using: Ethernet, Ethernet WAN Port: Automatic (Default), Connection Sharing: Share a public IP address
    TCP/IP Tab -> Configure IPv4: Using DHCP
    DHCP Tab -> DHCP Beginning Address: 10.0.1.2, DHCP Ending Address: 10.0.1.200, DHCP Lease: 24 hrs
    NAT Tab -> The box following 10.0.1. is left blank, Enable NAT Port Mapping Protocol box is CHECKED.
    The remote AEBS is set to:
    AirPort Section:
    Base Station Tab -> Allow setup over WAN is CHECKED
    Wireless Tab -> Wireless Mode: Creat a Wireless Network, Radio Mode: 802.11a/n - 802.11b/g, Radio Channel Selection: Automatic, Wireless Security: WPA2 Personal
    Internet Section:
    Internet Connection Tab -> Connect Using: Ethernet, Ethernet WAN Port: Automatic (Default), Connection Sharing: Off (Bridge Mode)
    TCP/IP Tab -> Configure IPv4: Using DHCP, IP Address: 10.0.1.2, Subnet Mask: 255.255.255.0, Router Address: 10.0.1.1, DNS Server(s): 10.0.1.1  (Everything else under this tab is blank)
    Hope this helps with info needed.

  • Airport Extreme Base Station - Need to extend network for extra distance

    The literature on this topic is sparse. I have an Airport Extreme base station. I will like to "extend the signal" so that it is stronger in part of house. I would like to buy a product that will do this. Questions:
    I think this is called "bridging".
    1. Can I do this with the Airport Express as a 2nd unit??
    2. Does the Airport Extreme work with other WDS 2nd units like Netgear?
    3. Is there a darned manual to tell you how to configure the settings on BOTH stations?
    Thanks.

    How new is your Extreme? I ask because if your Extreme supports 802.11n, the setup process will be greatly simplified.

  • Airport Extreme Base Station Dual Band MC340LL/A will not create a Wi-Fi network.

    It will allow access to the internet only through the ethernet but not Wi-Fi.  I downloaded the airport utility to set up the device and the yellow light keeps blinking.  I use an ethernet DSL modem.  This is the first Apple product i have bought and i got it off of Ebay as refurbished.  Hopefully i don't have to return it because the router is the problem   I don't know much else. Thx

    FYI, i have reset the router many times with no new results.

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

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

  • Printing wirelessly to MacBook Pro with Airport Extreme Base Station

    I have an Airport Extreme Base Station that I used to use wirelessly until I got Verizon Fios. The Fios technicians said the base station couldn't be used and so it's been sitting unused for a few months. However, I really, really miss printing wirelessly, and was wondering if it was possible to use the Airport Extreme Base Station ONLY to print wirelessly, and not connect it any way to my internet (I don't want to mess with any of the fios stuff at all).
    If it's not possible, is there any other way to print wirelessly without purchasing another product or special printer. I have a HP c4480 printer.
    Thanks!

    If your printer has a USB cable the easy way to go about this in my opinion is to plug that USB cable into your Extreme base station. I have the Extreme ABS that looks like a flying saucer. I plug the usb cable into the port that has the symbol that doe NOT look like this <--> rather it looks like a Saguaro cactus.
    My computer then sends print documents to the Extreme via WiFi and then Extreme sends them to the printer via the USB cable.
    If your Airport status is not showing in the Mac's menubar go to system Prefs/Network/Airport and check a little box so it will show up in the menu bar.
    Now if your Extreme is plugged in the wall and powered up your Mac should be able to find it. Click on that menubar item for Airport and scroll down and select your Airport Extreme. I don't know for sure what its name will be. It should still be the same as it used to be when you used it last.
    Now try printing a simple document. In the print dialog window you should be able to select what printer you want to use. If your new Extreme printer is listed select it. You may need to click on Print & Fax and figure out how to select it from there, and choose it to be the new default printer.
    I think this info will do the job. Whenever you want to print you have to go to the Airport icon in the menubar and change your airport connection from your Verizon stuff to your Extreme. Then of course you have to change back when you are done. That is why it would be great to toss the Verizon WiFi radio out the window and just plug your Verizon modem into your Extreme WiFi radio transceiver (router). But I understand you cannot deal with that at this time.
    If this does not do the job, if I have missed something, I will bet you 5 bucks that you can still figure it out if you just look at any error messages and/or look at the Print&Fax prefs and the Print dialog windows etc. and see what I may have missed. Maybe you have to go to SystemPrefs/Sharing and allow your printer to be shared. I don't think so. The way I figure any of this stuff out is to just look at stuff and think and try things and see what happens.
    Your Verizon setup should be something like this.... a cable comes into your house and goes to a 'modem'. From there and ethernet cable (CAT-5 cable) goes from that modem to your Verizon router (WiFi radio transceiver).
    As for getting rid of the Verizon router, when you are ready to give it a go, simply unplug the ethernet cable (it has a plug on the end that looks like the kind of plug that telephones use to plug into the wall, except it is a bit wider, but still has that same kind of snap-lock tab) that comes from the Verizon modem (the modem has the heavy round cable and probably many blinking lights) and plug it into the Extreme. Mine has an icon on the Extreme that is many dots in a circular pattern.
    At this point you may have to unplug the Verizon modem form the wall AC power and the Extreme also. Then plug them back in, wait a minute, go to your Airport icon on your Mac menubar, Select Extreme and start surfing the web.
    It really is that simple with a Mac. Maybe Verizon has found a way to make things difficult but my guess is no. Any password should be taken care of in your Airport Setup Utility program. It should be the same password(s) as you used before when you used your Extreme.

  • Lion 10.8 e Airport Extreme Base Station

    Installata Lion versione 10.8 e non riesco più a configurare il mio Airport Extreme Base Station. La versione istallata di Utility Aiport 6.1 non funziona con questa base e mi dice di istallare la versione 5.6. La 5.6 però non è compatibile con 10.8 infatti non si installa. Che fare?

    FWIW, I currently have Ubuntu 10.4 running as a VM machine on my MacBook and it doesn't have any issues connecting to either of my 802.11n AirPort Extreme Base Stations (AEBSn). However, I should note that the VM considers my network connection is via Ethernet and may not be relevant here.
    Can your Ubuntu box connect to any other Wi-Fi or just not to the AEBSn? How do you currently have your AEBSn configured? That is what radio mode and wireless encryption type is it set for? What is the make/model of the Ubuntu device's wireless?

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

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

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

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

  • Dell latitude unable to detect Airport Extreme base station

    I have an Airport Extreme base station at my parents house and I am unable to detect the wireless network or connect to the base station on Dell Latitude D610 with Windows XP. I installed the base admin utility for windows Xp and it cannot detect the base station.
    Please help....

    You don't need the utility to connect, it is ONLY used to configure a base station.
    Problems connecting an XP PC to an Airport Base Station
    http://www.ifelix.co.uk/tech/2002.html
    iFelix

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

Maybe you are looking for