?? New AExtremeBS- MInis self assign an IP instead of picking up DHCP addy

Hello and help! I have a new Airport Extreme Base Station that I'm deploying in our warehouse that will host 3 minis and 3 MacBooks. It's set up to serve a DHCP range out of our LAN's subnet - .126 through .150. I'm using WPA Personal with a 13 character password. It's in "automatic" mode for channel and speed.
The clients are setup with the network in the "preferred" pane of network preferences, password added to the keychain, and set to "automatic"
The Macbooks quite happily join the network, get a dhcp addy, and surf on out to the internet and internally to other LAN computers and servers.
The minis, however, APPEAR to join up (the airport signal bars go to full power) - however, when going to browse the local net or the internet, there is no connection. Looking at the network pref pane gives the message that "airport has a self assigned IP address and may not be able to connect to the internet". No duh! When I look at the TCP/IP pane, I see that they have indeed given themselves a rendezvous addy and subnet.
Now, I assumed that - perhaps - they had timed out in trying to get the DHCP addy and had fallen back on rendevous. However, I moved the base station _directly on top_ of one of the minis, same problem.
I then set one to an addy within the DHCP range (.149), gave it the correct subnet and gateway, Locked the network pane, and still got no love.
Even stranger, after rebooting (with a locked network pane) still no love, and STRANGER still, when checking the network pane, it was unlocked. ???
The minis in question are: one core solo circa April of last year, and two new Core 2 Duos just recently purchased (this March).
I've updated ALL to the latest firmware and 10.4.9 updates that are available to this date (5/2/07). I tried to apply the .n updater to the later models, but the CD doesn't show it as available for install - and I know it's on the disk, as I've applied the update to my Mac Pro, so I'm led to believe that the Core 2 duo minis shipped with the enabler live.
I'm getting ready to punt these frickin machines. Any ideas before I put my spikes on?
Thanks all!
mini core 2 duos and a core solo Mac OS X (10.4.9)

Hello,
Think I'm having the same problem. Got a iMacG5 and old PB. Both working fine till 4 days ago. I connect to a wireless network shared between 3 flats. Don't remember changing anything on settings tec.. but now the iMac looses internet connection every 10minutes or so and the PB can't connect at all. Both have full bars on the wireless signal indicator.However the PB Airport info in Network settings show's "Airport connected to 'wireless network' but has a self-assigned ISP and may not be able to connect to the internet". The iMac doesn't seem to have anything odd. The other 2 flats (with PC's) have no server problems and are working fine.
Any ideas anyone?

Similar Messages

My new iPad mini is connected to a Logitech keyboard but can't seem to get it to type instead of the touch screen version on the iPad - any hints?

My new iPad mini is connected to a Logitech keyboard but can't seem to get it to type instead of the touch screen version on the iPad - any hints?
Michael

Is this a Bluetooth keyboard?
Have you turned on Bluetooth in iPad's Settings app?

Bought new ipad mini. When usingiMessage it shows my daughters contact instead of mine.

Bought new ipad mini. When usingiMessage it shows my daughters contact instead of mine.

That's because you are using her Apple ID or sharing an Apple ID on your iPad.
Do you have your own Apple ID? Do you share an ID? If so, is the ID her Apple ID?

By mistake i setup my new iPad mini with my iPad instead of a new iPad what can i do?

By mistake i setup my new iPad mini with my iPad instead of a new iPad what can i do?
I use them for diferentes Things what can i do to reverse my mistake???

Go into the settings, reset, erase all content and settings. Which puts it back to 'out of box' state, then go back in and go through your set up but this time choose the 'set up as new' option.

Self-assigned IP and renewing the DHCP doesn't give me a new IP no internet

When I went to connect to my wireless I wasn't able to, I ran a network diognostic and it said it couldnt fix the problem; normaly it works without a problem. I turned off my wireless box (netgear)and back on and still couldn't connect, my iPhone can and other pc's can. I started to look through the network preferences and saw it had a self-assigned IP. I took it to an I.T. technician at my college who also has the same macbook. He tryed renewing the DHCP but the same IP and subnet mask came up. I had recently updated the airport utility and thought it might be that but the technician had also and didnt seem to have the proble. Next we connected it by cable to the modem but that to had a self-assigned IP. We couldn't figure out what the problem is and he said all the settings I had were correct apart from the DHCP wouldn't renew.
Any help would be great, Thanks
Message was edited by: Spyonicle

I can also state the exact same issue with my MacBook. I am a consultant working for a large business customer, who has well-established hardwire and wireless networks. I have been using the company's WiFi guest network since Nov 2008, and starting the morning of June 5 I can no longer connect. BTW, my iPhone and every other Windows machine around here can.
Because I am able to connect to every Starbucks, library, home, and every other WiFi network that I try, the company's network support folks and I thought that my issue was related to a known DHCP server issue in the company's network configuration. Last night, this DHCP server issue was resolved, but my Macbook still cannot connect.
Do we have a known OS issue that affected everyone on June 5? I notice that there are no responses to this thread. In my past inquiries, this is usually the case when nobody responds. What is the next step toward resolution? Wait until September in hopes that OS 10.6 works better?
Message was edited by: tomfrenock

HT201269 I set up my new ipad mini as a new user instead of as my ipad2 identity. Is there anyway I can change this?

I set up my ipad mini as new and now I am wondering how to get my stuff from my ipad2 identity to my new ipad mini identity. Is there a way or do I need to swipe it clean and start over? Thanks.

You can resync stuff. But if you want your mini to be a near clone of your 2, and if you have a good backup, I'd start over.

Self-assigned IP (DHCP is not getting correct IP address)

I just moved and got my internet connection not long ago. When the installation people were there, they tested the internet connection by plugging the ethernet cable directly to my girlfriend's macbook (one of those new white macbooks). It worked pretty well. I set the router up then, and it worked fine.
The problem is: I can connect wirelessly to the LAN created by the router (and internet works), but if I try to plug the ethernet cable directly from the modem to my macbook, it will self-assign an IP address and I can't get a connection. This problem has never happened before, and it happens just at home (no matter how many times I try to reboot the modem). The funny thing about it is that it still works if I plug the ethernet cable directly to my girlfriend's macbook instead of mine.
Can anybody give me a suggestion? Just to make sure: my mac (as well as my girlfriend's) runs snow leopard.
Thanks in advance,
Davi

There's no common issue.
All a self-assigned IP address means is that DHCP did not assign you an IP address.
This can occur for a variety reasons, from the DHCP server only issuing one address per network (many DSL modems do this) to running out of addresses (many cable modems will issue up to five but no more, and many routers will not issue more than ten.)
The brute force fix attempt is, as mentioned above, to power off your Macs and other machines, power off the router, then power off the DSL or cable modem. Wait a minute, then power them up in reverse order (DSL/Cable modem, then a minute later the router, then a minute later your PCs/Macs.)

Self Assigned IP address – can't figure this out. Frustrated.

This is a long post but bear with me. It proposes a challenge for the mac connoisseur. Who knows? Might be fun?
OK, here goes:
Please help. I have been trying to fix this for about 7 months. I first noticed this issue when I started traveling around the country, from hotel to hotel. While others (PC's and Mac's) had no trouble connecting to the free wifi at these hotels, I did. I kept getting "self-assigned i.p."
This was extremely frustrating. I often had to call up the i.t. guys and ask them to help me manually put in ip address, subnet mask, router (gateway), and dns. This worked much of the time but not always.
Let me also say that, sometimes it worked perfectly! I'd say about 25% of the time (at these hotels) my internet worked perfectly – just connected immediately. The other 75... "self-assigned i.p."
I just spoke to the mac "geniuses" and they told me it's not an issue with my computer at all (either hardware or software). Are you kidding me?!?! How can they explain everyone else's internet working except mine. And I'm talking like 100 or more different hotels in a 4 month period. They were trying to tell me that it was just a coincidence every time! "You'd be surprised" one guy said. Hahaha. They said that the routers aren't accepting my computer's whatever. OK, well WHY?! The router works for everyone but me. It's something wrong with my computer right?! Well no one acknowledged this.
More background info:Just had my airport card and logic board replaced. Computer came back and the sheet said "passed all hardware tests." BUT, none of my issues (I had other ones too involving battery life and not being able to access certain websites) were fixed.
I went to an apple store. They told me to do an erase and reinstall or whatever. So I did that (by dragging and dropping everything I'd saved on an external hard drive using disk utility). By the way, I also upgraded from leopard to snow leopard. So now, if I have the same issues after this I'll know both leopard and snow leopard are screwed up.... right?
OK, so I followed their instructions on deleting and reinstalling to a tee and guess what?! Everything worked! Or so it seemed. Battery fine. Websites now accessible. I figured the airport issue was fixed too. But now that I'm not touring anymore and the airport works in my house, I never encountered any issues. Until now. At my work.
I got a new job and it's one in which I HAVE to have a computer that connects to the internet. So of course, the same issue with self assigned i.p. presents itself. Everyone else in the office has no problem. Including a Mac person that used to work there.
I've been reading some other threads that are just completely confusing me. One of them might be the solution but I thought I'd detail my troubles so that some smart computer person out there can diagnose my specific problem and give me a specific fix.
I noticed that many people believe there was a bug in one of the 10.5 updates. I am pretty quick to install updates (maybe I shouldn't be because I hear that the first updates are often buggy and maybe you should wait for a while). But this problem has continued now with Snow Leopard too so... I don't know. I don't know anything anymore. I have tried everything. And Apple is telling me it's not a problem with my computer. Give me a break.
One more interesting quirk: before doing the erase and reinstall my computer could not find the Apple Store's network. After the erase and reinstall it works. That's why I assumed everything was fine! But no. And now the Mac people are saying there's no problem because they can't see it.
BTW, I have tried all the obvious things. It's not an obvious thing. But I mean, if you think it is... then tell me I guess. But I've been in the advanced tab thousands of times. I feel like I've exhausted everything in there.
Thank you thank you thank you in advance if someone is actually able to solve my issue.

continuation of console log:
Feb 1 13:08:45 localhost kernel[0]: npvhash=4095
Feb 1 13:08:45 localhost kernel[0]: PAE enabled
Feb 1 13:08:45 localhost kernel[0]: 64 bit mode enabled
Feb 1 13:08:45 localhost kernel[0]: Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
Feb 1 13:08:45 localhost kernel[0]: vmpagebootstrap: 507215 free pages and 17073 wired pages
Feb 1 13:08:45 localhost kernel[0]: standard timeslicing quantum is 10000 us
Feb 1 13:08:45 localhost kernel[0]: migtable_maxdispl = 73
Feb 1 13:08:45 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
Feb 1 13:08:45 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for Quarantine
Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for Sandbox
Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Feb 1 13:08:45 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Feb 1 13:08:45 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Feb 1 13:08:45 localhost kernel[0]: MAC Framework successfully initialized
Feb 1 13:08:45 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
Feb 1 13:08:45 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Feb 1 13:08:45 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Feb 1 13:08:45 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)
Feb 1 13:08:45 localhost kernel[0]: rooting via boot-uuid from /chosen: 5924DB5A-4C9F-323F-BC39-2469AEAB4D18
Feb 1 13:08:45 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string> <key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Feb 1 13:08:45 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
Feb 1 13:08:45 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
Feb 1 13:08:45 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe8a7584; max speed s800.
Feb 1 13:08:45 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0 /AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver /IOAHCIBlockStorageDevice/IOBlockStorageDriver/FUJITSU MHW2120BH Media/IOGUIDPartitionScheme/Untitled@2
Feb 1 13:08:45 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Feb 1 13:08:45 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
Feb 1 13:08:45 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
Feb 1 13:08:45 localhost kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0
Feb 1 13:08:45 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
Feb 1 13:08:45 localhost kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
Feb 1 13:08:45 localhost kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RXMAXLE 1024, TXMAXLE 768, STMAXLE 3328
Feb 1 13:08:46 localhost kernel[0]: yukon: Ethernet address 00:1b:63:94:9c:ad
Feb 1 13:08:46 localhost kernel[0]: systemShutdown false
Feb 1 13:08:47 localhost kernel[0]: NVDANV50HAL loaded and registered.
Feb 1 13:08:47 localhost kernel[0]: Previous Shutdown Cause: 5
Feb 1 13:08:47 localhost kernel[0]: Atheros: mac 12.2 phy 8.1 radio 12.0
Feb 1 13:08:47 localhost kernel[0]: DSMOS has arrived
Feb 1 13:08:47 localhost kernel[0]: AirPort_AthrFusion: Ethernet address 00:1e:52:77:13:82
Feb 1 13:08:47 localhost kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
Feb 1 13:08:56 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 1 (Unspecified).
Feb 1 13:09:05 Michael-Pines-MacBook-Pro kernel[0]: Warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.
Feb 1 13:09:13 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 13:09:13 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 13:12:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:15:38 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:15:39 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:18:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:18:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernate image path: /var/vm/sleepimage
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: sizeof(IOHibernateImageHeader) == 512
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: Opened file /var/vm/sleepimage, size 2147483648, partition base 0xc805000, maxio 400000
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernate image major 14, minor 2, blocksize 512, pollers 5
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 7 (Frame received from nonassociated STA).
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernateallocpages flags 00000000, gobbling 0 pages
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 7 (Frame received from nonassociated STA).
Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: System SafeSleep
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall start
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall time: 114 ms
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: pages 274489, wire 35250, act 50684, inact 887, spec 62, zf 137, throt 0, could discard act 24613 inact 28670 purgeable 6142 spec 128044
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall found pageCount 87020
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: IOHibernatePollerOpen, mlget_interruptsenabled 0
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: IOHibernatePollerOpen(0)
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: writing 86158 pages
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: image1Size 73471488
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: PMStats: Hibernate write took 4108 ms
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: all time: 4108 ms, comp time: 592 ms, deco time: 0 ms,
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: image 166148608, uncompressed 353234944 (86239), compressed 162715248 (46%), sum1 dc78ee00, sum2 4fe372a2
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatewriteimage done(0)
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: sleep
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: Wake reason = UHC3
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: System Wake
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: Previous Sleep Cause: 0
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: USB (UHCI)ort 2 on bus 0x5d has remote wakeup from some device
Feb 1 13:41:08 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 13:41:08 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 13:41:09 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:50:04 Michael-Pines-MacBook-Pro kernel[0]: IOHIDSystem::relativePointerEventGated: VBL too high (33307137), capping to 20000000
Feb 1 13:55:23 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:55:23 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:59:32 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:59:32 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: systemShutdown true
Feb 1 15:24:13: --- last message repeated 1 time ---
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext loading now disabled.
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext unloading now disabled.
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext autounloading now disabled.
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kernel requests now disabled.
Feb 1 15:24:32 localhost kernel[0]: npvhash=4095
Feb 1 15:24:32 localhost kernel[0]: PAE enabled
Feb 1 15:24:32 localhost kernel[0]: 64 bit mode enabled
Feb 1 15:24:32 localhost kernel[0]: Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
Feb 1 15:24:32 localhost kernel[0]: vmpagebootstrap: 507215 free pages and 17073 wired pages
Feb 1 15:24:32 localhost kernel[0]: standard timeslicing quantum is 10000 us
Feb 1 15:24:32 localhost kernel[0]: migtable_maxdispl = 73
Feb 1 15:24:32 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
Feb 1 15:24:32 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for Quarantine
Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for Sandbox
Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Feb 1 15:24:32 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Feb 1 15:24:32 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Feb 1 15:24:32 localhost kernel[0]: MAC Framework successfully initialized
Feb 1 15:24:32 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
Feb 1 15:24:32 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Feb 1 15:24:32 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Feb 1 15:24:32 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)
Feb 1 15:24:32 localhost kernel[0]: rooting via boot-uuid from /chosen: 5924DB5A-4C9F-323F-BC39-2469AEAB4D18
Feb 1 15:24:32 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key> <string ID="1">IOResources</string><key>IOResourceMatch</key> <string ID="2">boot-uuid-media</string></dict>
Feb 1 15:24:32 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
Feb 1 15:24:32 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
Feb 1 15:24:32 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe8a7584; max speed s800.
Feb 1 15:24:32 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PR T0@0 /IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriv er /FUJITSU MHW2120BH Media/IOGUIDPartitionScheme/Untitled@2
Feb 1 15:24:32 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Feb 1 15:24:32 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
Feb 1 15:24:32 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
Feb 1 15:24:32 localhost kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0
Feb 1 15:24:32 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
Feb 1 15:24:32 localhost kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
Feb 1 15:24:32 localhost kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RXMAXLE 1024, TXMAXLE 768, STMAXLE 3328
Feb 1 15:24:33 localhost kernel[0]: yukon: Ethernet address 00:1b:63:94:9c:ad
Feb 1 15:24:33 localhost kernel[0]: systemShutdown false
Feb 1 15:24:44 localhost kernel[0]: Previous Shutdown Cause: 5
Feb 1 15:24:44 localhost kernel[0]: Atheros: mac 12.2 phy 8.1 radio 12.0
Feb 1 15:24:44 localhost kernel[0]: NVDANV50HAL loaded and registered.
Feb 1 15:24:44 localhost kernel[0]: DSMOS has arrived
Feb 1 15:24:44 Michael-Pines-MacBook-Pro kernel[0]: AirPort_AthrFusion: Ethernet address 00:1e:52:77:13:82
Feb 1 15:24:44 Michael-Pines-MacBook-Pro kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 1 (Unspecified).
Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 15:24:51 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 15:24:52 Michael-Pines-MacBook-Pro kernel[0]: Warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.
Feb 1 15:25:35 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

DHCP & self-assigned IP problem-Airport doesn't work

I'm not really a technical type, but I'm pretty quick to pick things up and several weeks of trying to deal with this issue has made me pretty knowledgeable about things related to it specifically.
Background:
I have a month-old Macbook Pro that runs Snow Leopard and is up to date on all its software stuff. On our home network we have another pretty new Macbook Pro running 10.5.9 and a fairly old Macbook also running 10.5.9.
We have a Linksys WRT54G wireless router. Our network uses a 40-bit Hex WEP password.
Problem(s):
When I try to connect to our wireless network, Network preferences tells me that it cannot connect because of a self-assigned IP address. Sure enough, the IP address DHCP comes up with is of the 64.XX.XX.XX variety. Google's revealed that this is a common problem for all recent versions of OSX, back to at least Tiger.
The "subnet mask" it comes up with is 255.255.0.0, which is different from the settings on our other (working) computers, which is 255.255.255.0. I'm not sure what this means, or whether it's significant. Renewing the DHCP lease either comes up with the same 64.XX.XX.XX type or, sometimes, it comes up with no IP settings at all. The most frustrating thing about this is that if I chose "DHCP with manual address" and type in any in our set that I've confirmed isn't in use and hit "apply", as soon as I go back to the panel it has reverted to the 64.XX.XX.XX type.
I've also tried manually entering the router/subnet mask/IP data, as well as the DNS numbers, and that leads to the Network Settings connectivity dot thing being green, but the internet still doesn't work. In those cases, diagnostics claims that everything is fine up to and including the ISP, but that it's unable to connect to the server and internet.
Of note: some people with a similar problem have talked about networks with this problem working intermittently, but mine seems to be consistently broken.
Initially I was able to avoid fixing the problem by using our neighbors' unsecured wireless network, which is sort of awful, I know, but at least it kept me from having to deal with this for a while. Today it started to do the same thing to that network. Both networks continue to work on our Macbook and other Macbook Pro, which is why I don't think that it's a router problem.
I've been able to connect to our other computers through computer-to-computer networks—going through our main shared network (and thus the wireless router) doesn't seem to work—which I think shows that the Airport card/hardware itself is intact (?). I did try connecting to the internet through the "internet sharing" option on our Macbook, but that had the exact same problems.
Another thing that may or may not be relevant, but is equally infuriating:
I've also noticed that my Macbook Pro has more trouble staying connected to a network than our Macbook—even when it was working, it disconnected/timed out extremely often, which is something our Macbook never does, even from the same location. When I try to connect to a network it spends a very long time displaying the "searching for network" animation in the menu bar icon, sometimes after the Network Preferences pane believes that it's connected, and sometimes even after I hit the button to turn Airport off. It's also started refusing to connect to any networks at all, on occasion, which is especially evident in the process of the diagnostics box thingy, because there it actually tells me it's unable to connect rather than just playing the searching animation for ages.
Here are some other things that I've tried:
setting up a new 'location'
restarting the computer
deleting the airport preferences file
restarting in safe mode
restarting open firmware
confirming that the firewall allows all incoming thingies
resetting the router
making sure the keychain password allows all applications to access it
connecting to the internet through a computer-to-computer network from another machine
Because the situation has deteriorated over time, I'd also like to know whether people think that it's two problems (the type of router then later the airport hardware(?)/software(?) itself, perhaps) or just one. Since I've tried basically everything besides switching out our router, I'm kind of inclined to blame it on that, especially because one of the more plausible explanations for this problem that I've heard is a time-out error due to Airport expecting a faster response than it's able to get from older routers; however, the fact that other networks haven't been working means that it's not likely to be just the router. If it's just one problem, which is the simpler explanation, then I guess there's something properly wrong with my computer's software, in which case I guess I'll take it to the Apple Store. :/
I'm in love with my computer otherwise, and I'll admit that I spent a good twenty minutes sobbing out of frustration over this. Any help would be immensely appreciated.

HI and Welcome to Apple Discussions...
Try Changing the Airport Channel
Open AirPort Utility, located in the Utilities folder in the Applications folder on a computer using Mac OS X.
Select the device you’re setting up, and then click Manual Setup. Enter the base station password if necessary
Click AirPort in the toolbar, and then click Wireless.
Choose a new channel from the Channel pop-up menu.
Carolyn

What to do if you can't access a wifi network and showing you message that your airport has a self-assigned IP and cannot be connected to the internet?

Hi,
i am currently using 10.6.8 snow leopard
i usually access internet through my broadband modem and wifi at home.
i've been using our home wifi network for almost 1 week now (since it's new) and almost everyone at home use it as well.
and im using my broadband everytime i go out.
this last week, i went to a vacation and i use the wifi connection of the hotel where i stay in.
my connection works fine and so i don't use my broadband anymore.
then i got home..
when i got home.. i tried to connect to our home wifi network again .
like what im doing before, im clicking the airport icon on the top of my desktop,
and since my airport is always on, the next step that im doing is to click the preferred network that i want to join and put the password on it.
this is perfectly working in my macbook before i left.
but now , it's not working to my laptop anymore! i can't connect to it!
after putting the password and hitting the enter, the airport icon at the top will run, however after seconds it showing gray color with exclamation point on it!
the alert is showing : No internet connection
but the network i joined is still checked and showing full signal !
i tried checking my Network under system preferrence and the airport tab in the left corner is showing me a message that
my airport has the self-assigned IP address 169.***.****.** and will not be able to connect to internet!
i don't know what happen and i dont understand why is this happening since everyone at home can still use and access our home wifi !!
it's the same network that i'm trying to connect to anyway!
i tried using my broadband instead to connect online and it works fine!
but everytime i try to connect using wifi at home , again i cant connect!
anyone can tell me what's going on?
i haven't try joining other network anyway! but i'm planning to do so..
can some one help me please??
showing me a message that
my airport has the self-assigned IP address 169.***.****.** and will not be able to connect to internet!

and now, when i tried to check again my network preference below the airport tab is showing a message that
"my airport does not have an IP address and cannot connect to the internet!"
then after seconds it will goes back to the first message that
"airport has the self assigned IP address etc....."
i don't know whats going on now!
airport tab is not showing green color anyway! i'ts always in yellow!
i tried turning it on and off but nothing happen! HEEELLLLPP!!!!

Self assigned IP Address, wireless doesn't work

After upgrading to Leopard I keep getting "AirPort has a self-assigned IP address and may not be able to connect to the Internet." when I try to connect to the wireless network. Thus, wifi does not work at all. I've researched it best I can and it seems to be a problem with the router assigning an IP address to the mac, but why didn't this happen in Tiger? However if I play around with it for awhile it will randomly start working, but the same method doesn't fix it everytime. It also works fine in bootcamp. If I physically plug into the router, it works fine. This problem didn't exist in Tiger at all.
Message was edited by: SuperDupe453

Follow-up:
On the two laptops, I finally managed to get on line by switching to a different wireless access point, on a different modem. I surmise that the communication between the Macbook DHCP client and the modem/router's DHCP server is less than 100% effective. Looking at the modem/router, I could see that all of the Macs had active connections. But, instead of showing the names of the Macs, the page showed a star (*) for each Mac. I had to compare Mac addresses to verify the connections. The MAC address, of course, is hard-wired into the computer's network interface. It appears that either the DHCP client didn't know what question to ask when it broadcast for an IP address, or it couldn't interpret the answer. Except in the case of the iMac, which worked perfectly.
I upgraded the MacPro last, since it is my primary machine. Same story--connection with self-assigned address, which is useless. However, this time, having nothing left to lose, I restarted the modem/router, which presumably dumped any inactive connections and issued new DHCP leases.
However, I do have a few words for the Apple GENIUSES! The Leopard network preferences page puts me in mind of a maintenance free battery. A few of the older folks will remember when you bought a car battery that had to be filled with distilled water to reconstitute the electrolyte. Then, periodically, you check the level of the liquid in the battery, and added distilled water when required. Adding water was required on occasion because some of the water would boil off under certain conditions. Then, we got the maintenance free battery, which is virtually identical to the older battery design, except that you don't have to perform the maintenance of replenishing the water. It turns out, however, that maintenance free batteries do vent on occasion, and should have water added. But, you can't add water because the battery is sealed. So, the difference between conventional and maintenance free is not that the maintenance free battery doesn't need maintenance, it is that you can't perform the maintenance without voiding the warranty.
The Leopard network preference page won't let you set the parameters that could restore a connection. If the DHCP client doesn't work automatically, you're stuck.

Self-assigned IP - No connection

I have a perfectly fine IP address when I'm hardwired, and a full signal, but no internet connection. Here's the steps I've taken. What am I missing?
-Obtained a valid IP address and connection by connecting my Powerbook G4 to my cable modem via ethernet.
-Turned off my computer, unplugged the cable modem, and let them sit, powered down, for over thirty minutes.
-Plugged the modem and Airport Base Station together via ethernet cord.
-Plugged the power into the cable modem. Waited for it to boot completely.
-Plugged the power into the base station. Waited for it to boot completely.
-Booted my laptop. AirPort: On. Full signal. No internet connection.
-System Preferences>Network>Network Status: "Airport is connected to the network home. AirPort has a self-assigned IP address and may not be able to connect to the internet."
-System Preferences>Network>AirPort> Configure IPv4: Using DHCP; IP Address: 169....
-Released and Renewed. Turn AirPort on and off. Released and Renewed again. Still 169 IP.
-Called ISP, said I was getting a good signal, problem must be on my end.
-Ran Network Set-up Utility. Get this error: Your computer could not connect to the Internet. Click OK to go back and change your network settings, and try again.
-Fails, fails, fails.
What is wrong? What am I doing wrong? And how can I make it right?
(All my software and firmware is up-to-date)
Powerbook G4 12 inch Mac OS X (10.4.5)
Powerbook G4 12 inch Mac OS X (10.4.5)

PrincessofMars,
I am getting the same issue. I just moved and got a cable modem from my internet company and went to set up my airport, old snow version, and I can't get both of my computers (pre-intel Mini and old ibook) to both work at the same time. I have been getting the "Self-Assigned IP - No connection" message as well. I have my mini working with the airport, but I can't get the laptop to work and I don't want to have to keep plugging in and unplugging stuff just to get the computer I am working on to connect to the internet.
Is it time possibly for me to just upgrade to a new Airport system?
- Sanjuany
I have a perfectly fine IP address when I'm
hardwired, and a full signal, but no internet
connection. Here's the steps I've taken. What am I
missing?
-Obtained a valid IP address and connection by
connecting my Powerbook G4 to my cable modem via
ethernet.
-Turned off my computer, unplugged the cable modem,
and let them sit, powered down, for over thirty
minutes.
-Plugged the modem and Airport Base Station together
via ethernet cord.
-Plugged the power into the cable modem. Waited for
it to boot completely.
-Plugged the power into the base station. Waited for
it to boot completely.
-Booted my laptop. AirPort: On. Full signal. No
internet connection.
-System Preferences>Network>Network Status: "Airport
is connected to the network home. AirPort has a
self-assigned IP address and may not be able to
connect to the internet."
-System Preferences>Network>AirPort> Configure IPv4:
Using DHCP; IP Address: 169....
-Released and Renewed. Turn AirPort on and off.
Released and Renewed again. Still 169 IP.
-Called ISP, said I was getting a good signal,
problem must be on my end.
-Ran Network Set-up Utility. Get this error: Your
computer could not connect to the Internet. Click OK
to go back and change your network settings, and try
again.
-Fails, fails, fails.
What is wrong? What am I doing wrong? And how can
I make it right?
(All my software and firmware is
up-to-date)
Powerbook G4
12 inch Mac OS X (10.4.5)
Powerbook G4 12 inch Mac OS X
(10.4.5)

Why does my Airport Express say "self assigned IP address"? No IP address for the ethernet, and it is not connecting to my cable router any longer...

Why does my Airport Express say "self assigned IP address"? No IP address for the ethernet, and it is not connecting to my cable router any longer...

Some cable providers.....like mine, a well known company......seem to take anywhere from a few moments to sometimes up to 30 minutes to allow their equipment back at the cable company to fully reset and issue a new fresh connection.
So, it would not hurt to leave things powered down for 15-20 minutes or more when you perform the reset that John Galt suggests.

10.5.5 Self Assigned IP OR no connection at all

Okay, I'll try to condense this as much as possible. I have an imac, MBP, cell phone, and a couple gaming systems which connect to my network via wifi. All has been well for ages with this setup. 10.5.5 comes along and I didn't install it for a bit. Thursday I finally do it, and now my iMac cannot stay connected to the network. It also many times will not connect at all, simply saying connection failed
The other devices all connect with no problem what so ever. I turned off my network security and same problem. I unplugged modem + router for 10 mins, problem persisted. I then fully reset my router and left it at default, same result. My iMac either gets no IP address, fails to connect at all, or does a self assigned IP which doesn't do anything because I still cannot get online. I also updated my router firmware with no effect (i tend not to do this unless I need to, it usually ends up causing more trouble than it fixes).
My router is a netgear wgt624 v3. This first occurred when playing WoW. This had me checking the WoW forums for solutions. Over the past week, the problem has happened enough times without WoW being on for me to rule it out as a cause.
My router is in the same room as the iMac, so this is not a range issue. The other devices connect fine, so it is not a shot router. I am at a loss for what to do. I am going to take the computer to another network in a couple of days when i have the time (school/work.. too busy) but I am unsure if that will help me much. If it works there I'll be further perplexed, and if it doesn't I guess it's time to consider a faulty airport card? I am under warranty still.
Anyone know of a possible cause to this? Or how to further investigate. Aside from trying on another network I feel I have exercised all options.

Very similar problem. Since upgrading to 5.5, my internet connection has been spotty. Now it seems to be gone for good. The very weird thing is I can ping my router, I can ping the DNS's (which are outside my network at my ISP) listed. I can ping anything, just can't get to the web or my email. None of my browsers can reach outside (Safari, Opera, Firefox, even ancient IE). I can't get my mail (Entourage). Up until now I've been more than happy with my new(ish) iMac.
I have a hard-wired connection, with a fixed address, so I tried the Airport. No dice, same thing. Reset my hard connection, same thing. Turned everything off then on then off then on again.
Any other computer in the house has no problems, just my newly upgraded Leopard iMac.
I was about to go bonkers when I checked my properties on my old XP machine. Somehow the aforementioned DNS addresses had been changed. This is very mysterious, none of my other computers had the DNS addresses as my iMac and I had not changed them since buying the computer. I entered my correct DNS addresses and voila, connection again.
Bottom line? Check your DNS addresses and see if they've mysteriously been altered. And if anyone else has had this odd problem Apple should know about it.
Another oddity is that when I originally opened my network panel the "Firewire" connection was highlighted. I have never used that one.
Very strange.

WiFi self assigned IP and no internet connection after OS & iTunes upgrade

I have two likely related issues that started as a direct result of upgrading to OS X 10.8.5 and/or iTunes 11:
Starting tonight, after upgrading my OS and iTunes I am no longer able to use Home Sharing between my iMac and Apple TV. Apple TV is logged in to my network and Home Sharing is on, on both devices (signed in to the same account), but Apple TV says Home Sharing is not connecting to my iMac. My iPhone 5 is also not showing a Home Sharing connection.
I've restarted both my iMac and Apple TV several times. Logged in and out several times. Turned Home Sharing off/on several times, power cycled and reset my network modem once.
While trouble shooting my Home Sharing connection I noticed that under my Network settings, Wi-Fi is yellow instead of green and reads "Self-Assigned IP... Wi-Fi has the self-assigned IP address xxx.xxx.xxx.xx and will not be able to connect to the Internet.".
When I go back to Apple TV I've found that althought it's connectted to my iMac through WiFi and I can see my purchased movies I can't view them becasue there is no connection to the iTunes Store (no internet coinnection through WiFi). But my actual network connection on my iMac is just fine.
So it seems that my new OS or iTunes upgrade has caused my WiFi to no longer allow an internet connection across teh wireless network.
Can anybody here tell me why that would happen and how can I fix it?
Any help is greatly appreciated,
David

Back up all data before making any changes.
Step 1
Take all the applicable steps in this support article.
Step 2
If you're running OS X 10.8.4 or later, run Wireless Diagnostics and take the remedial steps suggested in the summary that appears, if any. The program also generates a large file of information about your system, which would be used by Apple Engineering in case of a support incident. Don't post the contents here.
Step 3
If you're not using a wireless keyboard or trackpad, disable Bluetooth by selecting Turn Bluetooth Off from the menu with the Bluetooth icon. If you don't have that menu, open the Bluetooth preference pane in System Preferences and check the box marked Show Bluetooth in menu bar. Test. Continue if you find that Wi-Fi is faster with Bluetooth disabled.
From that same menu, select Open Bluetooth Preferences. If the box labeled Discoverable is checked, uncheck it. Click the Advanced button, and in the sheet that opens, uncheck the top three boxes, if any are checked. Click OK. Enable Bluetooth and test again.
If the application called "Bluetooth Setup Assistant" is running, quit it.
Step 4
This step will erase all your settings in the Network preference pane. Make a note of them before you begin, and recreate them afterwards. It may be helpful to take screenshots of the preference pane.
Triple-click the line below on this page to select it:
/Library/Preferences/SystemConfiguration
Right-click or control-click the highlighted line and select
Services ▹ Reveal
from the contextual menu.* A folder should open with an item named "SystemConfiguration" selected. Move the selected item to the Trash. You may be prompted for your administrator password.
*If you don't see the contextual menu item, copy the selected text to the Clipboard (command-C). In the Finder, select
Go ▹ Go to Folder...
from the menu bar, paste into the box that opens (command-V). You won't see what you pasted because a line break is included. Press return.
Step 5
Reset the System Management Controller.
Step 6
Make a "Genius" appointment at an Apple Store, or go to another authorized service center.
Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional — ask if you need guidance.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
*An SSD doesn't need to be zeroed.

?? New AExtremeBS- MInis self assign an IP instead of picking up DHCP addy

Similar Messages

Maybe you are looking for