Airport Extreme Base station - number 3 - a manufacturing or OS / FW issue?
I figured I ask the community.
I bought my first AEBS in July. Initially it worked great! Wireless, plus VoIP - great. Then, after 2.5 months it started acting up. First the wireless, then the ethernet, then it was gone.
Took it to the Apple store on October 15th. The tested it, and admitted that it was broken. After 10 days I got a new one. Set it up without a problem worked beautifully like the first one in the beginning. Until Friday, November 10th. This time it seemed to be able to connect, but then I couldn't get any internet connection. Neither wireless, nor through the ethernet.
Back to the Apple store. The tried all kinds of resets got, but with the same results - got it connected, but no internet connection.
I got a new one - number 3. Took it home, set it up, and after some tinkering got it to work with both Macs. For about 15 minutes. Then neither Mac can see the AEBS anymore, yet the ethernet connection (in this case VoIP) works fine. I tried resetting it many times, always with the same result. I get it to connect, but then after about 5min the wireless connection is gone. Neither computer can see it.
I can't believe that it is a problem with the AEBS, but rather has something to do with the OS / Firmware. I am using the latest of everything. How could possibly 3 of them be broken - I seriously doubt that.
I don't have any problems with a Linksys router that I am using right now to post this message.
Any thoughts/ suggestions are rather welcome.
Thanks!
Thomas
iMac G5, MacBook Pro Core 2 Duo 2.33 Ghz Mac OS X (10.4.8)
I am having a similar problem. I just purchased a Time Capsule with airport/router built-in. I setup it up 2 days ago and it was a breeze. My iMac, Macbook Pro, and 2 iPhones connect to it wirelessly via DHCP with no problems. Suddenly this morning my Macbook Pro and 1 iPhone cannot get an IP address, other than the dreaded 'Self-assigned' 169... address. I can get an IP with my Macbook Pro connected via Ethernet with no issues. I did not change ANY settings. How is this possible? Also, I have a guest network setup on the second band and all of my devices can connect to that with no trouble, even the said Macbook Pro and iPhone. iMac has been connecting all along to everything. I've tried the following on the Macbook:
- Removed Airport, rebooted, re-added Airport, rebooted
- Forced a manual IP address (yes outside the range of DHCP reserved addresses)
- Removed power / rebooted Time Capsule
Nothing works. I know my wireless card is fine because I can get an IP from the guest network. What gives?
Similar Messages
-
Airport Extreme Base Station and DSL modem, IP address Conflict issues
I recently set up DSL service in my apartment. I have ATT yahoo DSL modem, and an Airport extreme base station plugged into it. The network works fine with my Vista PC connected to it, but when I try to connect my macbook to the network I get errors telling me the IP address the macbook wants to use is already in use, and my PC gives me an IP address conflict error.
The internet is fine, and the modem is configured automatically, so I think it must be a problem with the way the network is set up or the network settings on my macbook...
any ideas?All,
I recently posted what I believe to be a similar/identical issue. See my post here: http://discussions.apple.com/thread.jspa?threadID=1378849
I have not changed my AEBS to "Off (Bridge Mode)" yet, because everything currently 'works' but I continue to get the occasional "Double NAT" warning suggesting I switch the AEBS to bridge mode. When this happens, I lose connection to the internet and need to unplugged both the AEBS and my modem to re-establish a connection to the internet and the external HD I have connected to the AEBS.
My question for Jmiller1138, do you continue to get the "Double NAT" warning even when you changed your AEBS to "Off (Bridge Mode)"? I am hesitant to change my AEBS to bridge mode since I'm assuming I'll need to totally reconfigure my entire network (meaning both the AirPort Extremes, my wireless HP printer, and my firewalls on my PCs).
The ignoring of the warning (i.e. closing the AirPort Utility without updating the AEBS) is what triggers the need to reset my AEBS and modem. Not fun.
I guess I'll just need to bite the bullet and set the AEBS to bridge mode . . . yes? -
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. -
How do I connect my Synology NAS to my AirPort Extreme base station?
I'm considering replacing an Apple AirPort Extreme base station with my current 5 year old router. I would appreciate if someone could tell me how the AirPort Extreme differs from any regular router. I do not have any OS X devices, but I have a lot of iOS devices. If my understanding is correct, I can set up the AirPort from an iOS device.
Also, I need to know how I would connect my Synology NAS system to the AirPort Extreme network via an Ethernet cable. I would need to be able to acces the files on the NAS through Windows clients. My Synology NAS currently has a web interface....would I still be able to access that web interface with the AirPort?
Thanks for all your help in advance as I am VERY new with networking devices.I would appreciate if someone could tell me how the AirPort Extreme differs from any regular router.
The AirPort Extreme is a combination router, wireless access point, and Ethernet switch. It also provides both external USB hard drive and printer sharing. So, it is not much different than most other routers on the market today. The one main difference is how you administer it. Unlike most other routers that employ a web-based administration interface, the AirPorts use a dedicated utility, called the AirPort Utility.
I do not have any OS X devices, but I have a lot of iOS devices. If my understanding is correct, I can set up the AirPort from an iOS device.
Yes. There are versions of the AirPort Utility for OS X, Windows, or iOS devices.
Also, I need to know how I would connect my Synology NAS system to the AirPort Extreme network via an Ethernet cable. I would need to be able to acces the files on the NAS through Windows clients. My Synology NAS currently has a web interface....would I still be able to access that web interface with the AirPort?
Your Synology NAS would connect to the AirPort Extreme pretty much the same as for any other manufacturer's routers. That is, you would connect it to one of the available LAN (opposing arrows) ports on the Extreme. You would still use the same web-based interface as before.
Note: When connected to an Ethernet port, the NAS would still function as usual. The AirPort Extreme would not provide any file sharing functionality when connected in this manner. All file sharing features would be the responsibility of the NAS device. -
2 airport extreme base stations later and still no internet connection-
Sorry - yet another beginner with internet connection troubles! (I have read all the posts I could find relating, but without any help).
I have had a Demon broadband account now for about a month (I’m in the UK) and in that time I have purchased a D-Link DSL-300T Ethernet modem and an Airport Extreme Base Station. I got wireless internet working relatively easily – with a powerful range over the whole house and garden, but then one Sunday night, the internet connection via the base station suddenly ‘died’.
I spent the following 3 days scrutinising all of my settings of both the Modem and the Base station, re-setting both, and bought new Ethernet cables / micro filters etc but with no luck. (I’ll point out at this stage that my broadband account is still active, and if I connect the Ethernet modem directly to my iBook [wired] I can still get my broadband connection. Alternatively, I tried daisy chaining the modem to the base station and then via an Ethernet cable to an iBook, but no connection could be made).
When wireless, Airport Admin recognises there is a modem there, and under preferences > network under Airport it states I am connected to the internet – but I’m not.
I then phoned D-Link and they confirmed my firmware was up-to-date for use with Apple products and talked me through all of the modem settings and tweaked a few things, but there was still no connection to the base station. I then phoned Apple. They were incredibly helpful (as ever) and after 35 min. came to the conclusion the base station might not be re-setting itself properly. The replacement one came yesterday, and again I spent a number of hours trying to get it connected to the internet, but there is still no internet connection via airport and I can confirm this from both my eMac and iBook.
Reading through the forums on here, I understand that my particular modem is problematic with the base station, but I can’t work out why it use to work and now it doesn’t! One theory I have investigated is that the firmware of the base station is two advance for the modem following an update, but after reinstalling the original firmware I started with, I still have no luck.
- The eMac is running 10.3.9 / iBook is running 10.4.3. The base station is reinstalled with the latest firmware via system update. The first base station and the modem were delivered to me 31/10/05.
Any help or suggestions would be really appreciated if anyone has any ideas
Thanks for your time
Will.
UK.http://discussions.apple.com/thread.jspa?threadID=2316
78&tstart=0
I think if you follow the instructions I gave in this
link you will be fine.
Remember, If you for any reason loose your
connection, it is normally always a Power Issue..Your
ISP is down for service ..or some other anomoly, If
you were good before your settings will still be
good...Good Luck...Don
Hi Don,
Thanks for you quick response. I printed off the instructions you posted on the support forum before, and ran through your procedue exactly, (twice) but I'm sorry to inform you that I haven't been able to re-establish my wireless internet connection. Would it be safe for me to assume at this stage that my modem is indeed fualty? It contines to work fine independantly, (I'm using it right now) but it can't seem to make contact with the basestation.
Will. -
Connecting Airport Express to Airport Extreme Base Station
Hi Folks. I am at my wit's end.
I have an Airport Extreme Base Station (main hub) purchased in 2003. Just bought a new Airport Express and it just won't connect to the AEBS. I think I've tried everything. From automatic WDS set up (described here http://docs.info.apple.com/article.html?artnum=107454) to using the Airport Utility and/or Airport Admin to set up. Nothing.
I've looked through the discussions and found this http://discussions.apple.com/thread.jspa?messageID=7011490� but the solution provided makes absolutely no sense to me.
All I end up getting after numerous attempts at connecting to the AEBS is error messages and then a flashing yellow (amber I guess) light. When I do a "hard reset" it just goes back to flashing amber and it seems a factory reset doesn't work because according to this http://docs.info.apple.com/article.html?artnum=108044 I'm supposed to see the green light flash four times after I hold the reset button and plug in but that never happens.
This is driving me crazy. Anyone have any ideas?
Thanks.Hey John.
I did finally solve the issue but I'm not quite sure how it happened but this is what I did:
First, I did had hard reset on the AEBS and set it up all over again via AirPort Utility. I set it up to use a WPA/WPA2 personal password.
Next I did a hard reset (not a factory reset) (hard reset: while plugged in, use a paper clip and hold the reset button for 15-20 seconds) on the AirPort Express and then restarted my computer.
After restart, I opened AirPort Utility and set up the Express to join my AEBS network. When it got to the point where it asked me to choose the network to join, I chose my AEBS network and it magically knew the WPA password I had set earlier and then after that it was smooth sailing.
I had tried a number of variations of that process many times before (and failed) and for some reason this time, it worked.
Hope it works out for you.
Best,
Benjamin -
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) -
Using Airport Extreme Base Station As A Wireless Card?
Hi,
I don't know if this is even possible but here's what I'd like to do:
I've started to share an internet connection with a cousin of mine that lives in my apartment building. The connection is in her apartment and as far as I can tell the wireless signal is coming from the modem she has, there is no stand alone router/ base station. So far I've just been connecting using my iBook with the aiport card in it. No problems. I just had to get the ip number and password from her and I was hooked right up.
Here's my real question:
I also have a G4 Mini with no wireless card in it at all and an Airport Extreme base station from before we started sharing a connection. In the time that we've been sharing I haven't connected to the internet at all using the Mini. Now I'm wondering if there is a way I can hook the Airport Extreme to the Mini and somehow use it as a replacement for a wireless card in the Mini. Thus using the Mini connected to the Airport to connect just the Mini to the internet.
I'm not worried about the iBook and do not wish to reconfigure the way I'm using/ connecting with it. Everything is peachy with that.
If this is possible, how can I do it?
Thank you in advance for any help with this.Ernest Lohrer wrote:
Hi,
I don't know if this is even possible but here's what I'd like to do:
I've started to share an internet connection with a cousin of mine that lives in my apartment building. The connection is in her apartment and as far as I can tell the wireless signal is coming from the modem she has, there is no stand alone router/ base station.
She has an "integrated" modem/router/access point.
So far I've just been connecting using my iBook with the aiport card in it. No problems. I just had to get the ip number and password from her and I was hooked right up.
Here's my real question:
I also have a G4 Mini with no wireless card in it at all and an Airport Extreme base station from before we started sharing a connection. In the time that we've been sharing I haven't connected to the internet at all using the Mini. Now I'm wondering if there is a way I can hook the Airport Extreme to the Mini and somehow use it as a replacement for a wireless card in the Mini. Thus using the Mini connected to the Airport to connect just the Mini to the internet.
I'm not worried about the iBook and do not wish to reconfigure the way I'm using/ connecting with it. Everything is peachy with that.
If this is possible, how can I do it?
Set up the AEBSn as a "bridge" and connect the G4 Mini to one of the "wired" internet connections. -
Airport Extreme Base Station N adjusts time, then drops WDS
I have a WDS network with a +Time Capsule+ (TC = WDS Main) and an +Airport Extreme Base Station with 802.11n+ (AEBSn = WDS Remote). Everything works great - except when it doesn't. The AEBSn will suddenly drop the connection, and instead of a normal IP address (10.0.1.11) it will get a self-assigned one (e.g. 169.254.130.58). I have pawed through a number of log files, and I see that at the point that things go south, I get a whacky net-time update; for example:
Jul 31 20:25:21 Severity:5 Internet Configuration leased -- host <10.0.1.11/255.255.255.0> gateway <10.0.1.1> dns <10.0.1.1> wins lease <14400> domain <dclient.lsne.ch>
Jul 31 19:54:15 Severity:5 Clock synchronized to network time server time.euro.apple.com (adjusted -3606 seconds).
Jul 31 20:55:35 Severity:3 No Address for NTP server time.euro.apple.com.
Note the 1-hour backwards time adjustment; after that, the AEBSn has dropped the connection. Note that there was no user traffic on the network at the time - no one was home.
Sometimes the status light on the AEBSn will go yellow, sometimes it stays green - I haven't been able to detect a pattern to that. The TC is zen: he's green no matter what happens. I thought he was supposed to be a caring master?
I thought this was perhaps related to interference from other wireless networks - I live in the city and there are a bunch around me - so I moved to the least-used primary frequency band: no change.
Help!!! This is driving me bananas. Thanks in advance.Bob,
Thanks for the response, and sorry for taking so long to get back. I think I found how to fix the problem of the dropped WDS connections, and I wanted to give it a while to make sure the problem was really fixed.
The drops got to be more and more frequent, until finally the WDS connection would drop pretty much immediately. At that point, the TC (the master in my setup) for the first time started showing signs of being unhappy: the status light would briefly flash orange at irregular intervals (I could see nothing relevant in the log file, though). I had always assumed the problem was at the AEBS end, and had always restarted him, but this time I tried restarting the TC - and bingo presto, everything started working, and has been working for over a month now, without ever restarting the AEBS.
I would guess that there's something in the WDS implementation (at least on the TC) that gradually degrades over the period of many months - memory leak or fragmentation or similar.
Thanks for the suggestion about the "extend a wireless network" option. When I read the manual, I got the impression that was just an automated way of setting up WDS; I didn't realize that it affects the band used. I now realize that the title of the section, "Extending the Range *of an 802.11n Network*," is not totally anodyne. Anyway, I just now set it up as you suggested, and so far, so good.
Thanks again,
-- Philip -
When was my airport extreme base station built
Can you tell me when my AirPort Extreme Base Station was built? Its serial number is 6F706F6SVZC. I figure this will help me determine a number of tech items about this model, including what generation it is. Thanks!
It is an express not extreme.. at least according to this.
Serial Number: 6F706F6SVZC
Model:
- AirPort Express (802.11n)
Codename:
- No codename assigned.
Build Country:
- This unit was built in China.
Build Year:
- This unit was built in 2007.
Build Week
- Your device was built in week 6 of that year (February).
Production Nr.:
- This unit was number 1250 to be built that week. -
I have an Airport Extreme Base Station now and I would like to know if I can use an Airport Express to extend my wifi network or do I have to use another Airport Extreme Base Station.
This AirPort Express:
http://www.apple.com/airportexpress/
It is the only Express with 2 Ethernet ports. All others are "old"
Apple does not specify a model number in their product information, but it is A1392 in the U.S. I do not know if Apple uses different model numbers in other countries. -
i have an airport extreme base station ,i conneted a hdd and i want to acces the hdd with my macbook from another place ...office...school....
I would appreciate if someone could tell me how the AirPort Extreme differs from any regular router.
The AirPort Extreme is a combination router, wireless access point, and Ethernet switch. It also provides both external USB hard drive and printer sharing. So, it is not much different than most other routers on the market today. The one main difference is how you administer it. Unlike most other routers that employ a web-based administration interface, the AirPorts use a dedicated utility, called the AirPort Utility.
I do not have any OS X devices, but I have a lot of iOS devices. If my understanding is correct, I can set up the AirPort from an iOS device.
Yes. There are versions of the AirPort Utility for OS X, Windows, or iOS devices.
Also, I need to know how I would connect my Synology NAS system to the AirPort Extreme network via an Ethernet cable. I would need to be able to acces the files on the NAS through Windows clients. My Synology NAS currently has a web interface....would I still be able to access that web interface with the AirPort?
Your Synology NAS would connect to the AirPort Extreme pretty much the same as for any other manufacturer's routers. That is, you would connect it to one of the available LAN (opposing arrows) ports on the Extreme. You would still use the same web-based interface as before.
Note: When connected to an Ethernet port, the NAS would still function as usual. The AirPort Extreme would not provide any file sharing functionality when connected in this manner. All file sharing features would be the responsibility of the NAS device. -
I have just purchased and installed a new Airport extreme base station but now the Airport Utility cannot see my old Airport Express. Are their compatibility issues and do I need to purchase a new Express?
When you can, take a look at the old AirPort Express and locate the model number in the faint print on the side of the device.
If you see A1084 or A1088, this is an older Express version that is no longer supported by the current version of AirPort Utility that you are using with the new AirPort Extreme.
If that is the case, your Express is at least 6 years old...probably older...so it is about time to treat yourself to a new version with much faster speeds and more features. -
I can't find an ac power adaptor for my AirPort Extreme base station.
I was given an AirPort Extreme base station, the square model, I just need an ac power adaptor. I can't seem to find one that will definitely fit. Help please?
It is easier and better to give the model number from the base.. A1143 is the oldest Airport Extreme that is N wireless.
http://en.wikipedia.org/wiki/AirPort_Extreme
All the models from Gen1 to Gen5 use the same power supply.. 12v 1.8A
But it can be replaced with any standard 12v supply.. of sufficient current rating.
The real thing is expensive. It still doesn't have the Apple cord.
http://www.ebay.com.au/itm/New-Genuine-A1202-12V-1-8A-Power-Supply-AC-ADAPTER-fo r-Apple-Airport-Base-/290923848575?pt=US_Power_Supplies&hash=item43bc69a37f&_uhb =1
Buy a power supply rated at 12v 3a 4a or 5a .. any of those ratings will work well.
I generally buy 4a or 5a. as they tend to be a bit better. Although if you check they all seem identical to each other..
Check in your local market if you want one fast.. just do ebay search for 12v 4a power supply..
http://www.ebay.com/itm/I-MAG-Electronics-IM120EU-400D-Genuine-OEM-12V-4A-AC-Pow er-Supply-Adapter-/380641968538?pt=Laptop_Adapters_Chargers&hash=item58a007819a
Power cord is probably a standard IEC computer cable.
Cheaper from HK but if you want reasonable quality pay around $10US.. cheaper can be rubbish.
Maybe you are looking for
-
Is there a way to connect the Apple TV as a second display without it automatically changing my Mac's audio output? I would prefer to use an audio interface for playback and the apple tv as a third display. I know I can go back to system preferences
-
I was really excited to see the free update to the opertaing system and pretty happy when things like iBooks and a new version of iMovies downloaded to my Mac. However, I am still trying to wrap my head around the reasonsing behind the podcast funct
-
i just installed itunes 12 and now when i plug my ipod into my computer it won't sync I have tried different ipods still nothing
-
[solved] - BenQ RL2450HT noisy screen
Just attached a BenQ RL2450HT monitor to my T510 thinpad with VGA cabel. I've ran `xrandr --auto` and tried to set manually the resolution however in both cases the screen is noisy on dark parts. I'm using the `extra/xf86-video-nouveau` package. Shou
-
Email Issue using FM SO_NEW_DOCUMENT_ATT_SEND_API1
Hi Experts, I am sending few data in through excel(in attachment) using fm SO_NEW_DOCUMENT_ATT_SEND_API1. I wanted to dispaly the data line by line in excel sheet. I properly populated the data in parameter 'contents_bin' i.e. appended the data line