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)

Similar Messages

AirPort does not have an IP address and cannot connect to the Internet.

Wi Fi problems
I have recently changed from a old netgear router to using a vigor 120 modem with airport extreme
Internet connection is established but my airport express reports "AirPort does not have an IP address and cannot connect to the Internet." although status is ON and the correct wifi address appears.
My iPhone also identifies the correct network but cannot connect
Any suggestions?

I don't have any phones, so not aware of the options, but on a Mac to fix this problem it'd likely be...
Instead of joining it from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed. Before I went through network diagnostics and all of that stuff in system preferences, and then I tried the "Join Other Network" method, and now it works like a dream.
https://discussions.apple.com/message/17028445#17028445
Or...
Go to System Preferences
Click Network
Highlight AirPort and click Configure...
Choose “By default, join: Preferred networks”
Select your access point and Remove your access point with the minus button.
Launch your keychain access in Utilities and delete your access point keychain entry.
Reboot

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.

Clients not receiving DHCP IP address from HREAP centrally Switched Guest SSID

Hi All,
I am facing a problem in a newly deployed branch site where the Clients are not receiving DHCP IP address from a centrally switched Guest SSID. I see the client status is associated but the policy manager state is in DHCP_REQD.
The dhcp pool is configured on the controller itself. The local guest clients are able to get DHCP and all works fine, the issue is only with the clients in the remote site. The Hreap APs are in connected mode. Could you please suggest what could be the problem. Below is the out of the debug client.
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Adding mobile on LWAPP AP 3c:ce:73:6d:37:00(1)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Reassociation received from mobile on AP 3c:ce:73:6d:37:00
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'Guest-ACL' (ACL ID 0) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying site-specific IPv6 override for station 10:40:f3:91:7e:24 - vapId 17, site 'APG-MONZA', interface 'vlan_81'
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying IPv6 Interface Policy for station 10:40:f3:91:7e:24 - vlan 81, interface id 13, interface 'vlan_81'
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 Applying site-specific override for station 10:40:f3:91:7e:24 - vapId 17, site 'APG-MONZA', interface 'vlan_81'
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1393)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 STA - rates (8): 140 18 152 36 176 72 96 108 0 0 0 0 0 0 0 0
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Initializing policy
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state AUTHCHECK (2)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 AUTHCHECK (2) Change state to L2AUTHCOMPLETE (4) last state L2AUTHCOMPLETE (4)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 3c:ce:73:6d:37:00 vapId 17 apVapId 1
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 0.0.0.0 L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last state DHCP_REQD (7)
*apfMsConnTask_3: May 24 13:26:49.372: 10:40:f3:91:7e:24 apfMsAssoStateInc
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 apfPemAddUser2 (apf_policy.c:222) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Idle to Associated
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station: (callerId: 49) in 28800 seconds
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 Sending Assoc Response to station on BSSID 3c:ce:73:6d:37:00 (status 0) ApVapId 1 Slot 1
*apfMsConnTask_3: May 24 13:26:49.373: 10:40:f3:91:7e:24 apfProcessAssocReq (apf_80211.c:4672) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Associated to Associated
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) State Update from Mobility-Incomplete to Mobility-Complete, mobility role=Local, client state=APF_MS_STATE_ASSOCIATED
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) pemAdvanceState2 4183, Adding TMP rule
*apfReceiveTask: May 24 11:35:53.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Adding Fast Path rule
type = Airespace AP - Learn IP address
on AP 3c:ce:73:6d:37:00, slot 1, interface = 13, QOS = 3
ACL Id = 255, Jumbo F
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 7006 IPv6 Vlan = 81, IPv6 intf id = 13
*apfReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (ACL ID 255)
*pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
*pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 Sent an XID frame
*apfMsConnTask_3: May 24 13:26:49.401: 10:40:f3:91:7e:24 Updating AID for REAP AP Client 3c:ce:73:6d:37:00 - AID ===> 1
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) DHCP Policy timeout
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station: (callerId: 12) in 10 seconds
*osapiBsnTimer: May 24 13:28:59.315: 10:40:f3:91:7e:24 apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: May 24 13:28:59.315: 10:40:f3:91:7e:24 apfMsExpireMobileStation (apf_ms.c:4897) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Associated to Disassociated
*apfReceiveTask: May 24 13:28:59.315: 10:40:f3:91:7e:24 Scheduling deletion of Mobile Station: (callerId: 45) in 10 seconds
*osapiBsnTimer: May 24 13:29:09.315: 10:40:f3:91:7e:24 apfMsExpireCallback (apf_ms.c:599) Expiring Mobile!
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 Sent Deauthenticate to mobile on BSSID 3c:ce:73:6d:37:00 slot 1(caller apf_ms.c:4981)
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 apfMsAssoStateDec
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 apfMsExpireMobileStation (apf_ms.c:5018) Changing state for mobile 10:40:f3:91:7e:24 on AP 3c:ce:73:6d:37:00 from Disassociated to Idle
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Deleted mobile LWAPP rule on AP [3c:ce:73:6d:37:00]
*apfReceiveTask: May 24 13:29:09.316: 10:40:f3:91:7e:24 Deleting mobile on AP 3c:ce:73:6d:37:00(1)
*pemReceiveTask: May 24 13:29:09.317: 10:40:f3:91:7e:24 0.0.0.0 Removed NPU entry.

#does the client at the remote site roams between AP that connects to different WLC?
#type 9 is not good.
*pemReceiveTask: May 24 13:26:49.373: 10:40:f3:91:7e:24 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
#Does your dhcp server getting hits.
#Also, get debug dhcp message & packet.
#Dhcp server is not responding.
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) DHCP Policy timeout
*apfReceiveTask: May 24 13:28:49.315: 10:40:f3:91:7e:24 0.0.0.0 DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.

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.

Station is not receiving an IP address from DHCP

Hello guys,
I have an ASA 5505 functioning as a router to connect to the Internet. Also, it is my DHCP server for my clients, and APs. When I connect my laptop to the ASA, I get an IP address and able to configure my WLC. The APs also receives an IP address from the ASA. However, when I connect to the AP wirelessly as a wireless client, my laptop is not receiving an IP address from the DHCP which is my ASA.
Here is my topology:
[3602i]--------[ASA5505]--------[WLC2504]
Here is my ASA config for my clients:
interface Vlan12
description *** DEFAULT GATEWAY FOR Wi-Fi GUESTS
nameif GUESTS-if
security-level 100
ip address 10.2.12.1 255.255.255.0
dhcpd address 10.2.12.100-10.2.12.131 GUESTS-if
dhcpd dns 208.67.222.222 208.67.220.220 interface GUESTS-if
dhcpd lease 1048575 interface GUESTS-if
dhcpd option 3 ip 10.2.12.1 interface GUESTS-if
dhcpd enable GUESTS-if
Here is the WLC interface config:

Hello jsnyder81,
I have another question. This is still related to the same network.
I am able to connect to the wireless network now, and receiving IP address from the ASA 5505; however, I can only ping my wireless gateway. I also don't have access to the Internet.
When I hard wired my laptop to the ASA's switch port, I am able to browse the Internet, but not via WiFi.
Here is the routing table that I have on the ASA:
Gateway of last resort is 192.168.1.1 to network 0.0.0.0
C    10.2.8.0 255.255.255.0 is directly connected, PRINTERS-if
C    10.2.9.0 255.255.255.0 is directly connected, FIOS-if
C    10.2.10.0 255.255.255.0 is directly connected, IP-CAMERAS-if
C    10.2.11.0 255.255.255.0 is directly connected, WiFi-USERS-if
C    10.2.12.0 255.255.255.0 is directly connected, GUESTS-if
C    10.2.13.0 255.255.255.0 is directly connected, WIRED-if
C    10.2.3.0 255.255.255.0 is directly connected, EXSi-if
C    10.2.4.0 255.255.255.0 is directly connected, AD/NPS/CA-if
C    10.2.5.0 255.255.255.0 is directly connected, inside
C    10.2.6.0 255.255.255.0 is directly connected, WLC-if
C    10.2.7.0 255.255.255.0 is directly connected, AP-if
C    10.2.20.0 255.255.255.0 is directly connected, WIRELESS-PILOT-if
C    10.2.21.0 255.255.255.0 is directly connected, WIRED-PILOT-if
C    10.2.22.0 255.255.255.0 is directly connected, SERVERS-PILOT-if
C    192.168.1.0 255.255.255.0 is directly connected, outside
d*   0.0.0.0 0.0.0.0 [1/0] via 192.168.1.1, outside
I also have this command:
same-security-traffic permit inter-interface

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!

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.

My airport Extreme just stopped assigning IP addresses to wired devices

I have an fairly large home network that is run by an Airport Extreme.
- Comcast Cable Modem for 3 public (not static) IP addresses
- small switch to be able to obtain three addresses
- Apple Airport Extreme connected to the switch and it receives an IP address and internet connectivity from Comcast
- Airport Extreme connected to a 16 port Cisco switch to handle the wired connections in the house. I have 54 ports of which 9 are currently in use.
all wired devices connected through the wall and a patch panel to the Cisco switch.
The issue is that after working flawlessly for about a month (just moved into this house) it stopped today. any device going through the hardwired Cisco Switch is no longer getting an IP address from the Airport Extreme.
I replaced the switch with a second one to see if that was the failure and it is not.
I unplugged the Cisco Switch from the Airport Extreme and plugged devices directly into the Airport Extreme 1 by 1 and they were able to obtain IP addresses.
I need more than the three ports available on the Airport extreme.
What changed and what do I do?

I unplugged the Cisco Switch from the Airport Extreme and plugged devices directly into the Airport Extreme 1 by 1 and they were able to obtain IP addresses.
This tells you that the AirPort Extreme is working correctly and the issue....whatever it is....is appearing after the AirPort Extreme on the network.
A few thoughts:
You have tested the ports on the AirPort Extreme and they are working, so the next step would be to disconnect the Ethernet cable that runs from the AirPort Extreme to the switch at the switch, and then connect a laptop to the Ethernet cable to check to make sure that you are getting a good IP address that way.
If you cannot, then you have a bad Ethernet cable between the AirPort Extreme and switch that will need to be replaced.
If the laptop is getting a good IP address when you run this "test", then you know that the AirPort Extreme and Ethernet cable are working correctly and the troubleshooting focus must now move to the switch.
Check to make sure that you have an unmanaged switch. Or, if it is managed design, that it has been configured to operate as an unmanaged switch.
Next, connect the Ethernet cable from the AirPort Extreme to the switch and disconnect all of the other Ethernet cables that are connected to the switch and test each port one by one with your laptop and a spare Ethernet cable to make sure that each port is working correctly.
If you cannot get a good IP address on your first test with the laptop connected to the switch, then you know that you have a misconfigured or defective switch.
If the switch checks out OK when you test each port, then the next step is to connect one of the Ethernet cables that runs to another area, and connect your laptop to the Ethernet cable to make sure that the cable is working correctly. Continue to test each Ethernet cable the same way.
About 95% of the time in issues like you are having, the problem is bad wiring somewhere on the network, even though the "tech" said that he tested everything. The trick is to find it....when there are no shortuts.

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

Airport Extreme not working properly after upgrading from Tiger to Leopard

I've been using the Airport on a home network to share internet between a Mac & PC via ethernet. I don't use wireless. My internet provider is comcast via cable modem. During the Leopard install the Airport asked for a firmware update to 7.3.2. So I installed the update during the transition. I lost internet connection. I resolved this by calling comcast- who reset my modem. This got the Mac connected again but not the PC. When I attempt to share the connection via the Airport utility, I loose internet again.
The error message is:
Your Apple wireless device does not have a valid IP address. Make sure your Apple wireless device is connected to your broadband modem or local network, verify your settings, and try again. If you still can't connect, contact your internet provider
What is a valid IP address? How can I determine what it is?
Also, I cannot see the PC on the network.
I've attempted going back to the previous firmware (7.3.1) but it didn't solve the problem
I'm connected to the internet now by taking the airport out of the loop and going directly into the Mac from the Modem.
Thanks Steve

Moved to AirPort Extreme (802.11n) forum

Airport Extreme not connecting to Internet

Here's my setup:
imac with Airport Extreme in home office
Airport Express hooked up to home ethernet network in family room to stream itunes (or connect laptop at other end of house)
Just got home and tried connecting my work powerbook to the Airport Extreme network, and suddenly it does not work. Basically times out after trying to connect to internet, even though i get full bars signal-wise, and network diagnostic says i should be connected. I can connect to the Airport Express network in the family room just fine. And my internet connection is working fine over the ethernet network.
Has my Airport Extreme bitten the dust? It's showing full bars, but my Canon i960 stopped printing from it the other day. I thought that was just a problem with the printer, but maybe the problem is my base station?
ps running all the lastest software...
Any suggestions? (Tried restarting cable modem, Airport Extreme, computer, etc. No go.
Thanks for any help.

Hmmm... That's odd that you can't administer the Airport Base Station
from the portable computer (the one you'd later use wirelessly) and
essentially check the thing out thoroughly; see if the firmware and
other things are up to par and the settings are chosen properly.
You'd use the ethernet cable in either case, to access the Base from
the portable or the tower; when you are doing an occasional test and
reset of the Base station. Sometimes, details make a difference.
Another factor may be in how you have the Base station set up to
share internet among computers; the ethernet-only G4 that sees
the through-ported IP dataflow should also be able to administer
the base station. But it may require the Portable, hardwired, to
check the settings and get it to work. I had a similar issue once
with my primary AEBS and had been administering it via a non-
wi-fi B&W G3 tower on ethernet cable; the other computers were
all wi-fi. That worked out great. Currently, I alternately run the iMac
G4 via wireless, and sometimes by wire. I have both set up & ready
and only need to go into the control panel/system preferences; to
make a change. Sometimes the wireless telephone (2.4GHz) is too
close and kills the wireless to my desktop Mac; so I change to wire.
What kinds of addresses are you seeing in your set-up for IP
to each computer? Unless you do actual file-sharing between
them, you can set that up so each computer has a full ISP
address; not those 10.0... or 193.00. or other networking ones.
Sharing a printer is another matter, if you run your AEBS as
though it were a wireless router only, it would be trial & error;
if set up to be wireless printing you'd probably need to get a
wireless USB module to see if that'd work for the G4.
The deal you are talking about, above, is how the device
works. Your G4 tower sees the internet via the through-port
in the AEBS router; it is a wired & wireless router, plus it
can give you wireless printing because it has a USB port.
But only when it is set up correctly. That is easier to do
than it is to write about. When mine fails, I look into it;
and as I suggested in other posts, it will just work later.
PS: In your Portable computer's System Preferences/
Network control pane, see what order it shows the
items or pathways available to connect to the net are
in; if the wireless airport isn't at the top of the list &
is not activated, drag it there. The check-boxes by
each option of course, need to be activated as needed.
When you see a signal, it should be able to find the IP
if the other settings were correct. Sometimes, the basic
defaults work OK right out of the box.
In the portable's System Profiler, you could also see if
there is an assigned IP address given to the computer.
At that point, there should be no reason for it to not work.
Like I said, it is harder to write or talk about it; easier to
see the things and work the strings in the right order!

My 2 airport extremes not extending far enough

I am trying to get my airports to extend far enough to hit my studio (garage) from house and its not quite enough. The garage is a recording studio and the walls are double thickness of a regular garage which makes it difficult.
I have a Mac Pro hard wired ethernet from the house . Is there a way to connect airport from the Mac Pro?
Airports are configured to extend signal. As soon as I walk in garage my signal drops on my iphone, is there a proper position for the airports to extend the max range?
Thanks!

I have a Mac Pro hard wired ethernet from the house . Is there a way to connect airport from the Mac Pro?
Can you consider connecting the Ethernet cable from the "main" AirPort Extreme to the AirPort Extreme in the garage? This would provide you with a far stronger signal that trying to "extend" using wireless only.
Your Mac could then connect to the garage AirPort Extreme using either a wired Ethernet connection or using wireless.
is there a proper position for the airports to extend the max range?
Wireless is always quite unpredictable if you are trying to "extend" using wireless only, but the basic rule would be that the "extending" AirPort be located about 1/2 to 2/3 of the distance from the "main" router to the area that needs more wireless coverage.
It's all a matter of compromises. If the extending AirPort is located too far from the main Airport, it receives a poor signal and that is what gets extended. If the extending AirPort is located too close to the main AirPort, it gets a strong signal to "extend", but it may not reach the area that you need.
Add to that the problem that every wall, celing, or piece of furniture in the signal path absorbs a significant amount of the wireless signal....and an outside wall typically absorbs about 3 times more than an interior wall. So, the end result is almost always a product of experimentation rather than firm rules.
The bottom line.....if it is possible to connect the AirPorts using a wired Ethernet cable, that is by far the best choice in terms of performance. The "extending" AirPort will need to reset back to default settings, then reconfigured again if you decide that you want to do try this.

Airport Express not receiving DHCP from Ethernet

Hello All,
Recently, one of my Airport Express 802.11n access points started using the self assigned IP address 169.254.238.166. While troubleshooting, I have found that this device will receive an IPv4 address when I connect it's Ethernet interface to my D-Link DG-S1248T, but not when I connect it to my Linksys SE2500 (the one it was connected to for over a year before starting this behavior). Ordinarily, I would suspect that something is preventing the Linksys from switching DHCP packets correctly to the Airport Express, but I can assure you the Linksys is sending DHCP packets because I am starting this thread from a Mac Pro connected to that Linksys, with a valid IPv4 address, and wireshark is showing bootps request and reply. I'm using bridged mode on the Airport Express, because I already have a gateway as my DHCP server with NAT, and created a wireless network with firmware version 7.5.2. I even setup another Airport Express 802.11n right next to the faulty one, same config (except the ID), same switch, and it works fine. I also swapped Ethernet patch cables on the Airport Express 802.11n Ethernet interfaces. The green LED access point went back to green when the cables were swapped, while the blinking amber access point stayed blinking amber. Therefore I believe the problem is localized on the faulty Aiport Express 802.11n. Has anyone else seen this fault? What is the root cause, and how did you repair the issue?
Thanks!

The Airport Express was functioning normally as recently as last Thursday, when I unplugged it to move. I took care in transporting it so there was definitely no chance of physical damage.
You mean that it was functioning normally when it was connected to a cable modem last Thursday. Everything has changed. Unfortunately, the Express is known to sometimes have problems after it has been plugged in for a long time, is unplugged, and then started up again. On average, I lose an AirPort Express about once a year this way.
Power up the Express for a few moments
Hold in the reset button for 8-10 seconds and release
Allow a full minute for the Express to restart to a slow, blinking amber light
Connect the Ethernet cable from wall jack to the WAN "O" port on the Express
On the Mac, open Macintosh HD > Applications > Utilities > AirPort Utilities
Click on Other WiFi Devices
Click on AirPort Express
The utility will suggest a setup that looks similar to this, except you will see a different picture of the AirPort Express
Network Name = Name that you want to call your wireless network. Keep it very simple.
Base Statation = Name that you want to call the AirPort Express device
Password = Password that will be used for both the wireless and device
Verify Password
Click Next
The utility will setup everything for you. When you see the message of Setup Complete, click Done
Check the network

New Airport Extreme not working with my Quad Macpro

Hi all-
My Linksys 902.11b router finally died and our household is now completely Mac-based (all with Airport Extreme cards), so I decided to take the plunge and get an Airport Extreme.
2 of the machines on my home's network are doing fine with the router and are getting good speeds - iMac Dual 2.4 (10.5.1) - Both the wired and wireless connections are solid with this machine / Macbook Dual 2.0 (10.5.1) - Both the wired and wireless connections are solid with this machine as well.
I have a Macpro Quad 2.66 machine running 10.4.11. I cannot upgrade to 10.5 yet on this machine since it's being used in my recording studio business and there are known issues with some of my apps and 10.5 at the moment.
The Quad can see the network and has seemingly strong signal from the Airport Extreme BS, but DHCP reception is inconsistent (the machine often eds up using a self-assigned IP for some reason) and IP connectivity in general is inconsistent, even when an appropriate static LAN IP is manually setup. I can often get to a few webpages while using a manually config'd IP, but only with very slow DL speeds and then the connection quickly disappears and drops out entirely.
The AExtreme is setup like this: DSL Modem-->Airport Extreme (config'd with a static IP from my ISP) -->DHCP broadcast dummy IP's to my network. Currently I've not setup any security since I'm in the process of troubleshooting and I don't want to further complicate the situation. Radio-mode on the AExtreme is set to 802.11n (b/g compatible)/Channel 1. I've tried numerous config setups on the AExtreme, but none have helped the situation.
I've also disabled IPv6 on all clients per some reading on the forums of possible issues.
Anyone know what the problem might be? Is it perhaps an issue because the Macpro's using 10.4.11?
FYI, I've also also got an extra Airport Express around that's not being used that could be used as a repeater/wired connection downstairs if broadcast strength is the issue, which seems somewhat unlikely to me. I'm not sure how to config the AExpress to work in this capacity though, so if anyone could point me to a tutorial I'd appreciate it very much.
Thanks in advance.
Lee

I just did some more testing using an app mentioned here on the forums, iStumbler. The app offered these details:
- Signal Strength is between 45%-56%
- Noise is between 24%-41%
- Freq = 2412
- No websites load despite it's seeing the router and saying we've joined it.
I also did a screen capture of the iStumbler's screen in case that's helpful. There were several bits of info I wasn't sure about.
Here's the screen grab: http://www.pbase.com/infiniteposse/image/91793322/original
Thanks again...

Airport extreme not receiving an ip address

Similar Messages

Maybe you are looking for