Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

AirPort - Self assigned IP address - no internet!

Thanks!

That's nutty, but it worked! Thanks!

AlBDamned said:
This is a very annoying problem that's just started happening on my leopard machine.

What you need to do is go into System preferences> Security>firewall then turn it off to "allow all incoming connections".

Then turn your airport off.

Then turn it back on again.

You should now be able to connect to the web.

Then you need to go back and turn your firewall back on (very important!).

Hell knows why this happens but it's yet another crap bug in Leopard.... :rolleyes:

Literally started happening for no apparent reason after three months.
Click to expand...
 
Hi,

I recently switched to a Cisco-Linksys WRT320N Dual-Band Wireless-N Gigabit Router. It worked perfectly fine during the first day, but it suddenly went down the drain after that. My 13" MacBook Pro's AirPort has full signal, but it has no internet whatsoever.

I've read tons of possible solutions for this one, but none of them seems to be working for me. I've reset my AirPort's preferences, 'flushed' all Firewall rules, etc. I have the exact kind of router as my cousin, but I never encounter a problem using the internet when I come over.

The range could be one thing, but I live in a two-story apartment and both my room and the router's located at the second floor. I doubt the router has this little range. When I walk from the router's location to my room, it's about 25 steps away. I go to my room, and there's no internet (but full AirPort signal). When I go to where the router is, the internet magically works.

Is there any way I could fix this problem? Any help would be very appreciated. Thank you!
 
OK, I just got past this thorny problem that apparently has quite a few different solutions by reconfiguring my router's wireless security option for "Cipher Type" from "Auto" to "AES" ("TKIP" was the other choice). Perhaps there's something goofy with the wireless cipher handshaking protocol.

Weird thing is that the "Auto" method worked fine on my Macbook. It was my MacBook Pro that was giving me all sorts of grief here.

My router is a Trendnet TEW-432BRP.

Hope this helps somebody!
 
Tried most of this before!!

G'day all, it's been a while since I was on here but this issue has been bugging me for some time now. Unfortunately, I have tried almost everything to fix it, I think the only one I haven't tried is the manual setting of the IP address, because I figure I shouldn't have to, it was working before it started happening. Anyway, most of the fixes I have read about and tried don't seem to line up exactly with how mine came about.
Let me tell you about it. I never turn my eMac off at the wall socket, ever, except this once, I also unplugged my Airport Express unit. When I fired up my eMac after the few days we were away, everything was wrong, pram battery was dead. No worries, just replace it, fixed the clock etc but Airport would not connect, self-assigned IP address. My wife's MacBook has no such problems, it connects fine (has the occasional dropout, similar issue??). Thus ensued a long and frustrating search, but as I say, have tried most of this stuff and now I just turn off the firewall, turn Airport off and on again, then reinstate the firewall, no probs.
Today, when I started it up, I happen to be sitting watching the screen and amongst the start up stuff saw a dialog box saying/asking to allow incoming connections for krb5kdc, which I knew a little about from my searching. I clicked the 'allow' button, three times mind you, and Airport connected without having to go through the routine. Is there something that I can invoke (say an Aplescript) that can pick up on this and fix it before the system decides to disallow incomings and thus self-assign an IP shutting down Airport? Thanks for any help, even if you can point me to a posting somewhere that addresses my particular issue.:confused:
 
i had this same problem with Leopard. I had to restart the router every time i wanted to reconnect to the network after waking the computer from sleep, that is until I downloaded the AirPort updates. Some problems persisted until Snow Leopard though, I'd recommend getting Snow Leopard if at all possible, it cleared up all of my Wi-Fi issues
 
So, did Apple...?

So, this begs the question, did Apple deliberately stuff Leopard to 'force' users to go to SL? I've been waiting for ages for a new update to Leopard so that it will fix the issues that 10.5.7/8 introduced, issues that were supposed to be fixes to, among other things, Airport. Just so you are aware and don't crucify me, I am not about to ditch my Macs, I still could not see me sitting in front of a PC:(. Long live Apple but please fix some things.
 
Some interesting observations.

Hi all,

since I last posted a response, I notice that I was the last one to post anything. This problem seems to be one that plagues a lot of people and there are many possible solutions, none of which have solved my situation.

But since my last post, I have observed some interesting things:

1. When I boot up of a morning, if, in the startup process, I get the krb5kdc and configd dialogue boxes to allow incoming connections and click them to allow, then my Airport/internet connection works fine first up;

2. If these dialogues don't appear in the startup process then I need to do the turn off/turn on again routine as described earlier and elsewhere on the 'net.

But recently, I have observed something very interesting:

3. The other morning and again this morning, when I didn't get the allow/deny dialogue boxes, I just needed to turn the firewall off and the connection was made, turned the firewall back on again with no problems.

Has anyone observed this on their systems and do they have a solution to this? Does this mean that the firewall has somehow become corrupt and, if so, what file needs to be fixed?

Thanks for any help or other observations.
 
Finally, some good news... for me.

G'day all, it seems that I'm the only one on this post nowadays, I hope that means that you all have your Airport issues sorted, but I guess not. Anyway, following on from my interesting observations posted previously, I have some good news.
For the past three days, I have booted up/logged on and found that my system is connecting to the Airport & internet without having to turn anything off and back on again, and getting a properly assigned IP address each time. Don't ask me what made the difference, I don't know, haven't done anything since my last post to change any of the functionality of the firewall/airport set up. I did download NoobProof to see if I could work some magic with it, but didn't really get to do too much with it and for the 3 or 4 days (or more?) that I've had it loaded before 3 days ago, it made no difference.
I don't think that was the solution in my situation, but certainly try it out if you think it might help in yours. NoobProof and WaterRoof are two similar?? projects for manipulating the IPFW firewall in OSX.
I'm sorry if I am not adding anything to help anyone else, but it seemed to come right by itself. Maybe I did something inadvertently to fix something but I don't know, I wish I did as I would pass it on to you all, I know how frustrating this issue can be.
Anyway, keep hanging in there, I'm sure there is a solution out there for each of you, just got to find it. I'll keep an eye on this thread to see how things develop. Cheers.
 
Au contraire; the problems still exist. I can't believe how long my subscription to this thread has existed.

For a while (across several MBPs) the issue seems to have gone away as local cafés stopped using the BitSurfr firmware that was having issues interacting with MBPs, and just recently - at work - have experienced exactly the same issue as in the beginning. (Shakes head)

I look forward to the decade where this thread dies, but I'm not holding my breath.
 
I am getting this issue on both my MacBook running snow leopard and my iPhone 4. At home both connect to my time capsule fine but at our caravan we have 2 wireless access points within range and both result in self assigned ip and an address 169..... on both devices.

I do not have any access to the access points so having to restart them or change any settings is not possible. They use WPA authentication.

I have tried just about everything on here except deleting prefs and flushing memory which I will try tomorrow. My iPhone is not jailbroken so that is not the issue but it is possible that someone else on the site has one that is. Although for both access points to not work there would have to be a jailbroken phone connected to each?

If anyone has any ideas please let me know. Or if there are any simple things I could ask the site management to try with routers it would be great

Thanks
 
well i spent best part of my sunday afternoon with this exact problem,


1. Go to Mac/Library/Preferences/SystemConfiguration
2. Delete the following:
a. Com.apple.airport.prefrences.plist
b. NetworkInterfaces.plist
c. Preferences.plist
3.Shut down computer
4.reset PRAM

didnt work, loaded up my windows pc and everything was working fine , ie net access etc,

Then I remember i downloaded some program called Noobproof a while ago,

I havent used it for ages and up until last night everything was working fine,

but as soon as i went into the noobproof settings and reset everything to default and used the settings in the program to uninstall the scripts everything started working again,

just find it strange how it blocked my internet with no input from me and like i said i hadn't used the programe for about 4 or 5 weeks
 
AlBDamned said:
This is a very annoying problem that's just started happening on my leopard machine.

What you need to do is go into System preferences> Security>firewall then turn it off to "allow all incoming connections".

Then turn your airport off.

Then turn it back on again.

You should now be able to connect to the web.

Then you need to go back and turn your firewall back on (very important!).

Hell knows why this happens but it's yet another crap bug in Leopard.... :rolleyes:

Literally started happening for no apparent reason after three months.
Click to expand...

Thank you so much! I just got a Macbook Pro and I couldn't figure out what the problem was. At first I thought it was the router but I now know it's Leopard. This made it work though! :) Thanks!
 
This work for me

jbatlas said:
Based on this article:

http://discussions.apple.com/thread.jspa?threadID=1654663

I opted to try using WPA authentication instead of WEP and that seemed to solve the problem for me.
Click to expand...

After many days trying all recipes in forums, etc. I entered my router, change the authentication type form WEB to WAP-PSK (in my case), change the password, save this settings. LISTO!
In Network preferences, advanced, cleared preferred networks, add one new, write name, choose security tipe (I selected WPA-personal), type the new password (the same I assigned in my router) and that was all. I get a correct DHCP negotiation and my NoteBook is now connected to Internet. Hope this help.
 
Had wrong WEP key

Just a quick note to say I had what looked to be a similar issue. When trying to access my WIFI I'd end up with a self assigned IP.

What I discovered is that it was the result of a typo in the password I used. My router lost power for a while and when it came back on OS X for some reason asked me to enter the password again (usually it just stores it and connects automatically). I had typed the password incorrectly. Rather than OS X telling me I'd entered the wrong password it would connect, and then do a self-assigned IP on me. Why it does not tell me I got the password wrong, I am not sure.

Anyway... I put in the correct WEP password and all was well again.

My mistake, and an easy solution. :rolleyes:
 
guess what...

so my battery died for my powerbook g4 15'' running leopard. It took me a good month to get a new one. Happy it works again, but Guess what... No internet, just like that. :confused:

self-assigned IP BS got me too. I've been figuring it out all day, checking out all solutions of forum topics like these, without any luck. gdmfsob.

just saying, any helping hands at all on this subject is still more than welcome these days, people still struggling with this issue !! I'll keep u guys updated anyways...

:apple: powerbook g4, 1,67Ghz, 2GB DDR2 SDRAM, running leopard 10.5.8.
 
I just started having the same issue out of the blue. I upgraded my router and everything was working great for about 2 days. Now I have this issue.
 
this worked ;-)

Thanks AlBDamned; what you suggested worked for my powerbook G4 when it wouldn't connect to the network

Tim


AlBDamned said:
This is a very annoying problem that's just started happening on my leopard machine.

What you need to do is go into System preferences> Security>firewall then turn it off to "allow all incoming connections".

Then turn your airport off.

Then turn it back on again.

You should now be able to connect to the web.

Then you need to go back and turn your firewall back on (very important!).

Hell knows why this happens but it's yet another crap bug in Leopard.... :rolleyes:

Literally started happening for no apparent reason after three months.
Click to expand...
 
AlBDamned said:
This is a very annoying problem that's just started happening on my leopard machine.

What you need to do is go into System preferences> Security>firewall then turn it off to "allow all incoming connections".

Then turn your airport off.

Then turn it back on again.

You should now be able to connect to the web.

Then you need to go back and turn your firewall back on (very important!).

Hell knows why this happens but it's yet another crap bug in Leopard.... :rolleyes:

Literally started happening for no apparent reason after three months.
Click to expand...

Thanks for that fix, it worked for me!

This has been so frustrating, it happened about a week ago and I had to take my MBP to Best Buy (had the 3 year extended warranty) and they tested it for two days and couldn't find anything wrong with it. They actually recommended a full wipe and restore which apparently wasn't covered in my warranty so they tried to charge me for it as well.

I said forget it and took it home and it magically started working again. It stopped working again today and so I googled the problem and found this thread. It's working so far, fingers crossed!
 
macbook connection

i googled my issue and found this site. wow a LOT of people with the same problem. My internet issues began with it dropping out, so i had to keep going through the set up and then it started only connecting for a few seconds at a time and then stopped connecting at all. I also have a DELL Laptop and my brother had a dell pc and my parents have other normal laptops that ALL work fine with my internet at home. I went to Apple shop, who suggested i turn off my firewall (which did not help) and set me up a new loaction which also did nothing. My mac would connect in the shop though which didnt help as they could not see the messages i got at home. Because is connected in the shop they said it must be an issue with my router at home, yet all other PCs work fine at home so it cant be the router! When I got home I saw it was sayin i didn't have an IP address. We have a sky router at home so its not a mac router.
So I came one here and took the suggestion of adding 1 to the end of my PC IP address and inputted it manually into my MAC. And it worked! How long for i dont know but it worked (and forewall is on too). So fate lot of use going to Apple was.
They MUST know about this problem if you have all been having problems and reported it to mac. I don't think I will buy a mac again to be honest. I have had a lot of hassle with mine. I have a Dell too anyways and I dont think MACs are worth 3x the price you pay for a Dell etc. I am so disappointed in it. Its 3 and half years old.
By the way we had changed nothing at home, no new router, etc. It just lost IP address and stopped working for no reason. Bizarre.
 
you know what, Albdamned's fix works but I still have to re-do it almost every time I switch wifi addresses or I restart my computer. Needless to say it got annoying, then I did another search and found that whoever updated their OSX 10.5.8 COMBO or whatever seemed to solve the problem. I downloaded the update and so far so good, it's worked for others so why not try. Might be the permanent fix:

http://support.apple.com/downloads/Mac_OS_X_10_5_8_Combo_Update

https://discussions.apple.com/message/11998534?messageID=11998534
 
The problem is different fixes worknat various times

It makes this hard to track down. I have Had the problem on my Air off and on for months. The last few weeks only at my local Panera in Cupertino. It persisted through the update from 10.6.7 to 10.6.8 last week. Currently the problem only occurs at that Panera, but has happened elsewhere, including home on many machines and even my iPad 2. :confused:

https://discussions.apple.com/thread/2140236?start=0&tstart=0

Offers some more fixes that sometimes work for some.
 
Alternative fix

Hi all,
My wife and I have been going through this same issue for two days. She called her tech support guy and he said:

1. Turn off the airport
2. Hold down the power button to power down the machine
3. Turn on the machine
4. Turn on the airport

And it worked! He explained, get this, that the machines sometimes carry too much static electricity and that interferes with the airport connectivity. Turning off airport and forcefully powering down the machine by holding in the power button discharges that electricity.

So if your firewalls are all disabled, and you are still getting this problem on your macbook, give this a shot.
 
I'll use this thread instead of creating a new one, since my problem is related.

I'm using a MacBook Pro with Snow Leopard, bought in February 2011. Today, I added a WPA key to my wireless connection in order to make it more secure. Since then, I'm experiencing the following issue : every time the computer goes to sleep (including by closing the laptop), or every time I switch from or to my Windows 7 partition via Bootcamp, I lose the connection, and have to restart the computer to get it back. Even then, I often have to disable/enable Airport after the restart in order to get the connection back.

Airport detects my wireless, connects to it (without me having to enter the password after the first connection), but the "self-assigned IP address" message shows up, as well as the little /!\ sign on my Airport icon, and I can't access the Internet.

My connection worked perfectly fine before I added the WPA key, which leads me to believe it caused the issue somehow. No update seems to be available for my programs. I tried switching the built-in firewall off and disable/enable Airport, as another poster suggested here, but it doesn't work. I tried resetting the PRAM - three times - but it doesn't work either. There are three other computers in my house, running Windows XP, and none of them seems to be having this issue. My Windows 7 partition does, as I said, which makes me think it's related to my MacBook Pro and not my router or Mac OS.

Would you have any suggestion ? Or previous threads I might have missed despite my search ? By the way, my ISP is a Belgian one, it probably wouldn't tell you anything, but for the record, I'm using a b-box2 from Belgacom.

Thank you (and forgive the possible grammar mistakes, I'm not a native speaker).
 
Last edited:
/!\

Is the very symbol that shows up when the self assigned IP problem shows up. Just this morning i had the problem on my iPad 2, but was at home and it cleared up by rebooting the router. That is not an option everywhere. I am at SFO now for a quick biz trip to seattle and can not take my MBA as i am not sure when it will have this problem. Most of the time it works. I too have tried all of the solutions mentioned in this thread, taken it to several apple stores and still no love. So instead of taking work machine, i a taking my personal MBP on this trip. Not ideal as it is a machine that has other uses at home, and the Air is a better travel machine in any case.

The air is 1 gen old, maxed out and running 10.6.8. It has had the problem across several OS version updates. Despite what you might hear, the problem is not your router, or your settings. Sadly i do now know what it is though.

If anyone has further suggestions, I would love some help with this. :( :confused:
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back