Airport Utility can't read my AEBS configuration

I know there have been thousands of questions/answers to this topic, but I'm stumped.
As of last night, my AEBS has not been cooperative. It has been working perfectly ever since I got it last December. As far as I know I have not made any changes. I am running 10.5.8. Everything is up to date. My airport utility is able to locate my device, but as soon as I press "continue" it can't read the configuration & comes back with an error saying the utility was unable to find my airport wireless device. And yes, I've tried everything.
-soft reset
-hard reset
-using ethernet cable
-re-installed airport utility.
-restart, unplug, reboot, etc...
-searching countless forums, posts, blogs all to no avail.
I'm having to use my neighbor's wireless connection to get on the internet. The odd thing is that I have a business VOiP phone connected to my router, and it works just fine. I just can't configure my AEBS now that I restored it to it's default settings. Boggling my mind.

I'm having a similar problem. It turns out that there is some kind of voltage issue on the WAN side of my equation. I bought a second Airport Extreme, thinking my WAN port was smoked. When I plugged the WAN wire into the new Extreme, everything worked. Old Extreme, I get Ethernet unplugged. Worked for about a week on the new one, then rebooted the new Extreme and kaput, nothing works. I tested the WAN connection to my Macbook - works great. If I take a Dlink router, plug the WAN into that, plug another wire from the DLink to Extreme WAN, Airport is happy.
There is a specific sensitivity (voltage?) to the Airport Extreme WAN port that makes it say the Ethernet is Unplugged. As an added bonus, my testing seems to confirm that when this condition exists, the Extreme also shuts down all the other router ports, as over wireless I can not access the other physical segments (i.e. my NAS). Yet if I my WAN is happy on the Extreme, the other ports work as well.

Similar Messages

  • AEBS stopped working/ airport utility can't read base station configuration

    AEBS was working fine including the 7.1 update except printer wasn't working. As I attempted to trouble shoot network, AEBS stopped working. I tried accessing it through airport utility but it couldn't find the base station. I have now done a hard reset four times and though airport utility will recognize the base station it gets hung up trying to read the base station configuration. So I can't troubleshoot the AEBS from airport utiltity and the yellow light keeps flashing. What do I do now?

    AEBS was working fine including the 7.1 update except
    printer wasn't working. As I attempted to trouble
    shoot network, AEBS stopped working. I tried
    accessing it through airport utility but it couldn't
    find the base station. I have now done a hard reset
    four times and though airport utility will recognize
    the base station it gets hung up trying to read the
    base station configuration. So I can't troubleshoot
    the AEBS from airport utiltity and the yellow light
    keeps flashing. What do I do now?
    I had the same problem and a hard reset (6 seconds on the reset button) was recommended by Apple Tech support and that did it for me. The AE was back being seen and allowing me to reconfigure it from scratch.

  • Airport utility can't read settings on my airport express after down loading update to yosemite

    airport utility can't read settings on my airport express after yosemite update

    I already did that & it works but i shouldn't have to do it at all, only started after update.

  • AirPort Utility can't see either AEBS or AirPort Express using either comp.

    I have an AirPort Extreme Base Station (AEBS) and an AirPort Express (APE). The dsl connects to the AEBS via ethernet (in the first slot), and the AEBS connects to the desktop via ethernet (in the second slot; it has no AirPort card). The PowerBook (PB) connects to the network via its AirPort card, and the APE is used to extend the network range.
    All of this worked as of last night.
    This morning when I woke the PB, it wouldn't connect to the network automatically. I tried to connect manually, but it wouldn't accept the password. (Maybe I'd forgotten, when's the last time I had to enter it?) I went to the desktop to set up the AEBS to reset the password. Both the AEBS and AirPort Express showed up on AirPort Utility (AU) on the desktop before doing so.
    After resetting the password, neither showed up in AU. (I suppose it's not surprising that the APE wouldn't, but the AEBS is connected via ethernet, and the ethernet is working or I couldn't connect here as set up.) I get the message that AU can't detect any Apple wireless devices. I rescanned several times with no luck. And I have pressed the reset button on the AEBS to no avail.
    I also can't see either the AEBS or the APE with the PB, which does have an AirPort card, as I mentioned.
    Any help or advice would be appreciated.

    Theirry, I had (among all the other things I'd done) already pushed the reset button for a little while, but that didn't work. So, not knowing what else to do, I pushed it and held it while I counted to ten three times, and that worked. Probably one could get away with less.
    After that, I had to start over again with the AEBS on AU, but I gave it the same network name and the password I thought I remembered, and the APE rejoined it automatically.
    I hope that helps.

  • Airport Utility can SEE TC, but not CONFIGURE it?

    I received my 1TB TC about a week ago (dual band).
    Setup
    I have AT&T U-Verse with a 3800HGV-B modem/router. Before my TC I had a Linksys Wireless router with DHCP turned off (I let the AT&T router handle DHCP). And yes, I turned wireless on the AT&T router to OFF.
    I knew that I wanted to let my TC handle DHCP so when I plugged the TC in and "set it up", I went to access the internet and my AT&T router put the TC on "DMZ Plus". The TC is handling DHCP for all of my wireless devices, and the AT&T router has 3 clients (2 cable boxes and the TC).
    Problem
    Every now and then I will go to access the USB hard drive plugged into the back of my TC and it will time out. Going into Airport Utility, it will recognize my TC, but when I click "Manual Setup" it times out trying to access the TC configuration. Internet still works, so the routing is fine, but I can not configure it. I've tried this on my iMac and my Macbook. The status light always remains GREEN.
    The only solution is pulling the power plug.
    My TC is on a 10.0.1.X ip schema network and my AT&T is on a 192.168.1.X schema. Am I having a DHCP conflict? Can anyone else think of why this might be happening?
    ALL firmwares/softwares are updated. EVERYTHING is wireless with the exception of the ethernet cable connecting my AT&T router to my TC.
    I've searched the internet high and low and can't seem to find any answers.

    *This just in!*
    Apparently unplugging the USB hard drive I have plugged into my TC will resolve my problem COMPLETELY. One question...WHY?!
    This doesn't seem to add up, but sure enough -- If I unplug the USB hard drive connected to the TC, I have NO PROBLEMS accessing the configuration for the TC. I did notice that the USB hard drive's power light turns off when the drive is not being accessed.

  • Airport Utility won't read base station configuration

    Hi
    This is very frustrating. I've just bought a new iMac and found out my previously working Airport Express that I use as an AirTunes hub can't be seen in iTunes.
    No problem, after trying everything I decided to reset it's factory defaults and then use Airport Utility 5.2.1 to set it up again from scratch. The utility sees my Airport Express hub and when I go to configure it it just stops on 'Reading base station configuration...' and doesn't move any further.
    Has anyone any idea why the utility is playing silly sods?
    Gaz

    I am having the same problem (sort of). I have two AX set up as WDS. I can see both units in Airport Admin Utility but cannot read configuration on either of them. It accepts their passwords but then returns the message "unknown error connecting to Airport Express" after a minute or so of the spinning rainbow.
    My main AX seems to be working fine. I can connect to the internet and my home network from either my iMac or MacBook Pro but my range is fairly limited which leads me to believe that there is a configuration issue with the 2nd AX as a WDS client but I can't check it. I have tried soft, hard and Factory reset all of which seemed to be successful but the problem still persists.

  • Airport Utility can't see AEBS?

    AEBS is working fine on a wireless XP laptop and ethernet connected pc.
    MacBookPro can connect to internet fine when using the ethernet connection
    but I've lost my wireless network and Airport Utility can't find my AEBS at all.
    It started whilst i was using 7.1.1 and have upgraded to 7.2.1, reinstalled Airport Utility from disc and tried everything else I can think of but no joy
    Any suggestions?
    Thanks

    It's fixed itself after the third reset, utility still couldn't find any network but went into system preferences/network and was able to find a network that way. Re-opened Utility and there it was.
    Hope this might be helpful for someone else

  • Loaded Mountain Lion and time capsule no longer works, airport utility can't be configured, back ups have stopped, sparse bundle in use errors occur, what a mess!!!!

    Should Airport Utility now be defunct for my time capsule because I have upgraded OS to Mountain Lion? I have tried every fix I can think of but AU will not set up. I'm also getting repeated time machine back up failures and now I have a new "sparsebundleinuse" error which is totally useless to me, I have no idea what a sparse bundle is, I have no idea what it's suddenly being used by and there's no information to say what to do about it. Apple is killing me here!!!

    I've tried to but on the install for Airport Utility 6, after the download I get through the introduction then the license then I get "airport utility can't be installed on this disk. The version of Mac OS X on this volume is not supported" and that's it, no more options!?

  • Airport disk utility can't read time capsule after a relocation

    airport disk utility can't read time capsule after a relocation. Wether I connect ethernet or wifi, airport doesn't read it. Even after reset.

    Do a full factory reset.. and you will need to reconfigure it.. that is the usual process when you move networks.
    You can do a fully manual setup though. The new v6 utility is just lousy at locating the TC.. if you still have a computer.. even a PC running windows it will do fine on v5 as long as the TC is not the latest model..
    Or use iOS version airport utility.. it also seems to have less issues than the mac version.

  • AirPort Utility can't see Extreme

    Airport Utility can't see Extreme
    I have reset the extreme, reboot the iMac, and while I have an internet connection, the AirPort Utility can the the extreme.
    Light is flashing Amber.
    AirPort Utility is 5.3.2

    SoCal Web Developer wrote:
    click on the AirPort icon (of your Mac) on the upper menu. See if the Extreme >> network shows up there. If so, log into that network...
    SoCal Web Developer wrote:
    So following your instructions I, disconnected everything, powered it up, and from the Airport icon I could see other wireless networks and join them.
    Next I created a new network with the Extreme, and join that one.
    I see nothing in his instructions about 'creating a new network'. Instead, I see the words: See if the *Extreme network* shows up there. If so, log into *that network*...
    SoCal Web Developer wrote:
    If that does not work, get an ethernet cable and connect the
    Extreme to your computer.
    SoCal Web Developer wrote:
    I originally had it hard wired to the iMac and could not see it with AU.
    Connect Mac to Ethernet LAN port on the AEBS. Make sure your Mac has IPv6 turned on (under System Preferences|Network|Advanced|TCPIP|Configure IPv6=Automatically). Open the Airport Utility.
    If you still don't see the Airport, open a terminal windows and type:
    mdns -B airport.tcp
    If you get a response, look for something under the "instance name" column. Take that name and type (replacing the name you got above with 'thatname' below):
    mdns -L thatname airport.tcp local.
    and copy the result and post it here.
    If you don't get a response from the first command, enter:
    ifconfig
    and copy the result and post it here.

  • My airport utility can't find the airport device.

    Everything is connected. I bought the device about eight months ago and have used it successfully to set up wireless networks twice. Now i have a DSL modem, and there was an error that the IP was in use. So i followed some tips online to reset both devices, restart, etc. Currently i have everything connected and plugged in, including with an extra ethernet cable from my laptop to the airport's wan port. However, NOW the airport utility can't find the device and it's just sitting there blinking amber slowly. The modem is all lit up and green and appears to be working. ***? is the airport express broken?

    adubatowka14 wrote:
    I got the AU to find my AE by connecting them with an ethernet cable.
    How are you configuring up the Express once you have AU working with it? Please provide us with what you want/need to have.

  • Airport Utility can't see all my devices after new cable modem

    Everything worked fine until I got a new cable modem from Comcast—it's a Cisco DPC3000. Now after firing that up, I can get to the web on my Mac Pro but my LAN seems to be missing. Airport Utility can see the AEBS (Base Station) that's connected to the cable modem but it can't see a second AEBS that's in my wife's office (wired to the Base Station in Bridge mode), or an Airport Express that's hooked up to my music system, or a second Airport Express that's used to extend the WIFI to a second bedroom. All these things worked fine previously—I could see them all in Airport Utility and I could access all those devices.
    Any ideas will be much appreciated—been dealing with this most of the day.
    Thanks
    Peter

    Well what do you know...after a week, it just magically decides to work, without even using Airport Utility.
    Boy are these Airports touchy....and unreliable.
    I still want to know: What makes these things drop in and out???

  • Airport Utility can't see Airport Express Device

    I tried to print some documents and I received a message telling me the printer is not ready or may not exists, so I launch the Airport Utility to see what is going on and there is no Airport Express just my Time Capsule.
    I already reset the airport express to factory settings and everything goes ok until the green light shows but the airport utility can't see it.
    Any help will be appreciate
    thanks
    Dan
    I already tried connecting the Airport Express to my computer with an ethernet cable

    Connect an Ethernet cable between the wall jack and the WAN (circle of dots) port on the AirPort Express. Connect a second cable between the LAN (opposing arrows) port on the Express to your computer.
    You should now be able to access the Express using the AirPort Utility to configure the Express as a WAP.

  • Airport Utility can't find base station

    I feel like I must be missing something very obvious. But my Airport Utility can't find any base stations, even though I am successfully connected to this network, the base station is about three feet away from the computer, and Internet Connect has no trouble finding it and specifiying the base station's id.
    I have just done a wipe-and-install of my whole computer; I've reinstalled all software from CDs or installers, and this utility wanted to upgrade to version 5.2.1 (it says Disk Version 2.0 on the disk) before running, so I did that. And no base station detected, despite rebooting the computer, and rescanning any number of times. I'm using OS 10.4.6.
    What can I do?
    Message was edited by: Paul-ny

    There is something puzzling that bothers me, even though I have things working again.
    I first lost access to the AEBS when I tried to use Airport Utility to change the security setting of my network. It has been on the default WPA2 setting, and I was wanting to downgrade that to WEP because the long WPA password was too long to be accepted by my Palm TX Wifi software. But the shorter WEP password shouldn't have been a problem. At the time, after my system reinstall, the utility and the base station seemed to be working all right.
    When I completed resetting the base station with WEP, though, there was an error message, after which I could no longer connect to the network with my laptop (using the old password or the new password), and then the utility lost sight of the base station as well. I had to do a hard reset and start over. When I did the same thing again, the same thing happened. When I reconfigured the base station with the WPA2 security, though, it all worked, and my laptop could get back online.
    At this point I tried changing it again to WEP, and the same problem recurred. One last time with WPA2, and that's where I am now, except that I was pleased to find that my PDA, which had just been replaced under warranty, has some newer software in it and it now can accept my passkey (?)-- my airport code rather than the 64(?)-digit number version of it, so it's working, too.
    But apparently Airport Utility has lost sight of the base station again. I don't need it for anything, but this is annoying. What's more curious, though, is what was happening when I chose WEP security.

  • After port forward, airport utility can no longer see my time capsule

    I tried to forward public port 1025 to private port 80 on a raspberry pi using  airport utility. But after I did that,  the airport utility can no longer see my time capsule. Wifi still works correctly. Are there any conflicts about port 1025? How to fix that other than resetting the time capsule?
    Thanks,
    Michael

    It doesn't sound like a port that is used.
    From the standard google search.. nope.
    Reboot the whole network..
    No luck tell me what OS version you are running the utility on and what model and firmware TC???
    Note with Yosemite, anything can and will happen.

Maybe you are looking for