Self assigned IP address

I am in desparate need f some help from anyone. My macbook pro will not connect to the internet. All I get is a self assigned IP address. I have tried renewing the DHCP, restarting the computer, resetting the network, etc. Nothing seems to work. I have the Mac OS X 10.7.3 version. Please help!!!

Mac Pro, Mac OS X (10.7.3)

Posted on Apr 9, 2012 10:46 AM

Reply
217 replies

Jul 9, 2014 9:42 AM in response to joepark14

.

Thanks ericdy


I reported earlier that ericdy had solved my problem (page one). But it kept coming back again and again.


Ok, I think I have a solution now. Before you do ericdy's solution, delete all the multiple locations (I had six locations)


>>System preferences >>Network >>Location drop-down >>edit locations


Delete all the locations. Then do ericdy's reset. Then it might work.


Grrrrrr to Apple.

Jul 14, 2014 4:26 AM in response to ralphy

.


Ok, back again. That fix lasted all of one day, then back to the normal "self-assigned IP address" routine.


Grrrrr.



I went through each fix, one by one. This one appears to be holding up for three days now.


By jcdill on page 5:

a. Open your >>Preferences >>network settings >>Advanced >>TCP/IP tab for your wifi connection. The bad IP address is on line two.

b. In the TCP/IP tab click "refresh DHCP" until it refreshes to empty (no IP address). (Try with new client ID or ID empty, wifi on or wifi off.) - I had to hit 'refresh' nearly 20 times before it was empty.

c. Eventually, you will get the IPv4 Address to be empty. Stick with that. Press 'OK' and 'Apply', and try to reconnect with the router in the normal manner.

.



I hope this is a permanent fix, because this is B annoying. Especially as my two iPads have had no problem whatsoever with this router…. !!!



Cheers,

Ralph

Jul 15, 2014 7:39 AM in response to ralphy

Grrrrrrrr. Back to square one, and locked out of my router.


i have resorted to a 25m ethernet cable, to link to the router, which works fine. But why is technology going backwards, to cables??


Does Apple not have an answer to this problem yet? And this is not a router problem, it is an Apple problem.


I have two ipads that will talk to the router.

I have a signal booster that will connect to the router, and both ipads will happily talk to the booster.


I used to have an iMac that would talk to both for a year.

But it first stopped talking to the booster, and now it has stopped talking to the router too.


What is going on here, Apple??

Sep 5, 2014 12:10 AM in response to Wintour

Background: A few days ago a number of laptops/computers internet stopped working. Both PC and my MacBook pro. Now, a few days later, all the PCs have managed to connect by either changing the IP Address or other methods. We have changed the router as our technician thought that was the problem. My mac is still not able to connect.


Methods i've already tried: Changing the IP Address, deleting the memory of the network in keychain access, system preferences>network, configuring IPv4 manually, using DHCP and renewing DHCP lease, deleting the WiFi network in system preferences and restarting before making a new one.
Basically, everything i've read in forums, i've tried and nothing is working. Other than the methods i've seen, it seems to me that it's a problem with the router but as that was changed yesterday I don't see why it would be a problem.
Also, because there were a number of computers that had the same problem and the others have now been fixed, I don't understand...


Any more options would be greatly appreciated because though I can borrow other peoples laptops for internet, it would be much more convenient to use my own.


Also, is this a problem that will affect connecting only with that network or will it still be an issue connecting to other networks? If it's only on this network, I will worry less as in 3 weeks I will move home to England and not have to worry about this network again. I can probably survive 3 weeks without a connection here but will still be frustrated.

Sep 5, 2014 12:21 AM in response to EmConn

As I posted before, my description could have matched yours. For me, it turned out that I had a switch between the router and my Macbook (and other devices). All of them worked except the macbook. Swapping in another router cured it for everything except the macbook, Then I remembered the switch and power cycling that immediately fixed the error with the macbook. You must have at least one other friend with a router/swicth you can plug into to see if the problem is persistent on all networks.

Sep 5, 2014 12:50 AM in response to EmConn

Routers are connected to 2 networks, typically a WAN (wide area network-internet) and a LAN (local network). A switch is essentially a hub for connecting nodes on a network with more intelligence than a simple hub about what's hooked to each port. Most routers that are not server based have a switch incorporated in them so you can connect nodes (PC, printers, etc) to them directly but it is very common to have one or more other switches in a network between the router and your PC. In my case, the router caused a problem in the switch down stream from the router, upstream from my macbook. Since I had forgotten about that switch, I spend hours trying to find the problem on my macbook when a simple power cycling (unplug the power to the switch for a minute or so and then plug back in - do this instead even if the unit has a power switch) cured the problem.

Making a lot of configuration changes on the mac is risky because you do not know that something you tried hasn't broken the ability to connect as well and when you find the solution, you won't know it when you try it. Try to reverse anything you do that does not help before trying something else.

Sep 23, 2014 3:22 PM in response to joepark14

I had the same problem on just some of my networks (specifically at work) and it was very frustrating. I tried all the other solutions posted here and none worked. I am using Norton for mac and found that Norton Firewall was blocking the internet connection from my work's network. Goto Firewall Status in Norton and if you see a red X for your Network, if so, try clicking on this and "allowing" connections from this Network. This solved my problem, the other solutions on the page did not.

Sep 29, 2014 11:30 AM in response to joepark14

I have this problem today for the first time and I tried several solutions proposed here by other users but nothing worked.


What it worked was the following:

Network Preferences

Advance

TCP/IP

DHCP with manual address

Type an IP from other computer that is using the same network

Change the last digit of the IP you chose (two users don't use the same IP)

Nov 24, 2014 6:50 AM in response to joepark14

I fixed it very simply. None of the other fixes I found by browsing the internet worked for me and could have made things worse for me because I was deleting system information and going into Password Keychain and deleting stuff there. I was using the wifi supplied by the owner of the apartment and I was sharing it with other people when I started having the self-assigned problem.


I fixed the problem very simply by going to Network and deleting the problem Airport network and creating a new one. I did this by first deleting Airport in the left window (I have OS 10.6.8) by highlighting "Airport" and clicking on the minus sign below. This removed Airport from the list. Then I clicked the + sign and after a couple of seconds a small window popped up. It said select the interface and choose a name for the service. An airport interface came up as one of the choices without my having to do anything. I then named it "Airport 10". You can choose any name just not a name chosen before for an Airport network.


After that, I clicked "Create".


After a couple of seconds, the new network appeared in the left hand pane and the symbol next to it showed green indicating I was connected to the internet.


And the internet now worked.


You can do this any time you get the "self-assigned" message. I also fixed other network locations that had the Airport IP self-assigned problem. and they all work now when I use them.


So don't try anything else without trying my solution first as with my solution, you are not playing around with system files.


And if the problem crops up again, simply do the same thing. I actually first fixed the problem first at work using the wifi supplied at work but the fix also worked at home.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Self assigned IP address

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.