Airport extreme base station is turning off when computer sleeps

I had Brighthouse upgrade my modem to their "Lightning" package. They installed a new modem. I had to make some config changes to block their wireless router and continue to use my airport extreme. Everything is working but when my computer goes to sleep or is off, I can't get on the internet with my laptop or I-phone.

Similar Messages

Why does my AirPort Extreme Base Station lose the internet when I unplug my printer Ethernet cable?

I just changed ISPs to Qwest from Speakeasy. New modem. Now my etherneted (from extreme base station) printer (Brother HL1870N) doesn't work.
And if I unplug the printer ethernet cable from the base station, the base station loses the internet connection.
Any help would be appreciated.
thanks

whats the version on your airport extreme and what renerations is it?

What needs to be done to avoid WIFI drop-offs with Apple AirPort Extreme Base station with Extended Wifi

Hi there,
can anybody please advise me what needs to be done to avoid WIFI drop-offs every half an hour or 1 hours.
I use voip phoe calls a lot using my WIFI, However my AirPort WIFI connection drops-off while I am in the middle of WIFI VOIP calls. This is causing significant disturbance in my family.
Please assist.
In details, I have extended my WIFI range using 2 Apple Airport Extreme Base Station.
Main Base is - A1408 9 (5th Gen), and I have extended my WIFI in my L shape house by connecting another Apple AiPort A1354 ( 4th Gen) with AA1408.
Note1:
> when I am close to A1408 my iPhone4 connected with A1408 automatically
> When I am close ot A1354 , my iPhone4 connected with A1354 automatically.
Note2: these drop-offs never occurred when I had only 1 Apple AirPort Extreme Base station WIFI
I think, this Auto switching causing the slight drop outs in my Wifi when I am on the VOIP call.
Do you think that something is going wrong with my Apple AirPort Wifi extended?
Much appreciated

To help eliminate drop-offs you need to ensure that your extended network is operating at its peak bandwidth performance. Base station placement is critical in an extended network. Please check out the following AirPort User Tip for details.

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.

Certain web address not available when using Airport Extreme Base Station

Hello. To access my "secure" account at the local library, I must use a web address that contains a colon followed by a number. I believe that this is a port number, but I confess that all the discussions here regarding ports are going well over my head, and I may be incorrect with this assumption.
My problem is that while I CAN access this site by connecting to my DSL router directly via ethernet cable from my iMac G5, I cannot access the site when connecting to the internet in the mode: iMac Airport to Airport Extreme Base Station to DSL router via ethernet.
The format of the web address is: http://xxxx.yyyy.net:####/zzzzz/, where #### is the number I guess may be specifying a port and causing my problem.
Can anyone advise me, in simple terms, how to get to this address when in the Airport--internet connection mode? Will the solution have any adverse side effects?
Regards and Thanks
iMac G5, 2.5 year old AEBS Mac OS X (10.3.9) Westell 327W 4-port DSL Modem, not using wireless feature.

Very likely the embedded firewall that comes with your AirPort blocks the port you are trying to use.
In order to solve this, best way is to modify the AirPort settings (open the AirPort maintenance app):
Click at the tab "port forwarding" and add the desired port as "public port" to the list. "private IP" is the IP of your Mac and for "private port" type in the port number again.
If you are unsure about the IP of your Mac, look at the network maintenance application.
Well, one side-effect is that you have an open port in your configuration which could cause security issues... but only if you are paranoid So there is nothing to care about (note that without the AirPort inbetween your Mac and your modem, this port would be not blocked and freely accessible

I told my wireless network to forget two airport expresses so that I could rename them. Now the network does not see them even when plugged in about 10 feet away from the airport extreme base station. Does "forget" mean forever? How to reset?

I told my wireless network to forget two airport expresses 1 1st gen, 1 2nd gen so that I could rename them. Now the network does not see them even when plugged in about 10 feet away from the airport extreme base station. The network does recognize a totally new 2nd gen express. Does "forget" mean forever? How to reset?

The network does recognize a totally new 2nd gen express.
Then, it sounds like you have already reset the 2nd Gen Express, and now you need to set it up again, like you did the first time. Only, this time, assign the device name that you want to the AirPort Express.
Do NOT use the name that Apple suggests.....which will be something goofy like........Sueswimsf's Red Apple AirPort Express
Assign a simple name.....something like 2ndGenExpress

Error on Airport Express when using to extend Airport Extreme Base Station

I have had continual problems trying to get my Airport Express (n) to extend my Airport Extreme Base Station. The signal it is receiving is "good". The settings are correct (as far as I can tell) and it was working for a brief period of a month or so.
Now it is not working and I have a red 1 in a circle (like an update is needed... but it will not take me to an update) on the Sirport Express in my Airport Utility.
Under "Status", it says "Extended Network" with a green crcle, but the main circle on by the name is flashing green, and will not send a signal.
Also in "Status", it says this: "This AirPort base station was unable to extend the wireless network. Make sure the wireless network you're trying to extend was set up and is working correctly, that you entered a matching wireless network password into this device, and that this device is in range of the wireless network."
I have done all of those and yet..... STILL not working. Ugh.
Any thoughts? Procedures?
Thanks in advance.

At this point, I would suggest that you perform a "factory default" reset on the AirPort Express. In its default mode, the Express will broadcast an unsecured wireless network with a network name of something like: Apple Network NNNNNN.
Your Mac should recognize that there is a "new" AirPort Express present. You will find this on the dropdown menu from the AirPort icon on the OS X menu bar. Select the Express from the dropdown menu and the AirPort Utility should automatically start up to allow you to configure it.

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

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

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

Solution to Airport Extreme Base Station + Airport Express networking probs

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

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

Why does the new Dual-Band AirPort Extreme Base Station act as a proxy?

The previous thread
http://discussions.apple.com/thread.jspa?threadID=1531675
has been archived and nothing came of it, but after testing, I'm certain that their findings are true.
The Dual-Band AirPort Extreme Base Station (AEBS) with firmware 7.4.1 acts as a proxy for TCP ports 21, 554, and 7070 when NAT is turned on. This can be verified by using Nmap on any external server known to NOT have the ports open and having Nmap return that the ports are open. You can telnet to these ports to verify that they're "open," even though they are not on the server.
This functionality appears to be undocumented and as far as I can tell, the only way to turn it off is to put the AEBS into bridge mode and having some other device do NAT further upstream.
As a computer professional, this functionality extremely undesirable, particularly since it is not documented and doesn't have an "off switch." I wasted a bunch of time with one of my network engineers because of this, thinking that some network router was spoofing our server. I also wasted a bunch of my time trying to detect whatever "stealthy rootkit" had opened a FTP server and some other botnet related ports on our server, when in reality, it was simply my AEBS tricking me.
Disabling NAT-PMP ("Enable NAT port mapping protocol") does not affect this.
Is it too much to ask to have a checkbox in the "Advanced" section of the AirPort Utility to turn this feature off?

Welcome to the discussions forum Michael Bennett2.
Thanks for investigating this odd behavior.
If you want your work to be noticed by those who can effect change, you'll have to tell Apple via their feedback link. It won't do any good to post it here.
http://www.apple.com/feedback/

Macbook w/Airport Extreme Base Station

I have a Macbook that I just bought 3 days ago. Like everyone else, I am having the same problem with wireless encryption.
However, when I turn off the WPA and just use WEP, I can connect but it seems to lag. What I mean is everytime I browse, it's almost like my computer needs to "reconnect" with the router. If I stay a a site for more than a couple of minutes the connection kind of goes to sleep. It shows I am connected but it just sits there, sits there, and then connects. When I am on WPA or wired I do not get this.
So, for my actual question, does the Airport Extreme Base Station have issues like this?
On Apple.com, people are giving it glowing reviews. On the net, the reviews are marginal at best.
Current Setup:
Macbook
Linksys WRT54GX4 w/SRX400
Thanks in advance!

I have several Linksys routers and also an Airport Extreme Base Station. I like the Linksys better. The AEBS has arguably better output power than my Linksys, but in my 1600 square foot house, it doesn't matter.
I also have a Macbook c2duo running OSX 10.4.10, and it drops off the AEBS just as much as any other router.
The downside of the AEBS is that it doesn't have a native web based management system. You've got to use the management tool to deal with the AEBS using SNMP protocol. It'd be nice if you had to manage 100 AEBS, but is a nuisance for home use. I found the latest realase of Airport utility (v5.2) to be very buggy on Windows XP - it killed my PC's abaility to negotiate a DHCP lease until I downgraded back to version 5.1. I ultimately went back to using my WRT54GS. The Linksys has lower throughput, but that only matters for specsmanship. The other thing is that Linksys can do multiple PPTP VPN pass through, but VPN pass through doesn't work on the AEBS unless you use bridge mode and static IPs.
I spent the cash for the AEBS, but in retrospect I would have rather put it towards memory upgrades, etc.
Bill

Cannot access certain web sites through Airport Extreme Base Station

I use the old (round) Airport Extreme Base Station (AEBS). Approximately three weeks ago I could no longer connect to americanexpress.com or to Godaddy or their mail servers. About a week ago the Godaddy sites started working again, but the American Express sites are still not working.
My current setup:
- AEBS connected to Time Warner New York cable modem
- Three Airport Express units - two connected to speakers, and one set up with WDS to provide Ethernet access to computer (PowerMac G5), which is in a separate room from cable modem
- I also have an Airport card in my G5 to connect directly to the wireless network (but that doesn't solve any of my problems)
I have tried resetting all the units, and have also tried running the network with all the Airport Express units turned off, none of which as allowed me to access American Express.
I have the exact same problems with my work-issued Windows 2000 laptop when logged in to the wireless network.
When I plug a computer directly in to the cable modem, I have no problem accessing any of the sites, which leads me to believe that the solution somehow lies with the AEBS - I just can't figure out what it is.
Any help/suggestions are much appreciated.
PowerMac G5, 23" Cinema Display, Airport Extreme Base Station (802.11b/g) Mac OS X (10.4.9)

If you're having trouble with throughput performance or just connecting to some websites, try changing the MTU value, on your Mac, to 1492. (The default value is 1500.) To do so, you can use a utility, like Cocktail or via OS X's Terminal.
MTU will vary with connection type. Cable and non-PPPoE, can use up to 1500, whereas PPPoE connections (WinPoet, RASPPPOE, Enternet, etc.) can only use up to 1492. For secure VPN connections (i.e., IPSec) use a MTU value less than 1500.
The best value for MTU is that value just before the packets get fragmented. To test, use the Ping utility.
OS X: ping -D -s 1472 www.dslreports.com
WinXP: ping -f -l 1472 www.dslreports.com
Reduce 1472 by 10 until you no longer get the “packet needs to be fragmented” error message. Then increase by 1 until you are 1 less from getting the same error message. Add 28 more to this (since your ping packet size, not including IP/ICMP header is 28 bytes). This will be your MaxMTU. (Note: If you can ping thru at 1472, stop, you’re done! Add 28 and your MaxMTU is 1500.)

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.

Importing Snow Configuration to the Airport Extreme Base station

Is it possible to import the Snow's airport saved 'base config' and 'access control list' files to the Airport Extreme Base Station when setting up the extreme? I'm considering upgrading my wireless system. I have 4 XPs and 4 Macs and would prefer not to have to re-enter any of this data or loose any downtime reconfiguring all my computers.

As far as I am aware this is not possible.
However if you configure the Airport Extreme BEFORE you turn off the Snow the downtime should be minimal.
From a security perspective, unless you have Macs running 10.2 or earlier and/or your PC wireless adapters don't support it, all you really need to do is implement WPA for a secure wireless network.
Personally to avoid potential issues I would create a completely new wireless network with a new network name. Some clients have issues with joining a new wireless network with the same network name as a previous network, especially one with a password.
iFelix

Airport Extreme Base Station and G4

I have a G4 Desktop running OS 10.2.8 and a G4 laptop running 10.2.4 wth an Airport Card. I have high-speed internet access through a Wi-Fi ISP. I attempted to set up the AIrport Extreme base station, running the cable from the WiFi Antenna through the base station and connecting the base station to my desktop trough the ethernet port. When I attempted to run Airport set up, it could not find an airport card in the desktop, so this went no where. I was not able to access the internet through the base station, I expect because I had not set up the airport system. I was left with only dial up internet service and a significantly slower operating system. I gave up and reconnected directly to WiFi.
For what it is worth, the center light of the base station was on and the light to right was blinking through out this time. Any assistance is welcome.

Ok, please try the following, in order. After each step, try powering-down and restarting the Mac to verify if the steps solved the problem. If it hasn't continue on to the next step in the sequence:
1. Run the Disk Utility to repair Disk Permissions.
2. Turn off the Mac OS X Firewall
o System Preferences > Sharing > Firewall
o Click the "Stop" button.
3. Move System Configuration Files
(Note: You will have to reestablish your network connections settings.)
o Go to /Library/Preferences
o Move the SystemConfiguration folder and com.apple.networkConfig.plist file to the desktop.
o Restart your Mac. (Note: OS X will rebuild the files that are now sitting on your desktop. If this doesn't resolve the issue, you can move the folder & .plist file back to it's original location.)
4. Create a New User Account
o Create a new user account.
o System Preferences > Accounts > Click "+" to add a new account
o Log off, then log back on with the new user account.
o Try connecting with the AirPort.

Airport extreme base station is turning off when computer sleeps

Similar Messages

Maybe you are looking for