Airport Extreme not getting IP address

I've recently moved, but stayed with Verizon and their DSL service. When I plugged in my modem and Airport Extreme at my new house I couldn't get an IP address or other internet connection. My G5 connects with the modem easily via ethernet (hence my post here), but not my Extreme. I've done the whole pull the plugs for five minutes routine several times as well as dowgraded the Extreme firmware to 5.5.1 and then back to 5.6 again with neither working. I tried using my Airport Express in the same capacity and it fails as well.
Any ideas? Everything worked flawlessly in the past as you would expect from Apple products.

The service is identical in every respect. I'm using the same modem since this is considered a transfer account they wouldn't send a new one unless I wanted to be charged more money. The connection still uses DHCP and the account name and password are the same (although I can't really remember ever needing them).
I just spoke with Verizon and they recommended I unhook the modem for eight hours to allow the Verizon equipment to recycle and perhaps that will solve the problem. I'll keep you posted unless you have another suggestion before then.
Thanks!

Similar Messages

  • Airport Extreem Not Getting IP Address

    My Airport Extreem BaseStation is communicating with my cable modem and my computers, but is not getting an IP address and connecting to the internet. However, when I plug the ethernet cable straight up to my laptop the laptop gets on the internet. I have two laptops and neither one can get on the internet wirelessly through the Airport Extreem Basestation, but they can both connect when they are physically plugged into the cable modem. Help!!

    By "first time user" I was referring to someone who had just taken their Airport Base Station out of the box and was trying to set it up for the very first time.
    Perhaps you situation is very similar to Richard's. While in your case, power cycling the Base Station did eventually solve the problem, another solution that has worked for many people with a problematic Base Station after the Airport 4.2 upgrade is to do a hard reset and reconfiguration from scratch of the Base Station. Apparently this is also the solution recommended by Apple's own tech support people in response to a problem like this.

  • Since latest update to airport extreme im getting 10 unknown base station and time capsule items showing in airport utility as a network.  when able to "forget" them they initially drop off but soon return. how do i get them deleted and stay that way

    since latest update to airport extreme im getting 10 unknown base stations and time caps showing up as though they are a part of my network. sometimes i can "forget" them and they will disappear initially but soon return. i need and want only my connection inside my home . any ideas. i have done a factory reset and set up a new network but they continue to show up.

    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.

  • Nas on airport extreme not recognized by time machine. same nas was previously used as time machine backup on different airport extreme. are there any configuration files that i can delete to fix this problem ?

    nas on airport extreme not recognized by time machine. same nas was previously used as time machine backup on different airport extreme. are there any configuration files that i can delete to fix this problem ?

    Time Machine has been working just fine, but in the last week or two it has given up the ghost. I reset the connections to the drive, and it will basically save a few bytes of data and then hang.
    Although Apple originally announced, prior to the release of the first 802.11n AirPort Extreme Base Stations (AEBSn), that it would support Time Machine backups to AirPort Disks, they removed that option before they did finally release the base station for sale.
    Since then, Apple has posted (as you have noted) that they DO NOT support Time Machine backups to AirPort Disks. As far as I know, they have not changed from that position and those who do these backups find that they become corrupted over time. Sorry, but it sounds like you just confirmed that for yourself.
    1) Has one of the recent updates either on the AE (firmware) or OSX disabled this function?
    No. Again, this feature has never been supported by Apple for every generation of AEBSn released.
    2) Are there any changes I can make to get this working again?
    If your data backups are critical to you, then you will want to use a different solution for your Time Machine backup destination drive strategy. I would suggest that you connect your WD My Book directly to your Mac in the mean time.
    Your other options would be to either use a Time Capsule (which interestingly does support TM backups to AirPort Disks) or a non-Apple solution like the Drobo FS or HP MediaSmart server.

  • Airport does not have IP address and Self assigned IP address

    Using a 2.66GHz Mac Pro with OS X.6.6 and a Netgear DNG200 wireless and installed Airport Extreme Card and WPA2 security.
    In Network click on Airport and 'Turn on Airport' Up comes the message 'Airport dos not have IP address and is unable to connect to the internet'.
    Go into advanced and double click 'Network Name'. Supply password even though remember is selected, and message changes to "Airport has Self Assigned IP address 169.254.etc.etc and will not be able to connect to the internet'.
    After repeated back to Network Name and double clicking and supplying password eventually connects. Simple to reconnect by selecting Turn Airport On in Menu Bar so long as the machine is not turned off.
    Any suggestions please?
    Message was edited by: harryb

    Hi,
    http://osxdaily.com/2009/12/22/mac-wireless-problems-guide-to-troubleshooting-ai rport-wireless-problems-on-your-mac/
    Hope it helps.
    Cheers.

  • Why does my airport extreme not recognize my cable modem anymore?

    Why does my airport extreme not recognize my cable modem anymore?

    Have you tried resetting the modem? Power it down and let it rest a moment, then power it back up again.
    Also, some ISPs require physically detaching their cable from the modem for it to be fully reset. Literally unscrew it from the modem. Try that, in conjunction with powering it down.
    Don't do anything with your Extreme, other than powering it down too, in the event the modem reset does not help. Reconfiguring it may be necessary but this is not justified quite yet.

  • Guest users not getting IP address

    I am setting up Cisco wireless along with ISE 1.3 for guest wireless.  The client is going to use the self-registration portal for guest wireless users.  I followed this Cisco doc to configure the self-registration portal:
    http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/118742-configure-ise-00.html
    I tested this in my home lab and everything works fine.  However, at the client users are not getting IP addresses from the DHCP server.  This is the same DHCP server that is used for corporate wireless and if you connect that SSID, you get an IP address.  I have looked what I configured at home and the client and everything looks the same.  In the back of my mind, I feel something is missing, but I can't figure out what it is.  
    Edit: Not sure if this makes a difference or not, but they are using a Nexus 5K for their core switch and it hosts the SVI for this network.  
    Let me know what information you need and I will post it.
    TIA,
    Dan

    Hello,
    Some verifications below :
    Did you verify if DHCP Proxy is enabled in wlc's wlan interface ? Case DHCP proxy is disabled, did you verify if the ip helper address is enabled in Nexus SVI ?
    DHCP Scope is enabled in the DHCP Server or is enabled in the WLC ?
    Verify if Trunk in the switch is enabled correctly passing all VLANs to WLANs ?
    Verify if ACL to redirect configured in the WLC is allowing DHCP Server and DHCP Client to client receive IP Address and ports 8443 to Cisco ISE and DNS to resolve some address and get access to ISE Portal ?
    The scenario is Local Switching or Central Switching ?
    Regards

  • DHCP via Hyper-V VM, Server2012r2 Hyper-V host, clients not getting IP address

    You have to authorize a dhcp server as Britv8 says. That's the only way it'll start dishing out leases. That's standard for Windows DHCP server in an AD Domain.
    Also there's 0 reason to mention Hyper-V here. The whole point of virtualization is to do hardware level abstraction.

    I recently encountered this. Setup:
    Initial setup of the system was at a different location from its final destination, with different network equipment (switches) between the two. No teaming is involved, however.
    Set up the system at its final destination, with DHCP via a Hyper-V VM (Server2012r2), Server2012r2 Hyper-V host, physical clients on the lan were not getting IP address.
    The physical server box has a 4-port Intel Gigabit ethernet card.
    I moved the setup (Hyper-V Virtual Switch manager) so that the interface for the DHCP server VM was isntead using one of two built-in Broadcom adapters.
    While this topic seemed promising,
    http://community.spiceworks.com/topic/251317-hyper-v-vm-not-leasing-ip-s-dhcp
    unfortunately, "fiddling about" was not what I was looking for as possible solution.
    My notes for the resolution:
    Hyper-V system running...
    This topic first appeared in the Spiceworks Community

  • When connecting wired my router straight from my internet provider I get speeds in the 90mps range.  Now when connecting wired through my airport extreme I get speeds near 10mps. Also when using wireless for my ipad3 I recieve download speeds of .63mps.

    When connecting, wired, to my router from my ISP I get speeds in the 90mbps range.  Then when connecting, wired, to my Airport Extreme I get speeds of 10mbps.  Wirelessly I get download speeds of 6mbps on my laptops and only 1mbs with my Ipad3.  I am making sure only one device is sharing the network to make sure to get accurate results.  Why are things so slow?

    Hi Ty,
    First, check with you ISP to see what speed they've promised.  In my case, they indicated that the speed should be greater than 50 Mbps.  If they say that it should be significantly higher than what your getting, then try the following if you're using Airport Utility v.6.:
    1. Open the Airport Utility (Desktop: Command+Shift+U to open Utility Folder, select Airport Utility)
    2. Click on the visual representation of the Airport Extreme and then select "Edit" (bottom right corner)
    3. When the window opens (to a tab "Base Station"), click on the "Wireless" tab,
    -it should have the following options: Network Mode, Wireless Network Name, Wireless Security, Wireless Password, Verify Password, a checkbox with "Enable Guest Network", and a button "Wireless Options..."]
    4. Select "Wireless Options", which should open another window with the following options:
    5Ghz network name, Country, a checkbox with "Create hidden Network", Radio Mode, 2.4 GHz Channel, and 5 GHz Channel [both of which can stay on "Automatic"]
    5. Clicking on  "Radio Mode" will bring up a list in which the las option should read:
    802.11n only (5Ghz) - 802.11n only (2.4 GHz)
    Once you click "Save", your router will blink amber for a little while and then it should work.
    Hope this helps.  Let me know if it does/doesn't.
    DFLovesBikes
    p.s. I apologize if the directions were excessively explicit, but I was thinking about my 73 year-old mother trying to follow them, so I erred on the side of making them more understandable.  Good luck.

  • Trying to set up Directv GenieGO using Airport Extreme.  Getting error message: DHCP range entered conflicts with the WAN IP Address of your base station.  How do I resolve the conflict.

    Trying to configure an Airport Extreme manually.  After I enter the IP Address of the GenieGo along with the rest of information required I am getting the following error message when I click update:
    DHCP range entered conflicts with the WAN IP address of your base station. 
    How do I resolve the conflict? 

    You cannot use the same range on LAN and WAN if you are routing.. it must be different.. and you should not be routing at all.
    The AE should be in bridge mode. NO DHCP settings at all.

  • Airport extreme not receiving an ip address

    Hey i was wondering if anyone knew why my airport extreme is not receiving an ip address. Im connected to the internet through a cable modem connected to a airport extreme. I know the internet works because when i connect directly to my macpro book the internet works fine.......its just when i try to use my wireless network. Also its not my wireless card in my laptop because it works fine with other wireless networks. The other thing is i know my airport extreme works because it will connect for a while and then it wont connect at all until i reset everything (modem, computer, airport).....any suggestions?
    I called apple support and they said it was a comcast problem and comcast said it was a problem with my airport extreme......figures huh?
    macpro book 15"   Mac OS X (10.4.8)  
    macpro book 15"   Mac OS X (10.4.8)  

    i think i found the answer while browsing the archives.
    http://discussions.apple.com/thread.jspa?messageID=2202720&#2202720
    sjones posted this:
    FIXED!
    Ok, after getting the usual run around with apple not being able to advise me about my ISP and my ISP not being able to advise me about apple some wonderful support person at my ISP let a bit of info slip: Comcast have decomissioned a load of bad DNS servers today.
    If you use Comcast and cannot connect via wireless try this:
    Open applications/utilities/airport admin utility
    select your base station
    click configure
    click internet
    whatever is typed into the dns servers input boxes, delete it
    update your base station
    and you are connected to the internet.
    It makes perfect sense if you have this problem. You base station has been trying to connect to the WAN using a decomissioned dns server. All Comcast dns servers are now distributed dynamically via the dhcp server.
    I am working again! Hope you are too.
    I tried it, and was able to connect to my mini-mac for the first time. Phew! Now, I'm going to try the printer and my powerbook. I hope my tinkering with those does not tamper with the delicate balance of the universe.
    Sjones, if you see this, THANK YOU!
    Power PC G4 & Mac Mini   Mac OS X (10.4.3)  

  • Airport not getting IP address

    So here's my problem.
    I have a wireless linksys router that I've never had a problem with before until recently. My Mac connects to the network fine, but it says that my Airport does not have an IP address and that I can't get internet access through it. I have full bars and am connected to the network, but no internet. My roommate is connected via ethernet to the router with his PC and his works fine. Even when I connect mine via ethernet, I still have no internet connection.
    I got on the phone with a Linksys technician who ran me through configuring the router, and after about an hour of trying he said that it wasn't a problem with the router but with my airport settings.
    Please help! I know next to nothing about networking and I really need internet access for my work!
    Macbook Pro 17" Mac OS X (10.4.8)

    You may want to check the thread about not being able to connect to the internet. <http://discussions.apple.com/message.jspa?messageID=3615819#3615819> I am starting to get the idea that it my be effecting several differnent types of laptop and not just the iBook G4. I am cruising around and hearing similar stories of people having problems not being able to connect to the internet all of a sudden with their laptop, me being one of them. See if it doesn't sound similar.

  • Airport Extreme Not Consistently Assigning DHCP

    I am using a relatively new (within the last year) Airport Extreme as the primary router on my home network.  Connected directly to the router is a GigE switch, an AT&T Microcell, and another router - an Aruba RAP which creates a secure VPN for my home/remote office network.  The connection to my Apple desktop is made through the GigE switch, as are three additional wired connections to other devices in my home, including two Apple TV's and (hopefully) two Airport Expresses.  
    I recently discovered when trying to configure a new Airport Express to extend my wireless network over ethernet (roaiming network) that my Airport extreme is not consistently assigning the IP addresses within it's defined DHCP range (10.0.1.0 - 10.0.1.200).  About half of the time devices on the network are getting a default 169.254.x.x IP address, which (in the case of my desktop) results in an 'self assigned IP' error within the network settings.  I can reboot my apple desktop and the next time it gets a correct 10.0.1.1 address.  Reboot again, it defaults back to a 169 address - and so on. It doesnt seem to make any difference if I connect my desktop directly to the Extreme, or, if I connect it through the GigE switch.  And, every time I get a 'self assigned IP' I have no connectivity beyond the Extreme (no internet), and I'm forced to use my wireless/Airport connection.
    Another problem here is that the Expresses both expect to receive 10.x IP addresses and when they don't get one, they basically become pretty $100 paperweights when connected over ethernet. Also, if you try to configure a new Express without the 10.x address it expects to be assigned (and defaults to a 169.x), the Airport Utility will no longer 'find' the Express once the Express auto-restarts and the update will fail.  I learned this after spending two hours on the phone with Apple support yesterday - during which they were able to get my first generation Express configured, but, not my 24-hour old second Generation Express, which continues to act only as a paperweight.  Oddly enough, everything works perfectly well if I use only wireless connections to the Extreme - there are no IP problems and everything works correctly.  Unfortunately, I want to use wired connections for all my devices (expresses, Apple TV's) because we stream alot of audio and video.     
    Is my Extreme not working correctly?  Does anyone think it's problematic to have a second router (the Aruba) connected behind the Extreme?  I suppose I could force some components to use only specific IP's, but, that sounds like a pain.  If the Aruba is problematic, I would also consider a second internet connection, or, finding some way to split home IP traffic vs work IP traffic. 
    Thoughts?

    I've been doing some research and it appears the 'self assigned IP' address is a common problem in the Apple support community.  And, for what it's worth, it appears an inability to isolate or accurately troubleshoot the problem - by users or Apple tech support - is a recurring theme.  I totally understand that no two home networks are exactly alike (different ISPs, switches, configurations, etc.), but, after being a die-hard PC user for my entire life I can honestly say I never encountered anything like this while using my PC.  I'm not about to trash my Mac, but, the Apple 'ease of use' selling point is quickly losing it's lustre.
    I got into this mess because I added a GigE switch to my network.  Rather than buy a different switch (a tactic which assumes my problems are being caused by the switch) I'm inclined to buy another Airport Extreme and try daisy-chaining them together to overcome the reason I bought the GigE switch in the first place, which is not enough ethernet ports on the Extreme.  That, or I'll spend a weekend in my attic re-wiring my home network to daisy-chain my two Express devices together instead of requiring individual connections to my router.  My experience with Apple hardware thus far is that it prefers to 'play nice' with other Apple hardware over non-Apple hardware.  It could be $100 error on my end (or, a weekend of not doing yardwork), but, I think it's the best shot.  Other possible fixes, including manually assigned IP-addresses, put too much emphasis on software and network configuration - which (by my non-scentific analysis), are two areas even harder to troubleshoot. 
    I'll let you know how it goes. 
    Mh
    Post Script - Dear Apple: please find a way to significantly increase the number of ethernet ports on your Airport Extreme Router.  Thank you. 

  • IMac on Netgear X104 and Airport Extreme intermittently loses IP address

    We have a Netgear X104 plugged into an Airport Extreme Base Station.
    Another X104 (which carries network information through the household electrical wiring) is plugged in for a networked iMac with OS X v 10.5.4.
    The network works flawlessly, but every few days, the iMac loses its IP address. All lights are working properly on the X104, indicating that it is seeing the network.
    The only workaround on the iMac is to go to: System Preferences/Network/Advanced and click RENEW DHCP LEASE. The iMac then gets reassigned a new IP, such as 10.0.0.200 by the Airport Extreme.
    The Airport Extreme, settings are as follows.
    Wireless Mode: Create a wireless network
    Wireless security: WPA/WPA2 Personal
    Connect using: Ethernet
    Configure IPv4: Using DHCP
    IP Address: Provided automatically
    Powering off and on the Airport Extreme and the Cable Modem have not fixed this recurrent problem.

    Hi,
    http://osxdaily.com/2009/12/22/mac-wireless-problems-guide-to-troubleshooting-ai rport-wireless-problems-on-your-mac/
    Hope it helps.
    Cheers.

  • AirPort Extreme Not Connected to Internet

    I have been trying all day to connect a new AirPort Extreme base station. The base station appears to be configured correctly, in that the green indicator light burns solid. But I can't connect to the Comcast Internet: I get an error message that the Ethernet cable is unplugged (it isn't). I've powered down, reset, and restarted the cable modem; and have disconnected and reconnected the power supply to the base station numerous times, but still no Internet. When I reattach the Ethernet cable directly to the Mac everything is fine. I can't tell whether or not the base station is pulling the IP address, etc., from Comcast. Anyway, I'm getting nowhere with this, and would greatly appreciate input from this discussion group. Thanks very much.

    Hello driverdude. Welcome to the Apple Discussions!
    Although I know you tried multiple resets, please try the following to see if this will get you Internet connectivity with your Comcast modem ...
    Try the following, in order, checking for Internet access after each step, or until resolved:
    1. If the modem has a reset switch, use it to reset the modem. Wait at least 5-10 minutes for the modem to initialize.
    2. Remove power from the modem. If it has a backup battery, remove this as well. Wait 5-10 minutes. Replace the battery, and add power back to the modem.
    3. Perform a complete power recycle of your network components as follows:
    Modem/Router Power Recycling - Quick
    o Power-off the modem, AEBSn, & computer(s); Wait at least 5 minutes.
    o Power-on the modem; Wait at least 5 minutes.
    o Power-on the AEBSn; Wait at least 5 minutes.
    o Power-on the computer(s)
    If this fails to get the modem to "recognize" the Internet router, then try the "Full" version.
    Modem/Router Power ReCycling - Full
    o Power-off the modem, AEBSn, & computer(s). (Wait at least 30 minutes. If possible, leave the modem off overnight.)
    o Power-on the modem; Wait at least 15 minutes.
    o Power-on the AEBSn; Wait at least 5 minutes.
    o Power-on the computer(s)
    4. Contact your ISP to have them perform a "modem reset."

Maybe you are looking for