Self-assigned IP on one device at startup which eventually corrects itself

I use a Time Capsule as my primary wireless router (full disclosure: an Airport Express also acts as a repeater, and a wired Netgear router is also connected). 8 out of 9 devices connect wired and wirelessly without any issue, except for a wireless MacBook Pro which always boots and wakes with a self-assigned IP (no internet connection) despite a successful connection to my WPA wireless network. After 3-5 minutes, and perhaps coincidentally after a Time Machine backup is started manually or automatically, the internet connection rights itself.
I have tried every solution I could find - at least a dozen - including resetting all devices and waiting, deleting airport preferences, renewing DHCP lease, uninstalling and reinstalling Airport, deleting and creating locations, deleting keychain entries, turning off firewall, updating firmware and software, safe mode reboot, etc. Can anyone offer any last wisdom?

Siouxnil wrote:
deleting airport preferences, renewing DHCP lease, uninstalling and reinstalling Airport, deleting and creating locations
From your description I'm guessing you tried the steps below. If not, you might try the remaining ones.
1) Use the AirPort menu bar item to turn AirPort off, then on again.
2) In the Network panel of System Preferences delete the AirPort item from the left column, then add it back.
3) In the same panel as (2), define a new location and see if you can make that work.
4) In the folder /Library/Preferences (not <yourhomefolder>/Library/Preferences), move the folder SystemConfiguration onto the Desktop, then restart your computer. See if you can now make your AirPort connection work.

Similar Messages

  • Possible to assign apps to one device?

    I have an Iphone 4S and a Ipad 2 on the same account.
    Is it possible in iTunes to assign each app I have to either only my iPhone, or my iPad or both.
    I am tired of seeing apps I got for my Ipad end up also on my Iphone, and vice versa.
    btw, just noticed that my Ipad2 don't show on my registered list down below. It should be as I have been using it with the same account since I got it new last fall. Did I miss to do something?

    Welcome to the Apple Community.
    Turn off automatic downloads for apps (settings > store) and sync the apps you want on each device via iTunes.

  • Self assigned ip and can't connect wirelessly on any apple device

    Man oh man... this issue has been festering for almost an entire year now and I have not found a solution. Last August (2009) my macbook stopped wirelessly connecting to my ATT 2WIRE dsl modem saying it had a self assigned ip address. I bought the computer in July and could connect with no issues for about a month. Ever since then, I've been connected via ethernet with slow connection. At the same time, the 2 iPhones in our household also could not connect wirelessly. One G5 could connect wirelessly but was extremely weak and often dropped the signal.
    I did tons of research and found zillions of other people with this issue and no resolution. I've tried every solution on macrumors, and apple discussions with no results... I've disabled firewall, renewed DHCP, tried DHCP manual (which then changes the status to say I'm connected, but nothing works in my browser), restarted, etc. At work, I can connect to our Linksys router wirelessly with no issues. When my friends come over, their macbooks and iPhones don't work either!
    Originally I thought the issue was my modem so I ordered another one. Same issue. Just this week I was at my wits end and cancelled my service with ATT and switched to Clear. I acquired a Linksys router to connect to the Clear Modem and I'm STILL having this issue. The difference is now that my iPhone can connect wirelessly but my macbook still cannot. The router is a Linksys WRT51ab. My macbook pro is on version 10.5.8. I can only assume that some kind of update to airport is causing the problem. As of now, my IPv4 address is: 169.254.111.225
    Please someone help me! I promise some kind of reward if you can help me fix this.

    Based on the model number, your Linksys router is OLD.
    I'd actually suspect that your router has been the problem.
    You can download the full user manual here --> http://homedownloads.cisco.com/downloads/wrt51ab_ug.pdf
    I don't know if you ever secured your wireless router or renamed it from the factory defaults.
    If it your Linksys wireless router is not password secured, it's possible that someone else changed settings about the time things stopped connecting.
    Regardless, you can completely reset the Linksys to the factory defaults by holding down the Reset button on the Linksys for more than 10 seconds.
    Do that first.
    Then see if things 'magically' start connecting again. I'm guessing the phones will connect, but the Mac still won't, because of the IP address in the current configuration.
    If not, here's how to configure your Mac network settings.
    On your Mac, in System Preferences, Internet and Network, Network,
    Click on Location, Edit Location
    Click the + sign to create a new location called '_test'
    (The underscore before the name will put it at the top of your Locations list where it's easy to find)
    Select Ethernet (wired)
    First, we'll let DHCP try to set the address.
    Click Apply.
    Move the selection back to Ethernet, and watch the Status.
    If it shows Connected and IP address appears after a few moments, at least the WIRED configuration is working.
    Now IF the Wired configuration works, lets move on to the wireless configuration...
    (If the Wired configuration is still not working, post back and we'll work through it.)
    Still in System Preferences, Internet and Network, Network, with the _test location you just created...
    Select the AirPort interface in the left column.
    Turn AirPort On.
    If no Network Name appears, click on the up/down button and select Join Other Network and select your Linksys router name.
    Click 'Apply'.
    Leave DHCP settings alone and watch the Status to see if it connects.
    Let me know what happens!

  • Upgraded to Maverick. Now cannot connect to wifi. All my other devices will connect. Have rest wireless hot spot switch and cable modem. Other devices still connect but MacPro does not. MacPro wireless is self assigning an IP address blocking access.

    Upgraded to Maverick. Now cannot connect to wifi. All my other devices will connect. Have rest wireless hot spot switch and cable modem. Other devices still connect but MacPro does not. MacPro wireless is self assigning an IP address blocking access. It will connect if I connect to my iPhone hot spot via wifi. Any ideas?

    If you follow this video you'll see how to delete your WiFi AP from the OS, this will allow you to select it again which I feel will correct your problem.
    https://app.box.com/s/fe7v7h7kywjr23spumqp

  • One SOLUTION for "self assigned IP address"

    Hello there, dealing with the nasty issue of "self assigned IP address" has been my latest two days nightmare, I tried lots and lots of solutions I read in forums here and there without getting to a point.
    I started this post because I want to post here a solution that really worked for me and I haven't seen it posted over the web.
    I don't remember where but I saw the comment that WEP encryption by the router is not very mac compatible as opposed to WPA. So a while ago when I entered my router home screen (Thomson TG585 v7) I saw the option to enable WPA-PSK encryption and went for it, I can tell you it inmediatelly got me online and till now my airport wireless conection is working perfectly.
    I'm not any mac/web guru and maybe I'm stepping some technical details but I want to share this tip with all of you because I know it can be a really nasty problem that one of the gat dam "self assigned IP address" and this may help somebody else. ;-)
    Best regards
    Luis Erantzcani

    Great tip Luis, thanks!

  • Airport extreme has self assigned ip... on all my apple devices

    Man oh man... this issue has been festering for almost an entire year now and I have not found a solution. Last August (2009) my macbook stopped wirelessly connecting to my ATT 2WIRE dsl modem saying it had a self assigned ip address. I bought the computer in July and could connect with no issues for about a month. Ever since then, I've been connected via ethernet with slow connection. At the same time, the 2 iPhones in our household also could not connect wirelessly. One G5 could connect wirelessly but was extremely weak and often dropped the signal.
    I did tons of research and found zillions of other people with this issue and no resolution. I've tried every solution on macrumors, and apple discussions with no results... I've disabled firewall, renewed DHCP, tried DHCP manual (which then changes the status to say I'm connected, but nothing works in my browser), restarted, etc. At work, I can connect to our Linksys router wirelessly with no issues.
    Originally I thought the issue was my modem so I ordered another one. Same issue. Just this week I was at my wits end and cancelled my service with ATT and switched to Clear. I acquired a Linksys router to connect to the Clear Modem and I'm STILL having this issue. The difference is now that my iPhone can connect wirelessly but my macbook still cannot. The router is a Linksys WRT51ab. My macbook pro is on version 10.5.8. I can only assume that some kind of update to airport is causing the problem. As of now, my IPv4 address is: 169.254.111.225
    Please someone help me! I promise some kind of reward if you can help me fix this.

    cbrown1 wrote:
    Last August (2009) my macbook stopped wirelessly connecting to my ATT 2WIRE dsl modem saying it had a self assigned ip address.
    Welcome to Apple's discussion groups.
    The "AirPort Extreme" in this board area actually refers to Apple's "AirPort Extreme Base Station". It doesn't seem that you have such a thing. Please confirm that. The best place for similar posts is probably the "Getting Online and Networking" forum (http://discussions.apple.com/forum.jspa?forumID=1222) of the "OS X v10.5 Leopard" area.
    To address your problem, you might try resetting your connection settings using the steps listed in this message:
    http://discussions.apple.com/thread.jspa?messageID=10695921&start=1
    They're not guaranteed to solve the problem, but they'll only take you a minute or so to try.

  • WiFi, Self-Assigned IP (secured networks only), and Knocking Other Devices Off Network

    My MacBook Pro (3,1) refuses to initially connect to any secured WiFi network (home, work, hotel, etc.).  First it self-assigns an IP address and gives that little "!" symbol in the WiFi icon.  Then, after a few moments, it connects to the Internet but knocks every other computer and device (iPads, cell phones, etc.) off the network.  When you go to reconnect the other computers and devices, the MacBook Pro gets knocked off the network and then refuses to connect to the router at all (you get an instant "timed out" error) until a restart.  It has absolutely NO problems whatsoever connecting to a non-secure network (free WiFi, WiFi without a password at home, or those public hotspots that take you to a webpage to agree to the terms before connecting).
    The following are true of my MBP:
    1. The entire harddrive has been replaced (not original).  I had this problem before and after this replacement.
    2. The OS has been upgraded / wiped / reinstalled more times than I care to count.  I started having this problem with the original upgrade to OS X 10.5.x and have continued through to its current OS (10.8).  No particular OS was more or less difficult that I could tell.  It currently has a fresh (re-wiped) install of OS 10.8.
    3. The AirPort card has been replaced.
    4. The issues are consistent regardless of my location or the router / services I am connected to.  I have no problems at all if there is no security - I have the above problems when trying to connect to a secure network (any security).  I can be at home in my own house or in a hotel or airport - if there is no password, it connects no problem - if you have to type a password, forget it.
    5. The computer doesn't have any problems using an Ethernet connection, and the WiFi behaves the same with or without an Ethernet connection (in other words, I can be connected to the Ethernet fine, but the WiFi can still self-assign an IP - the 169. whatever)
    Any thoughts?  Things I could try?  Things I could be doing differently?

    Do this the stuff you find at the bottom of this thread:
    https://discussions.apple.com/thread/3864270?tstart=0

  • Assign VLAN by MAC for one device

    Is it possible to assign a single device to a vlan by its mac address? 
    On a Dell 6248 I could use
    vlan association mac 1111.2222.3333 12

    Hi,
    I don't think there is a command to assign a device to a VLAN by using it's MAC address. But it can be done by setting up a VMPS (Vlan Membership policy server). Which dynamically assigns VLANs to the devices using their MAC or IP address.
    Rate if you find this helpful.
    Regards,
    Chandu

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

  • Self assigned IP : still no bug fix ?

    I have a problem for a long time with my Time Capsule. I use an ADSL modem and router (from Free French ADSL Provider) and my TC is plugged on it and set to "Bridge" mode.
    I have many devices wired and wireless on the TC. But I have a big problem, sometimes (not all the time), my MacBook is getting a "169.254.x.x" IP address, a self assigned IP.
    That's weird because sometimes it works well from 6 AM to 7 PM for example, then at 7 PM it doesn't work anymore. There is no reason why, because I haven't touch anything in my network.
    It's pretty annoying. Is Apple aware of this problem  ? Can we hope a fix soon ? I had many problems with the WIFI on my Mac (before, it was the "wake up" WIFI problem but it seems to be fixed in the last Lion update).
    I've tried everything, reset all (TC, Macbook etc.), sometimes it works a day, the other day it's not
    Thanks

    7pm sounds too specific to me.. get a wifi analysing software, kismet on the mac but inssider on a pc is a better utility. Locate all the wireless around you and what channels are used. I would say you are being swamped by higher intensity wireless than the TC can produce.
    Go into the wireless setup and change over to manual settings.. set to N wireless.. and set to manual channels.
    In 2.4ghz try 1, 6, 11.. but pick whatever is the lowest usage from your survey of wireless usage.
    Also try and use 5ghz as it has less interference. When you are bridged, the IP address is derived from the modem and not the TC so the issue can be there.. try setting dhcp to fixed for the MAC address of each wireless. and set the lease to very short.. 30min or even try 10min.
    There certainly are issues with Lion networking.. exactly what is hard to figure out.. but you can also try the TC with earlier firmware.. go back to 7.5.2 which was much more reliable than later ones.
    You can also try it in router mode putting the modem in bridge if the ISP supports PPPoE.. or use DMZ with the modem still doing routing. The TC will kick up a double NAT error but just select to ignore it. Sometimes it will work better in router mode.

  • 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

  • MacBook Pro can't actually connect to Wi-Fi with Self-Assigned IP

    Hi there
    I have a 15 inch MacBook Pro and it can connect to Wi-Fi but have no actual data coming in. And it says self-assigned IP.
    This only happens to my home Wi-Fi, however, I can connect and use Wi-fi at school or anywhere else perfectly. In the mean time, my Android phone and my flatmates' Windows have no problem using the Wi-Fi. The problem has been going on and off for a month, sometimes it works again and sometimes it goes wrong like this again.
    During this time I mostly use my other MacBook Pro 13 inch Retina. Until today, this problem happens on my 13 Retina mac for the first time, and the 15 Pro again as well. A few days ago, my 15 Pro started working again, and today they just gone wrong together at the same time.
    I just found out that my 15 pro can still work if connected to ethernet, but I can't just work in the living room, where the router is. And as you know Retina doesn't support Ethernet.
    I've check on the Internet and found many people have the same problem as I do. I also tried lots of ways to fix it with the information I found online. And nothing works. I even suspect that it's actually my flatmate blocks me out with some setting on the router (Is it possible?)
    Anyways, can someone please help me fix it thoroughly... Please and thanks.

    Each country regulates wireless networking differently. Wi-Fi devices are restricted to certain frequencies and power levels. The client devices try to find out where they are and configure themselves accordingly. Since a wireless access point (WAP) usually does not move across national boundaries, the Wi-Fi regulatory domain (country code) is set by querying the first one to respond when the client initializes itself. You don't have any direct control over it on the client. If your device is picking up the wrong country code, and is therefore locked out of using some Wi-Fi channels or operating at full power, the only lasting solution is to fix or remove the misconfigured WAP.
    To find out which WAP's are broadcasting a wrong country code, do as follows.
    Triple-click anywhere in the line below on this page to select it:
    /S*/*/P*/*/*/*/*/airport -s | open -ef
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Launch the built-in Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window by pressing command-V.
    The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign ($) to appear.
    A TextEdit window will open with the output of the command. The first line should look like this:
    SSID BSSID RSSI CHANNEL HT CC SECURITY (auth/unicast/group)
    Each line below that one represents a WAP within range. Compare the two-letter code in the column headed "CC" with the ISO code for your country. The code "X0" means that the country couldn't be determined. If a WAP with a wrong code is not under your control, try restarting the computer as close as possible to your own router.

  • "self-assigned' IP address.

    Firstly to be semantic. Part of my frustration at this problem is the fact that Apple call this a "self-assigned" IP address. In no way have I assigned this IP address myself. My Macbook Pro assigned it for me.
    I have had this problem intermittently since I bought my Macbook Pro years ago. The first time I found a solution by renewing my DHCP lease and sometimes that would work, sometimes not.
    Second fix is a reboot, third fix is to make airport inactive and then re activate it again, fourth fix is to add new location from system preferences and then start from fix number one again
    I have also tried various commands suggested for terminal and tried deleting folders that have been suggested as the cause.
    But now returning from a trip overseas I get the "self [apple] - assigned IP address" message and none of the fixes that I have wasted my time applying in the past are working.
    It's almost comical because just a week ago I was saying to somone how I was thinking of moving to PC as I had had enough of trying to fix problems with my Mac.
    Hours of trawling the internet for a simple walk through of the problem suggests anything beyond what I  have already tried. I can't believe I have put up with this issue for so many years, just accepting that it's a small problem that occaisionally interupts the massive benefits of using a Mac.
    So if anyone has a final suggestion of where to go to fix the problem [on line] I would be so releived of my frustrations. If not then I am heading out to buy a PC tomorrow and I will take great pleasure in destroying my Macbook Pro.

    I have a little Macbook that connects to my wifi connection automatically without any problems and always has.
    I have a much more expensive, much more powerful 2010 Mac Pro Quad Core which is totally incapable of jumping on to the same Wifi Connection. Even if both devices are right next to one another.
    Of course, I have the usual 'Self Assigned IP' problem, and like you, I have trawled the internet endlessly following all sorts of guides, all sorts of DHCP Renewal methods and all sorts of manual methods and all sorts of Firewall settings etc etc etc.
    In the end up, none of it ever works. Except for the very rare occasionally day I'll turn the Mac Pro on and it will have randomly decided to connect to the WIFI connection and work fine.
    I gave up trying to figure it out. I can no longer connect to the internet so my Mac Pro has to live with no important updates etc. Not very future proof at all and extremely frustrating.
    I run a busy recording studio so its solely the fault of this problem that I struggle to be as competitive as my rival studios as I can not preform the simple Audio software updates everyone else can. Brilliant.
    INFURIATING.

  • Self Assigned IP / DHCP problem : sharing my fix.

    Okay. I WAS frustrated for a long two weeks before I figure this out. It seems that this problem has affected a LOT of people out there, and since I now am (supposedly) free of this thing, I want to share my hypothesis of the problem's roots (A) and my fix (B).
    Note that:
    - i'm free of this problem since the last one week, so .. well, hopefully this is right.
    - the problem happens almost anywhere, with any router types, and in any connection type, be it ethernet or wireless a/b/g/n.
    - the problem is automagically fixed by running into safe mode.
    - the problem keeps happening again and again, although you have powercycled everything of the electronic peripherals in your house, even by disconnecting your phone/ADSL line and main power fuse.
    - disabling the Mac OS X Application Firewall sometimes cures it, but most of the time it happens again.
    - AFAIK (correct me if i'm wrong), the ipfw, mother of all OS firewall, exists within Mac OS X, and the Mac OS X Application Firewall (i call this OSXAF) has nothing to do with ipfw.
    A. My hypothesis and the reasons.
    * for an unknown reason, there is a rule created for ipfw that tells it to block the ports 67 and 68, both are the common DHCP ports.
    * because of that, your Mac cannot contact with any DHCP servers, anywhere. This forces your mac to assign an IP address by itself.
    * disabling OSXAF incidentally removes that rule, but after (one or a few times) reconnect or reboot, the rule appears again.
    * powercycling your routers or anything related does not concern ipfw, thus has no effect whatsoever to the problem.
    B. My fix.
    1. Get the WaterRoof free ipfw frontend (forgot the site, just google)
    2. Open it.
    3. Go to Static Rules part.
    4. Find everything which reads "deny blah blah blah port blah,blah,67,68,blah blah"
    5. Edit those rules so that there is no 67 and 68 inside.
    6. Open tools -> rules configuration -> save to startup configuration -> yes.
    7. Open tools -> startup script -> install startup script -> yes.
    That's all.
    For me, this seems to be a permanent fix. Please note that the startup script mentioned before exists in all *nix-based machines, so don't worry about startup time, there'll be no slowdowns (again, please correct me if i'm wrong, i had only little experience with *nixes). Besides, i suspect that if you don't save and reinstall that script, the previous script is the one which has 67 and 68 inside.
    Hopefully this helps. Any corrections, comments, suggestions, and/or knowledge are welcome.
    Cheers,
    -bam, the noob.

    OK, so a little background -
    I have an MBP with 10.5.5 (which I downloaded yesterday, so that's not the issue). This year at school they upgraded the wireless system and network control to Foundry routers and Bradford Securities Network Control. Problem is, my computer is intermittently and randomly having a hard time sticking with one IP and staying away from a self-assigned 169 IP. The System Prefs are fine, and even when I change to manual settings for the IP, it doesn't stick. I checked the terminal (tcpdump) and it seemed to be having a tough time accepting one of the two IPs the servers offered (there are two servers for redundancy). It asked for an IP, gets two offers, and then asks again. I was stumped, and so were the IT guys on campus. And it's not just me, many other 10.5 users are having the issue. And it's not the network, because nobody else is having the issue but 10.5 users. Certificate problems are similarly eliminated from possibility.
    The IT guy showed my this thread, and I was excited, so I first tried to just shut off the Firewall all together, and that worked, briefly, but now it doesn't matter if the Firewall is on or off, the problem persists. I tried your WaterRoof method, and the similar program NoobProof, but there were no rules relating to ports 67 or 68 at all, let alone denying them. (As a side note, when my FW is off, there's only the rule allowing all IPs in and out, and when it's on (but only allowing specific programs) it gives a second rule that denies "icmp from any to me in imcptypes 8." No idea what that means.) I've been watching tcpdump and the FW logs closely (as well as the console itself), but nothing has changed. The only interesting thing is that when the IP changes from the (good) 137 IP I'm supposed to have to the (bad) 169 IP, often times (in fact, most times) there is no firewall activity. The console says that the en1 link (wireless) is now down, and the tcpdump picks up the computer asking for an IP again, but the firewall logs pick up nothing, neither through the console or through WaterRoof. Which is weird, because I thought it was a FW problem (as did the IT guys), but the logs show that only occasionally when the servers offer me an IP does the FW block the request, but not all the time.
    As another point to note, this is not only an issue with the wireless. The wired connection (Ethernet right into the wall, and attempted from many different plug-in sites) also has this issue.
    My only conclusion is that the FW is buggy, or that the logs are missing denials, neither of which makes much sense, IMHO.
    Any thoughts?
    EDIT: Shutting off the FW often solves the problem, but not always. Sometimes I can get a correct IP even with the FW in full swing without anything popping up in the logs. And sometimes I can't.
    Message was edited by: kangasaurus

  • Self-Assigned IP fix?

    As with a number of users in the community, my wired Ethernet connection has reverted to a self-assigned IP. Are there any viable solutions to this problem?

    OK, so I hit this problem yesterday and I thought it was just one friend's mac. This morning I found that several macs were having the same problem on wifi. (Ethernet was OK, but not wifi.) I have SOLVED it for me - so here's the info in case it helps!
    NB - I have tried most of the solutions on most of the help threads. (Once, years ago, I had the same problem, and one of the fixes I found back then did work. I think it was either deleting the  wifi setting from Network Preferences or fixing the keychain or both. But this time, those fixes were achieving nothing.)
    Anyway, the solution was simple! My modem-router included a setting for its DHCP server that was limited to 20 addresses. In other words, it was offering addresses from 192.168.1.1 to 192.168.1.20.  At first I dismissed that possibility, since you'd think 20 would be plenty for one house! However, I was very wrong. Here's why.
    1. Yes, we do own several Macs, and some of these are connected by ethernet AND wifi, so those ones use two addresses each.
    2. Yes, we own several iPhones, iPods, an AppleTV etc.
    3. Yes, we had visitors in the house. My daughter's friend had brought her iPad; my parents had brought their laptops and their phones!
    4. I have an Airport Extreme and a Time Capsule, both connected (in Bridge Mode) to the modem-router, so that's two more addresses.
    5. Remember that DHCP leases last for 24 hours (or whatever your router is set to), so even when visitors are gone or machines are turned off, those addresses might not become free.
    SOLUTION? I changed the router's setting to offer all addresses up to 192.168.1.40. (I might even go back and offer even more than 40 - no reason why not).
    My wifi macs had no trouble from that point. Hope this helps!
    [NB - The reason my ethernet was always OK was that those connections had been running a long time. But if an Ethernet connection had gone down, and I had reconnected it at a time when its address had been stolen by another device, then I likely would have hit the same "self-assigned IP" error. In other words, in my case I don't believe the issue made any real distinction between wireless and wired connections.]

Maybe you are looking for