Self Assigned IP ( Simple FIX )

OKAY , SO iHAVE HAD THIS ISSUE FOR QUITE A WHILE. I HAVE RESEARCHED MANY TIMES AND WAS UNSUCCESFUL AT FINDING A WORKING SOLUTION. SO, I CONFIGURED A SIMPLE METHOD WHICH WORKED PERFECTLY. I AM HERE TO SHARE WITH THOSE HAVING THE SAME ISSUE.
ISSUE :
SOLUTION ---> https://www.youtube.com/watch?v=ulHud2DnVbI&feature=plcp

Hello, good work, thanks for the tip!
But a simple small Text Instruction would seem far better!

Similar Messages

Self-Assigned IP --possible fix

I have been having difficulty with this problem, and have done every step from clearing .plists to reseting and rebooting.
I did do one thing yesterday which was a long shot, but it solved it completely.
I changed my router password from WEP to WPA personal, and then it worked again. Just like that.
Let me know if this works for anyone.

Hello, good work, thanks for the tip!
But a simple small Text Instruction would seem far better!

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

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.

My macbook air will not connect to the internet due to a self assigned IP address. I have tried trawling the support forums, but either I can't understand the suggestions, or they don't work. Please explain to me in simplest terms how to fix this. Thanks!

My macbook air will not connect to the internet due to a self assigned IP address. I have tried trawling the support forums for hours, but either I can't understand the suggestions, or they don't work. Please explain to me in simplest terms how I can fix this. Many thanks!

The warranty entitles you to complimentary phone support for the first 90 days of ownership.
If you bought the product in the U.S. directly from Apple (not from a reseller), you have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different. If you bought from a reseller, its return policy applies.

Hey, for some reason i turned on my macbook pro 2012 and it says i have no internet access. I then found out that it also says that my self assigned ip address will not connect to the internet. How is this and how can i fix it?

hey, for some reason i turned on my macbook pro 2012 and it says i have no internet access. I then found out that it also says that my self assigned ip address will not connect to the internet. How is this and how can i fix it?

Reset your modem.

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 - Fixed, but help still needed, please

I'll add a bit of a back story first which I hope will help people understand my issue, but also hopefully lead people with a self-assigned IP issue to a fix (link is within the post)
I’m on on an iMac 20″ Mid 2007. I recently updated to OSX Lion after having wifi connection issues in Leopard. I used to randomly get kicked off my wifi and given a self assigned IP. With Leopard, the issue was fixed by applying a manual IP, router address etc and restarting. The issue would return months later, but I got over it after a few tantrums.
Then as soon as I updated to Snow Leopard, I instantly had no internet access and I could only upgrade to Lion if I downloaded system updates. So after a few hours of searching, I toggled my internet sharing ‘on & off’ and that was enough for that fix.
But then I upgraded to Lion and again, no internet. And nothing worked for me at all, every fix on the internet I tried failed. If my airport ever managed to connect to my router I would get a self assigned IP. Or it would say it was connected but there was no internet. So I hunted for hours and eventually found this:
Now, here is a fix for anyone who is having the same issue. I hope it works for you!
http://www.davidpierron.com/index.php/archives/2009/04/13/289/
This did work for me. The fix is to flush your ipfw through terminal, and it worked for me instantly.
However, I now have another issue that I really hope people can help me with. It's not as annoying as the above, but my god it's still very annoying!
Here are some bullets to show the tedious routine I have to go through in order to connect to the internet via my airport.
• I turn on my mac and my it tries to connect to my router automatically. But after a minute of trying, it says it can’t connect.
• I select my router manually from the list and have to enter my password manually, even though it is already saved in my Keychain.
• It then connects and says, ‘Connected but no internet’, so I leave it for two minutes and throw things around the room.
• After those 2 minutes it connects to the internet. But no, I can’t browse the web as the browser says 'DNS look up failure'.
• So I open terminal, enter 'sudo ipfw flush' to flush my ipfw and BINGO, I’m online 5 minutes after logging on to my machine.
The router I am using was only issued to me 8 months ago by my new ISP here in the UK, it connects via WEP and has always been stable for every other device I have connected to it. But I am going to ring up my ISP and see if there is a new router I can get.
If anyone - ESPECIALLY APPLE who seem to be shying away from admitting there has ever been an airport wifi issue - has any information to advise me, then please let me know.
Also if you are having a Self Assigned IP address issue and that fix above works, give the man some credit on his blog, and if you know him, give him a kiss from me!
Thanks

Update:
I spoke to my ISP to see if they had any newer routers and if they did WPA now.
I have a new router on its way and they have updated my router to do WPA!
The result?
I now connect to my router automatically after a restart. No issue there.
However,
It still can't find the internet when it first connects.
I still have to wait 2 minutes for it to find the net.
I still have DNS issues once connected
I still have to flush ipfw before it works correctly.

Fix for Airport Wireless Connection Problem stating Self-Assigned IP and not wanting to connect in Lion OSX.

Fix for Airport Wireless Connection Problem stating Self-Assigned IP and not wanting to connect in Lion OSX.
Bought my girlfriend the newest Macbook Pro 13" and began experiencing problems with my wifi the moment we got home. Her Macbook would not connect to our home Wi-Fi while my old Macbook Late 2008 running Snow Leopard connected without a problem. Airport would say that it had a Self-Assigned IP address (168.x.x.x). Did not realize it was a Lion problem until after using her Macbook Pro and becoming jealous of the new OSX, I upgraded. Soon after I was unable to go online. Luckily I had my iPad 2 and I began to scoure the net for help. Ran into allot of suggestions but it was not until I tried the following all together was I able to share the good new, from my Macbook. Hope this works:
First go to Preferences > Network and click on the cog next to the + and - on the sidebar and click Set Service Order
     - Move Wi-Fi to the top and click ok.
     - Set location to Automatic
     - Click Apply
     - Click Advanced
     - Click the "-" on the selected Wi-Fi router you wish to connect to
     - Click Apply
     - Click Lock to Prevent Further Changes
Go to your Mac's harddrive, (Macintosh)
     - Go to Library > Preferences > SystemConfiguration >
     - Delete "com.apple.airport.preferences.plist" file
Turn off your computer
     - push and hold Option+Command+R+P
     - turn on computer
     - when the grey screen turns on you will hear the OS X "ON" sound (for lack of a proper term) and it will momentarily restart.
     - you will once again hear the "ON" sound, let go of all keys.
     - this resets your PRAM
Go to Preferences > Network > Advanced > + sign
     - click Choose a Network
     - Select your network and enter password
Viola!!! I tried this on my Macbook Late 2008 and my girlfriends new Macbook Pro 2010

     No you are clearly mistaken. The Self-Assigned IP address problem exists on many Macbook Pro models, including the current model, which I mentioned as being the original computer with the problem. While my 2008 Macbook is older it was working perfectly on Snow Leopard and didn't suffer issues until switching to Lion. So clearly the problem exists on the operating system and not so much the hardware.
     I called Apple Support and they had no fix for the problem and told me that this would hopefully be addressed in a subsequent update. It wasn't until I came accross the answer after trying many different methods that I got both of the Macbooks to connect to my router. Otherwise I wouldn't or could not have been surfing the internet for the last 4 months.
Cheers.

Self-assigned IP adress problem. What if none of the fixes worked?

I just developed the "self-assigned Ip adress" at my college last night. I've been up all night on forums trying to solve the problem and tried about everything.
I've:
Tried to Renew DHCP Lease. (does nothing)
Manually input ip address. (doesnt work because the college uses a dynamic ip instead of static)
Opened the firewall to allow all connections. (I think it already was open)
Created a new location. (nothing)
Run diagnostics about 10 times. (prompts to reset router or modem, which I doubt is the problem since my roommate's laptop works fine)
Created another ethernet connection. (nothing)
Repaired the permissions. (nothing)
Can't think of what else I did, but I'm thinking it could be an issue with the 10.5.5 update, so if nothing else works, I am planning to use my OS disks to reinstall OS X (I think it was 10.5.3 when I bought it.)
If there is an easier way, please advise!
Any help would be greatly appreciated.

I too am having this problem. I just updated from 10.4 to leopard, and could not connect due to the self assigned IP. Found somewhere online on another computer that you can shut down, restart and hold down the shift key to boot up in safe mode. Then restart, and everything works, normal IP. I then did software update, to get the latest leopard updates, and had the same problem, used the same fix. I was coming on the forum to ask if anyone else had this problem and to see if there were any explanations. Hope this works for you. I will keep reading to see if anyone else has an explanation. I also noticed that Internet connect is no longer part of OSX. I travel a lot and that function has helped me connect in many places, so I hope it's exclusion won't mess me up.

No Internet with Lion. Stay away until self-assigned IP addresses are fixed!

I have a TimeCapsule (802.11n 3rd gen) and four Macs. Until two months ago all was well and everyone could connect.
Two months ago the Apple apps on the MacBook Pro stopped connecting to the Internet on the TimeCapsule network (Mail and Safari would not connect, Firefox was fine). The MacBook Pro connects on all other networks. I travel a fair amount and the computer has connected fine at all networks tried. I have sinced updated to Lion (10.7.2) and the problem is the same. The error in System Preferences indicates that the computer has a self-assigned IP address and will not be able to access the Internet - but Firefox works, so we know that is not entirely the case.
Last week our desktop stopped being able to access the Internet using the TimeCapsule network. Problems the same as the MacBook but the desktop Mac is using Snow Leopard.
Our older laptop is using an earlier version of OSX and all is well. Out antique Mac laptop is also working well.
We also have a Verizon MiFi and all machines can access the Internet on that.
I have tried every "fix" I can find on the boards and through Google. Nothing works. From the looks of the boards, there are thousands of users with this problem and no answer from Apple.
I was much better off before I switched to Lion. In those days, I just used Firefox and looked at my iPad when I needed mail (and waited to sync at the office). But with Lion comes iCloud and an increased reliance on the App store, making internet connectivity through Apple apps is a must. Can someone from Apple help us fix this? Does anyone have any suggestions?

That is what I told Comcast, but they said since my
computer works "fine" in Safe-Boot,
Classic, and the other PC—then they
conclude there's no problem with their hardware and
that its not their problem; that its Apple's issue.
And nope I'm not connected wirelessly, it's through a
basic ethernet cable.
I don't know who to blame for this. Five years ago, this never happened, but it is common now. It affects both Macs and PCs, but as usual, people like Comcast will make an effort to fix a PC but throw up their hands with a Mac. Go figure.
So, what speed, duplex and adapter type numbers
should I put in?
I don't know for sure. Start with duplex. If it current says "auto", change it to "full". If that doesn't work, or if it already was "full", change it to "half". If still nothing, switch it back to "auto" and fiddle with all the 10/100 speed combinations. You may have to go back and try different duplex and speed combinations! It sounds harder than it is. Try changing the duplex and adapter settings from "auto" before changing the speed. I'm am on my work Dell right now (which needed the same fix BTW), so I can't give you very good step-by-step instructions.
The thing that troubles me is why is it that the
internet works fine in Safe-Boot and Classic, but not
Normal OS X mode?
No clue about that.

IPad Wi-Fi has the self-assigned IP address 169.254.210.251 and will not be able to connect to the Internet. How to fix?

Mini connects to internet via cable modem fine.
Want to have ipad connect also but mini Wi-Fi has the self-assigned IP address 169.254.210.251 and will not be able to connect to the Internet. How to fix?

Hello:
I am a long way from a wi-fi expert, but.....
You need, I think, either a router with wi-fi or an airport (express or extreme). The iPad needs to connect to to a network. In my case, I use an airport express and both my iMac and iPad 2 connect to the Internet through the airport device.
Barry

Airport has a self assigned IP address. Why and how can I fix it

Airport has a self assigned IP address and can't connect to the internet. Why and how can I fix it?

First thing you need I think is to get your iMac connected to the Internet.
Shut down your iMac and you iPad. Then power off your router. Wait 30 seconds and power up the router.
After the router indicates that it is connected to the Internet then start up your iMac and see if it connects. If the iMac connects to the Internet then your iPad should too.
If this power up sequence doesn't work you'll have to dig into the router setup to make sure it is working properly.

Self-Assigned IP: How Can I Fix This?

Hi,
I've posted on this issue before, but am still having trouble. All was working well with my wireless network until recently, when I became unable to connect my iBook G4 to my wireless network via a Netgear router. I am getting the "Self-Assigned IP Address", despite the fact that I am using DHCP, have renewed the DHCP lease, and input my IP address manually. I can see my IP addresses under the DNS tab, and it is configured using DHCP with an IPv4 169. address.
I've tried all solutions. I was once able to resolve the problem by dragging the Library/Preferences/System Configuration folder onto the desktop. Now the problem has returned despite the folder being on the desktop and remains even if I move this folder back into the Preferences.
Can anyone help me? I am at the point of simply buying a new laptop, but surely there has to be a solution...
Thanks.
lsb
Ps. I am using an iMac running Snow Leopard as well. The iBook is running Panther. The desktop, so far, touch wood remains OK.

lsb wrote:
Hi,
I've posted on this issue before, but am still having trouble. All was working well with my wireless network until recently, when I became unable to connect my iBook G4 to my wireless network via a Netgear router. I am getting the "Self-Assigned IP Address", despite the fact that I am using DHCP, have renewed the DHCP lease, and input my IP address manually. I can see my IP addresses under the DNS tab, and it is configured using DHCP with an IPv4 169. address.
I've tried all solutions. I was once able to resolve the problem by dragging the Library/Preferences/System Configuration folder onto the desktop. Now the problem has returned despite the folder being on the desktop and remains even if I move this folder back into the Preferences.
Can anyone help me? I am at the point of simply buying a new laptop, but surely there has to be a solution...
see if the posts by Tesserax in this thread http://discussions.apple.com/thread.jspa?messageID=10162935&#10162935 give you any pointers
good luck !

Self assigned IP??? Don't know how to fix

My airport keeps self assigning an IP address, I've tried rebooting PRAM, manually entering router and Ip address, deleting system preferences files, renewing DHCP lease, deleting airport, reconfiguring internet settings and airport settings and rebooting router. OUT OF IDEAS, this is a new problem for the first time in 3 years. HELP

quatchi11 wrote:
My airport keeps self assigning an IP address
Welcome to Apple's discussion groups.
By "my AirPort", do you mean an Apple AirPort base station or the AirPort functionality of your Mac? Is the referenced IP address that of your Mac or of something else? Does this happen in connection with any other event, such as waking from sleep? How often does this happen? Is your Mac connected to your router wirelessly? When you see the self-assigned IP address, are you still connected to your router?
I've tried rebooting PRAM, manually entering router and Ip address, deleting system preferences files, renewing DHCP lease, deleting airport, reconfiguring internet settings and airport settings and rebooting router.
It sounds like you may have tried all the steps below for resetting the connection settings on your Mac:
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 same panel, select the AirPort connection item, click the "Advanced" button, select the "TCP/IP" tab, then click "Renew DHCP Lease".
5) 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.
If there are any you haven't tried, you might try them. Before you try these, note all your network settings, because the latter steps will destroy them.

Self Assigned IP ( Simple FIX )

Similar Messages

Maybe you are looking for