Comcast HSI, AirPort Extreme Base Station issues

Recently, I've been having some connection issues with my Comcast High-Speed Internet and my AirPort Extreme Base Station. I'll be connected fine one minute, and the next my AirPort monitor drops to 2 bars of signal and nothing will connect. Resetting the base station and the modem works about 50% of the time, while just sitting here "dealing with it" works the other half of the time.
I rent my cable modem from Comcast, and I believe it is the Terayon TJ715. I went to the Apple Store San Francisco and had my base station replaced, thinking it was the culprit, but alas, the problem is continuing, only less frequently.
I've replaced all my ethernet cables, tried it with my AirPort Express (which works more often, yet has the same problem occasionally), yet my connection uptime and signal still drops to 2 bars and essentially disconnects.
Even stranger, the computer I have connected to the LAN port seems to work fine even when the computers connecting wirelessly are having issues.
I'm going down to a Comcast Support Center on Friday to (hopefully) replace my modem with a newer model (someone told me that older Comcast modems "kill" AirPort Base Stations), but other than that, any ideas? Anyone have this type of issue with Comcast in the past?
The 3 machines im running are:
Dual-Core 2.3Ghz Power Mac G5 via AirPort
867MHz PowerBook G4 (Titanium) via AirPort
800MHz iMac G4 (Flat-Panel) via Ethernet
Thanks,
Alexis
Dual-Core 2.3GHz Power Mac G5   Mac OS X (10.4.3)  

Don,
Thank you for the link. However, it did not seem to solve my issue.
It's not that I haven't been able to connect to the internet at all using wireless. I will be connected fine (all 3 computers connecting to the internet simultaniously) when suddenly, any machine connected via AirPort (specifically my Dual-Core Power Mac G5) will receive two bars of signal and will no longer connect to the internet. The only remedy I've found is to reset both the cable modem and AirPort Extreme Base Station, and this only works about 50% of the time.
I am going to have Comcast replace the modem (and in the meantime, get new Ethernet cables) tomorrow, so hopefully I won't be having this issue anymore, but I'm more curious what may be causing the issue. Have you heard anything about older Comcast modems causing latency issues with AirPort Extreme Base Stations?
Thanks again,
Alexis

Similar Messages

  • Vonage, AirPort Extreme Base Station, and Comcast

    I just picked up an Airport Extreme Base Station, and wanted to use it to get my MacBook Pro on my home network. However, I can't get it to actually provide an network connection to the MacBook. In the Network pane of System Preferences, under the Network Status, AirPort has a yellow icon, and the following message: "AirPort is connected to the network HulkNet. AirPort has a self-assigned IP address and may not be able to connect to the Internet."
    Here's my current setup:
    Comcast > Cable Modem > LinkSys RTP300 > PowerMac, PC, AEBS
    I have the "Distribute IP addresses" disabled on the AirPort, and the internet for the PowerMac & the PC work fine. In the network status of the RTP300, the AEBS is listed as having an IP address of it's own.
    Any gurus out there that can help me figure this out? I just want to be able to access my home network from anywhere in the house!

    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?

  • Airport Extreme Base Station Internet Connection issue

    I have a connection question for Airport Extreme Base Station.
    I have Comcast cable broadband. I connect that to a Linksys router for
    use with my Vonage phone, and then from the Linksys router I connect
    via Ethernet to my iMac. I like the direct Ethernet connection for
    performance reasons.
    In order to set up a home network to connect my Tivo's (and eventually
    my PC and printer), I have set up an Airport Extreme Base station and
    connected it to the Linksys router from it's ethernet connection to the
    WAN (cable modem) input on the Extreme.
    I have connected to the Airport network with my iMac, but since I am
    connected to the Internet via Ethernet, I cannot tell if my Airport is
    connected to the Internet so that I can use it for my Tivo. My PC is
    still in storage from a move, so I can't check with that.
    My question: How can I tell if my Airport is connected to the Internet
    without disabling my Ethernet connection on my iMac?
    A few more info points/questions in case it helps answer:
    1) I previously used this Airport to connect this iMac wirelessly.
    2) Should I be connecting it to the LAN port since it's coming out of
    the router?
    3) If the connection issue is because I am going through the Linksys
    first, can I connect the modem to the airport and then use the LAN port
    to connect to the Linksys router?
    4) If I have to disable the ethernet connection to test the Airport,
    how do I do it? Just unplug it?
    I appreciate any help as the online and manual help from Apple is not
    quite up to par with such a complex configuration.
    Regards
    Bill

    2) Should I be connecting it to the LAN port since it's coming out of
    the router?
    No, connecting to the WAN port is fine.
    3) If the connection issue is because I am going through the Linksys
    first, can I connect the modem to the airport and then use the LAN port
    to connect to the Linksys router?
    The issue is that you have two routers which effectively creates two networks. Unless this was your original intent, you will want to setup the AEBS as a bridge.
    To set up the AirPort Extreme Base Station (AEBS) as a bridge, using the AirPort Admin Utility, connect your computer directly (using an Ethernet cable) to the LAN port of the AEBS, and then, make these settings:
    Network tab
    - Distribute IP addresses (unchecked)
    - Apply the new settings.
    - Wait at least 5 minutes.
    4) If I have to disable the ethernet connection to test the Airport,
    how do I do it? Just unplug it?
    Well, that's certainly one way, but an easier way is to temporarily disable the "Built-in Ethernet" in your network configuration.
    System Preferences > Network > Show > Network Port Configurations
    - Built-in Ethernet (unchecked)

  • Several PC and Mac connectivity issues with Airport Extreme Base Station

    Hello,
    This is not all necessarily airport base station related, but there is some crossover, so I'm posting all of these issues...
    Here is the laundry list of things that I can't make work in a home network that contains a PC w/ XP Home, MacBook 1.83 w/ 10.4.7, and Airport Extreme Base Station w/ Modem.
    1. Can't see the PC from the Mac.
    a. "Connect to server -> Browse" does not find the PC
    b. "ipconfig" on PC provides valid looking IP address
    c. ping from mac to PC IP address times out
    d. Firewall on XP is disabled via control panel
    b. Windows file and printer sharing is enabled
    2. Can't see mac from PC
    a. Windows file sharing enabled on mac
    b. Firewall on mac disabled
    c. I used \\MacIPAddr\shortusername
    d. ping times out
    3. Using dial-up to access internet, how do i tell airport to dial using PC?
    a. this feature is working fine from mac
    b. If already connected (via instruction from mac), can surf the internet fine from PC
    c. Is this even possible from the PC?
    4. Can't see printer connected to base station from PC
    a. See it fine from mac
    b. How do i "find" the printer on the PC?
    c. Is Bonjour required for this? (I don't have it on the PC yet)
    5. Can't see a "shared" printer on the PC from the mac
    a. printer is connected directly to PC
    b. Mac's add printer wizardry looks like it may "see" the printer, but then it asks for username and password for PC. This is XP home, with no usernames or passwords. Single user. Nothing seems to work in the credentials pop-up dialog.
    Any suggestions on any of these issues is very welcome.
    Thanks

    Is the PC running any kind of internet security or firewall software?
    1. Can't see the PC from the Mac.
    2. Can't see mac from PC
    Sharing files between an XP PC and a Mac running OS 10.4.x
    http://www.ifelix.co.uk/tech/3020.html
    3. Using dial-up to access internet, how do i tell
    airport to dial using PC?
    Jon Sevy has a Java Utility for this purpose.
    You will need Java in order to run the utility
    http://www.java.com
    4 . Can't see printer connected to base station from
    PC
    Printing from a Windows XP PC to a printer attached to an Airport Extreme Base Station or Airport Express
    http://www.ifelix.co.uk/tech/1004.html
    Printing from a Windows XP PC to a printer attached to an Airport Extreme Base Station or Airport Express using Bonjour
    http://www.ifelix.co.uk/tech/1008.html
    Problems with finding Printer Driver on Windows XP when using printer connected to Airport Extreme or Express
    http://www.ifelix.co.uk/tech/1012.html
    5. Can't see a "shared" printer on the PC from the
    mac
    Printing to a printer on a XP PC from a Mac running 10.4.x
    http://www.ifelix.co.uk/tech/3015.html
    Printing to a printer on a Mac running 10.4.x from a Windows PC using Bonjour for Windows
    http://www.ifelix.co.uk/tech/3014.html
    iFelix

  • Setting Up Comcast to Work with the AirPort Extreme Base Station

    I just set up Comcast high-speed internet through the cable modem and ethernet connection and it works fine. What I need is a step by step instruction on how to set up the connection through my AEBS. I've tried to configure using the Admin Utility, the AirPort Set-Up Assistant, the Network panel---all with no success. I'm not sure what to enter in the boxes or what to check. I've read the "Designing AirPort Networks" PDF and it wasn't much help.
    The AirPort Network was working fine with the dial-up connection I had before.

    Voila! NOT!!!
    I'm having the same problem trying to set up a friend's "new" Macs, and I cannot get them connected to the internet. I've also followed the same steps. I tried the resetting trick (unpluging, waiting, repluging the modem first, then the Airport Extreme Base Station.)
    The DSL ISP is SBCGlobal. Their dsl modem is SpeedStream 5100. The AirportEBS is the about 4 year old white base station with the phone jack, and a WAN and a LAN ethernet ports. I'm trying to connect two iBooks and a MacMini.
    Everything did fine for the past year with the modem in "regular" mode and only ONE Mac connected. When the new Macs were recently acquired, SBC techs said that the modem needed to be put into PPPoE mode so that multiple Macs could be connected at the same time. This was done. [The techs said in regular moden the modem does the authentication; in PPPoE mode the modem acts as a bridge and the AirportEBS is the router and provides the authentication. I am assuming the techs are coreect, but I don't know for sure.] The CAT5 ethernet cable from the modem goes into the WAN port on the AEBS. The computers all see the local wireless network set up by the AEBS.
    However, when any of the Macs try to connect to the internet, the error message returns "No PPPoE server available." Resetting the modem and base station has not cured this. [n.b. Bypassing the AEBS completely by connecting the CAT5 cable from the modem directly to the Mac will provide internet connection.] Any other ideas? Sounds like both of us are having the same sort of problem.

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

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

    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.

  • Is my AirPort Extreme base station A1034 (802.11g) compatible with Comcast 50 Mbps internet service?

    Is my AirPort Extreme base station A1034 (802.11g) compatible with Comcast 50 Mbps internet service?

    The WAN port on the A1034 will handle up to a 100 Mbps Internet connection, so you are OK there.
    Wireless on the A1034 is limited to 54 Mbps tops, so things should work OK as long as wireless devices can receive a strong wireless signal from the Apple router.

  • How do I open the same ports on an Airport Extreme Base Station for multiple computers at the same time?

    As the title suggests...
    I have a mix of five Mac and PC's at home using an Airport Extreme Base Station as the router.   I need many ports opened on the AEBS for all of the computers- not just one computer.  (for example: three people want to play TF2 on Steam at the same time; each machine needs the correct ports open on the router).   Port forwarding  only allows me to forward a given port to a single IP, yet I need that port open for five differnt IP's, all at the same time. 
    How do I do that on an AEBS?
    In the same way, I have a small office of four iMacs using an old airport with the same exact issue.   I would like to be able to connect to all of them remotely with Apple Remote Desktop, but the port forwarding on the airport only allows a port to forward to a single IP.   I want to be able to tunnel into the office network and log onto any machine behind the Airport extreme... not just a single IP.    I currently have it set up where I can tunnel into the office from my house, I can find the one machine that the port forwarding has been assigned to, I can log on and everything is just fine... with one machine.    How do I open the firewall for the other machines? 
    TL,DR version:  How do you open ports on an Airport Extreme Base Station instead of forwarding ports?   Forwarding ports doesn't work for multiple IP's.  

    You can open a single or multiple ports to a single device or different ports to different devices, but you cannot open the same port to multiple devices via the AirPort Utility for the Apple routers.

  • How do I find a hard drive connected to Airport Extreme Base Station?

    *Apple Says:* "If your base station supports it, you can connect a USB hard disk to the USB port on your base station and computers on your network (both wired and wireless) can connect to it to access, share, and store files and data."
    Cool. So I followed the instructions. The drive is recognized by the base station and listed in the Airport Utility. It looks like it's ready to go...
    So... How do I access the drive? I don't see it on my desktop, it's not under network. I've tried "Connect to server..." and browsing, I can't see the drive, anywhere. Yeah, I've searched the crap out of this issue on google and this message board as well as apple support knowledge base. I'm sure this is a simple issue and I'm just missing the obvious. Help me out.

    Hello Timothy Uhl. Welcome to the Apple Discussions!
    Try the following to mount the disk...
    o Click on the Desktop to enter Finder
    o Go > Connect to Server...
    o Enter 10.0.1.1 for the server
    o Enter Disk Password
    o Connect
    If this still doesn't solve the problem, let's double-check your disk sharing settings...
    AirPort Extreme Base Station (AEBSn) - File Sharing Setup
    Either connect to the AEBSn's wireless network or temporarily connect your computer directly (using an Ethernet cable) to one of the LAN ports of the AEBSn, and then, using the AirPort Utility in Manual Mode, check these settings:
    Disks - File Sharing
    o Secure Shared Disks: <With disk password | With base station password | With accounts >
    (Note: Choose "With a disk password," or "With base station password" if you want to secure the shared disk with a password, or choose "With accounts" if you want to secure the disk using accounts.
    If you choose to use accounts, click Configure Accounts, click the Add "+" button, and then enter a name and password for each user that will access the disk.)
    o Guest Access: <Not allowed | Read only | Read and write>
    o Share disks over Ethernet WAN port: (unchecked)
    (Note: Select the "Share disks over Ethernet WAN port" checkbox if you want to provide remote access to the disk over the WAN port.)
    o Advertise disks globally using Bonjour: (unchecked)
    o Workgroup: <Windows workgroup name>
    o WINS server: <WINS server IP address>

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

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

  • HT1218 After a recent iTunes update attempt iTunes no longer functions and the airport extreme base station is not accessable on our computer.  We still have wifi but cannot access the base station software.

    After a recent iTunes update attempt iTunes no longer functions and the airport extreme base station is not accessable on our computer.  We still have wifi but cannot access the base station software.

    Thanks for the reply. I appreciate the response. I tried that approach this evening and it didn't work for me. (Technically it worked for me, when I was hardwired into my base station, but would not work for me wirelessly, which is my main issue.)
    Again, using the approach you recommended works only if I have my ethernet cable attached to the LAN port so my computer is communicating directly to the base station through the hard wire. I am able to scan for my base station and make setting adjustments normally this way too.
    As soon as I disconnect from the LAN port and try to go wireless is where I run into problems. The Base Station's wireless network I created is available to choose in the top right corner of the monitor with all of the other available wireless devices/networks -- but the network I created does not have access to the internet. I am also unable to configure my Base Station wirelessly. When my Airport Utility tries to scan for the Base Station and Network, it cannot find any Apple Wireless Device. It's like the Wireless Network in my base station is not sending out a signal.
    Is there a way to resolve this issue?

  • Airport Extreme base station no longer playing nice with Mac Pro

    This is a strange problem...
    I have an Airport Extreme base station (purchased in 2004) that I use with verizon DSL to get a wireless network going in my house, and I connect three computers wirelessly.
    I have an ipod touch and toshiba PC laptop that are both able to connect to the network and run just fine. But lately (past 2 weeks or so) when I try to connect with my MacPro desktop I can go to a few sites, but after a few minutes the airport locks up. At that point none of my computers will connect and I have to unplug and then replug the airport. At that point the network will start up again and if I do not try to get on with Mac Pro then things run fine, but when I try to connect with desktop again, after another few minutes the same thing happens.
    I know the problem is with the airport and my Mac Pro - I have done numerous connection experiments and have narrowed the problem down to that.
    Is it possible that my MacPro might be drawing more power and causing the airport to overheat? (it is rather hot in the room with DSL connection)
    Or should I accept that the current base it old, and bite the bullet and get a new base?
    Any thoughts?

    Could you post what you did in order to resolve the issue. I'm having a problem with the base station in that I cannot connect to the internet with my laptops (a mac and pc) while I can connect wirelessly to my network with my desktop (G4). The base station is not detected in the base statin admin utility or the aiport setup utility. If anyone else has a solution I would be much obliged to read it.
    Thanks!

Maybe you are looking for