Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
SELF-ASSIGNED IP??? (ethernet)
- Thread starter rph105
- Start date
- Sort by reaction score
This problem STILL exists as of today in Leopard here. It just started acting up around the time of the last security update here (back in October 2009). Scanning through this thread, most of it is pure nonsense. The problem is 100% without a single doubt Leopard's retarded FIREWALL. After that security update, it started asking me permission to allow connections for things like nmbd and configd. It would ask this EVERY SINGLE TIME YOU RESET even though it was listed in the firewall's access list (Leopard just seems to ignore those much of the time as this is FAR from the first time an application listed there that keeps asking for permission despite being in the list). Allowing or not, DHCP no longer functioned. If I manually set the address, the connection would resume and work fine (except that SAMBA wouldn't work right AT ALL with my PC or Apple TV boxes running XBMC).
Somehow I got it to work with the the DHCP thing again, but I've been rebooting into Tiger to scan photos with Photoshop CS3 (because it's just plain unstable in Leopard by comparison and usually crashes or causes the OS to crash within a dozen photo scans or so in Leopard, but runs without issue in Tiger). Tiger's firewall isn't screwed up so it works perfectly fine (although its SAMBA setup SUCKS for enabling individual directories, etc. compared to Leopard's easy setup through the preference pane). In any case, when I booted back into Leopard, the connection died again and seeing as SAMBA won't work right with a manual connection for whatever reason, I proceeded to try and find the problem. Well, turning off the firewall (Allow all incoming connections) IMMEDIATELY resulted in DHCP on automatic suddenly connecting to my NetGear Gigabit-N router and everything was fine again. So it is clearly and without a doubt something screwed up in Leopard's firewall that is literally BLOCKING the ports for DHCP. I don't know how it got screwed up, but there is not easy "it just works" method to fix this problem in Leopard. The GUI stuff is just plain broken and since Leopard is now more or less officially DEAD (in favor of Snow Leopard), I would imagine this problem will NEVER *EVER* get fixed/addressed by Apple so those of us with a PPC machine doing server duty get to have compromised firewalls in order to maintain a proper DHCP connection. Thank you Apple.
What ticks me most about Leopard (other than its general instability on PPC machines compared to Tiger which was darn near rock solid and which has never been fully addressed and now never ever will be) is that they took a perfectly functional firewall and made it DUMBER and full of bugs. The thing just doesn't work right. It never has and it never will seeing as Leopard is dead now for all intensive purposes. Apple couldn't care less about fixing things like that and it's why Windows will clobber Apple in the long run despite Apple's superior GUI, etc. The network needs to "Just Work" and it's one area where OSX just fails miserably again and again and again. Samba support is poor at best. Even AFP fails sometimes for no apparent reason. I regularly lose a connection/share between my MBP running Leopard and my PowerMac running the same (to move data to the server/media drive). It'll just say "Share Lost" and then the share will never reappear until a reboot even though all the other directories on the SAME DRIVE still appear. BUGGY BUGGY BUGGY!
I've had OSX drop its connection on a router reset for no apparent reason (i.e. I'm accessing the router through say Firefox in OSX and I change a setting and hit update and it suddenly loses its connection; this has NEVER *EVER* happened when doing the same thing on my WindowsXP machine. The PowerMac kept getting "bumped" by my iPod Touch even for no apparent reason until I set up reserved addresses for all my connected devices (wired and wireless). It never bumped my PC or any other device. I couldn't for the life of me figure out WTF was going on. I'd turn on my iPod Touch and my PowerMac would lose its internet connection! I'd then find the iPod Touch on its address even though neither were reserved at the time and the PowerMac wouldn't find a new address or anything and it was the one that was hard-wired with Gigabit! WTF!?
The PowerMac wasn't the first machine on the IP address list either (the XP machine was). This stuff is just too weird. Admittedly, I have around 10 devices connected to my network and I have two wireless networks running (one is plugged wired into the switch of the other one) so it's not probably your typical home network, but that doesn't change the fact the only problem device on that network has been the PowerMac running Leopard. My MBP seems much more stable running its own version of Leopard. I'm guessing Leopard was much more thoroughly tested for Intel machines than PPC (just as Tiger was vastly more stable on PPC than Intel).
In any case, I don't know what the root cause of the firewall instability is, whether its the secondary firewall running in the background or Leopard simply doesn't properly store (or has somehow partially corrupted) a configuration file. It's just not obvious at all on that end. I should not have to disable the firewall (even temporarily) to get a DHCP connect to my router.
Somehow I got it to work with the the DHCP thing again, but I've been rebooting into Tiger to scan photos with Photoshop CS3 (because it's just plain unstable in Leopard by comparison and usually crashes or causes the OS to crash within a dozen photo scans or so in Leopard, but runs without issue in Tiger). Tiger's firewall isn't screwed up so it works perfectly fine (although its SAMBA setup SUCKS for enabling individual directories, etc. compared to Leopard's easy setup through the preference pane). In any case, when I booted back into Leopard, the connection died again and seeing as SAMBA won't work right with a manual connection for whatever reason, I proceeded to try and find the problem. Well, turning off the firewall (Allow all incoming connections) IMMEDIATELY resulted in DHCP on automatic suddenly connecting to my NetGear Gigabit-N router and everything was fine again. So it is clearly and without a doubt something screwed up in Leopard's firewall that is literally BLOCKING the ports for DHCP. I don't know how it got screwed up, but there is not easy "it just works" method to fix this problem in Leopard. The GUI stuff is just plain broken and since Leopard is now more or less officially DEAD (in favor of Snow Leopard), I would imagine this problem will NEVER *EVER* get fixed/addressed by Apple so those of us with a PPC machine doing server duty get to have compromised firewalls in order to maintain a proper DHCP connection. Thank you Apple.
What ticks me most about Leopard (other than its general instability on PPC machines compared to Tiger which was darn near rock solid and which has never been fully addressed and now never ever will be) is that they took a perfectly functional firewall and made it DUMBER and full of bugs. The thing just doesn't work right. It never has and it never will seeing as Leopard is dead now for all intensive purposes. Apple couldn't care less about fixing things like that and it's why Windows will clobber Apple in the long run despite Apple's superior GUI, etc. The network needs to "Just Work" and it's one area where OSX just fails miserably again and again and again. Samba support is poor at best. Even AFP fails sometimes for no apparent reason. I regularly lose a connection/share between my MBP running Leopard and my PowerMac running the same (to move data to the server/media drive). It'll just say "Share Lost" and then the share will never reappear until a reboot even though all the other directories on the SAME DRIVE still appear. BUGGY BUGGY BUGGY!
I've had OSX drop its connection on a router reset for no apparent reason (i.e. I'm accessing the router through say Firefox in OSX and I change a setting and hit update and it suddenly loses its connection; this has NEVER *EVER* happened when doing the same thing on my WindowsXP machine. The PowerMac kept getting "bumped" by my iPod Touch even for no apparent reason until I set up reserved addresses for all my connected devices (wired and wireless). It never bumped my PC or any other device. I couldn't for the life of me figure out WTF was going on. I'd turn on my iPod Touch and my PowerMac would lose its internet connection! I'd then find the iPod Touch on its address even though neither were reserved at the time and the PowerMac wouldn't find a new address or anything and it was the one that was hard-wired with Gigabit! WTF!?
The PowerMac wasn't the first machine on the IP address list either (the XP machine was). This stuff is just too weird. Admittedly, I have around 10 devices connected to my network and I have two wireless networks running (one is plugged wired into the switch of the other one) so it's not probably your typical home network, but that doesn't change the fact the only problem device on that network has been the PowerMac running Leopard. My MBP seems much more stable running its own version of Leopard. I'm guessing Leopard was much more thoroughly tested for Intel machines than PPC (just as Tiger was vastly more stable on PPC than Intel).
In any case, I don't know what the root cause of the firewall instability is, whether its the secondary firewall running in the background or Leopard simply doesn't properly store (or has somehow partially corrupted) a configuration file. It's just not obvious at all on that end. I should not have to disable the firewall (even temporarily) to get a DHCP connect to my router.
Firewall issues...
My friend's mac book kept getting disconnected from my network even though I had set her prefs correctly, after many fixes I did remember the firewall issue, the two firewalls integrated in Leopard conflict with one another, one of the hints pointed to doing a Firewall Rules Flush in terminal 'sudo ipfw flush' I think is the proper command but im not sure, I have to look at my notes, but I do agree that the firewall in Leopard is very unreliable unlike Tiger's firewall that was not the best but it was more or less comprehensible and not given to contradiction, also I did have to make sure that the clock in the router had the correct Time Zone and had the right time, improper timing with the device set off its connectivity. Thanks for sharing.
My friend's mac book kept getting disconnected from my network even though I had set her prefs correctly, after many fixes I did remember the firewall issue, the two firewalls integrated in Leopard conflict with one another, one of the hints pointed to doing a Firewall Rules Flush in terminal 'sudo ipfw flush' I think is the proper command but im not sure, I have to look at my notes, but I do agree that the firewall in Leopard is very unreliable unlike Tiger's firewall that was not the best but it was more or less comprehensible and not given to contradiction, also I did have to make sure that the clock in the router had the correct Time Zone and had the right time, improper timing with the device set off its connectivity. Thanks for sharing.
Solved Self Assigned Ip Issue!!!
I Had The Same Problem With My Brand New Imac. It Worled Fine And Suddenly It Started With The Self Assigned Ip Issue And Nothing Seemed To Fix It. I Was Not Able To Connect To The Internet.
I Found Out That My Wireless Router (2wire) Used A 64 Bit Encryption With A Ten Digit Password. Imac And Mac Laptops Use At Leat 128bit Or Another Better Security Protocol And That Is What Prevent The Computer From Connecting To The Internet.
The Solution Is Simple, You Have To Contact Your Internet Service Provider And Ask Them To Re-configure Your Wireless Router To Support 128bit Or The Other One Which I Do Not Remember The Name (it Is All Letters Pcv Or Something Like That) And As Soon As They Do That Tyour Connection Problems Will Go Away!!
I Had The Same Problem With My Brand New Imac. It Worled Fine And Suddenly It Started With The Self Assigned Ip Issue And Nothing Seemed To Fix It. I Was Not Able To Connect To The Internet.
I Found Out That My Wireless Router (2wire) Used A 64 Bit Encryption With A Ten Digit Password. Imac And Mac Laptops Use At Leat 128bit Or Another Better Security Protocol And That Is What Prevent The Computer From Connecting To The Internet.
The Solution Is Simple, You Have To Contact Your Internet Service Provider And Ask Them To Re-configure Your Wireless Router To Support 128bit Or The Other One Which I Do Not Remember The Name (it Is All Letters Pcv Or Something Like That) And As Soon As They Do That Tyour Connection Problems Will Go Away!!
Well, slightly different spin. I have tried to get my AWLL6075 (airlink101 Golden N) to work on my mini with my Time Capsule on a 2.4 N only network. None of the ideas worked - although it connects just fine with my Linksys WRT54. Interestingly enough, the 6075 also won't connect with the TC from a Windows PC either, nor my MB. It sees the network; but fails to establish a reliable connection; network prefs show either self-assigned IP 0r don't connect with manually assigned address. I can get a decent n signal as my airport express is flawless in the same location when attached to the mini.
I may try the Time Capsule with G enabled; but I'd really rather keep it N only and let the Linksys handle g connections.
I may try the Time Capsule with G enabled; but I'd really rather keep it N only and let the Linksys handle g connections.
possibles...
If you are running online games N is the way to go, I have read plenty of forums where the general working of and reliability of N is always sketchy, some say its buggy and not really ready for prime time others denote the hastiness of it's implementation before proper sound stability was obtained, if not G has always been reliable, note that trying different transmission channels also may eliminate interference issues specially if you are outputting diverse signals, go through the whole gamut of available channels (1-10) to see which one is more stable, also check the time-zone and make sure the time is accurate on your router if available, have your DNS numbers properly listed in your Network prefs pane, this information is provided by your router when you log into one of it's info pages. And last but not least; cordless phones have been known to cause interference issues with wireless signals, try shutting them down to troubleshoot the issue.
If you are running online games N is the way to go, I have read plenty of forums where the general working of and reliability of N is always sketchy, some say its buggy and not really ready for prime time others denote the hastiness of it's implementation before proper sound stability was obtained, if not G has always been reliable, note that trying different transmission channels also may eliminate interference issues specially if you are outputting diverse signals, go through the whole gamut of available channels (1-10) to see which one is more stable, also check the time-zone and make sure the time is accurate on your router if available, have your DNS numbers properly listed in your Network prefs pane, this information is provided by your router when you log into one of it's info pages. And last but not least; cordless phones have been known to cause interference issues with wireless signals, try shutting them down to troubleshoot the issue.
Thnaks, I'll try that. Although G so far has been fast enough for video streaming, so I'm in no rush. Plex with a 30 sec buffer has run without a hitch so far.
That's neither "simple" or a solution given my Mac is connected via Gigabit Ethernet and so any idea this has something to do with "wireless" is right out the window. The problem is the Mac's firewall. Something is getting corrupted and/or altered somehow so that the "exception" list simply doesn't work or is getting blocked by a secondary "command line" firewall that there is no simple way to access. The mac is supposed to be EASY to use, not trip you up with crap in the background the average user isn't even aware of. The fact that Apple just IGNORES this problem instead of fixing it makes the situation 10000x worse. They clearly do not CARE about the problems of the average user and don't do anything until half the Mac Community whines and cries at them (like with that iPhone discount fiasco a couple of years ago).
The ONLY solution I could find that fixes the problem without incident (i.e. having to manually turn something on/off on every reboot) is to disable the firewall entirely. That works, but it defeats the whole darn point about having a firewall in the first place and makes Mac security a complete and total utter JOKE. People talk about Windows security issues and the like, but the fact is Windows is a 100x more secure than the Mac will ever be because it HAS TO BE (i.e. Macs just don't get attacked the way Windows machines do). The truly SAD thing is that the firewall in Tiger works PERFECTLY on the same machine (i.e. I have OS9, Tiger and Leopard all installed on the same PowerMac). My MBP so far does not have this issue and it's running the same version of Leopard. My PowerMac didn't always have this issue so clearly a setting has been corrupted/changed somewhere/somehow and there is no obvious way to fix it that I've seen anywhere so far except to disable the Firewall entirely or put up with having to reset it EVERY SINGLE TIME YOU REBOOT (meanwhile any programs automatically running at boot will be whine and moan and even not function correctly UNTIL you fix it because they cannot access the Internet (i.e. pop-ups galore come up on my machine from everything that is trying but failing to access the Internet; they don't even know there is a problem beacause OSX assigns that phony I.D. which makes them think everything is hunkey-dorey when it's not (i.e. it says "CONNECTED" in the Internet panel, but it cannot do anything because it's not REALLY connected if the I.D. is 100% BOGUS and made up by OSX (i.e. self-assigned). This is not a connection problem. It's a firewall setting problem that Apple will not acknowledge even exists and clearly people with both Intel and PPC machines and the latest version of Leopard (Snow Leopared also in some cases?) have run into it.
issues and headaches...
This thread comes and goes etc, the secondary firewall used to be disabled by going into Terminal and typing ipfw flush, I don't know if that still works in SL, the frustration is evident but never the less statements like "Apple does not care" could be very well be true, This leaves several avenues to proceed onto: 1) we revert to what is more stable (in many cases a proven OS like Tiger) 2) we implement an organized method of upgrading and testing before we change drastically our already perfectly-running systems, 3) we switch to Windows (not an option for me) but we need to be realistically cold and admit that if its not working avoid giving yourself more trouble. If the statement:"Apple does not care" is true then that leaves the following options as well:1) we rely on the forum community to find answers,2)we take the Mac in question back to Apple to see a Genius agent and 3) we sell our macs on eBay etc. There is a lot of anger and frustration in these posts, these posts are read by good Macrumors people and not by Apple, and to write indignantly and such is highly unproductive, you may find that the more detached you are the faster people respond, Its not recommended that you chastise the very people that are trying to help you.
When I have a little bit of time I will peruse through the thread and I will post several things Im trying to remember, because we had this issue not too long ago with Tiger, ethernet disconnections etc. I will look through my document files for possible solutions, stay tuned.
This thread comes and goes etc, the secondary firewall used to be disabled by going into Terminal and typing ipfw flush, I don't know if that still works in SL, the frustration is evident but never the less statements like "Apple does not care" could be very well be true, This leaves several avenues to proceed onto: 1) we revert to what is more stable (in many cases a proven OS like Tiger) 2) we implement an organized method of upgrading and testing before we change drastically our already perfectly-running systems, 3) we switch to Windows (not an option for me) but we need to be realistically cold and admit that if its not working avoid giving yourself more trouble. If the statement:"Apple does not care" is true then that leaves the following options as well:1) we rely on the forum community to find answers,2)we take the Mac in question back to Apple to see a Genius agent and 3) we sell our macs on eBay etc. There is a lot of anger and frustration in these posts, these posts are read by good Macrumors people and not by Apple, and to write indignantly and such is highly unproductive, you may find that the more detached you are the faster people respond, Its not recommended that you chastise the very people that are trying to help you.
When I have a little bit of time I will peruse through the thread and I will post several things Im trying to remember, because we had this issue not too long ago with Tiger, ethernet disconnections etc. I will look through my document files for possible solutions, stay tuned.
Self-Assigned IP Issues
Macbook Pro
Mac OS X
Version 10.5.8
Hello,
I came across the same problem the other day. All of a sudden I couldn't connect wirelessly to my internet or my neighbors. So I went to network preferences to see what was wrong and noticed that under Airport it said "Self-Assigned IP". Why is that?
Also my IP address starts with 192 if that matters.
By the way, I actually got it to connect after restarting my router, but I'm not able to connect it anywhere else like I used too. The only thing is that whenever I close my computer or if it just shuts off, I lose my connection meaning that I have to restart my router all over again (every time). Then just today when I was connected, I got a random error saying that there's something wrong with my connection and then my internet just stopped working. I don't know whats going on because my brother has a mac too and his works just fine. Its only my computer that's having problems.
Why is that? What should I do?
Macbook Pro
Mac OS X
Version 10.5.8
Hello,
I came across the same problem the other day. All of a sudden I couldn't connect wirelessly to my internet or my neighbors. So I went to network preferences to see what was wrong and noticed that under Airport it said "Self-Assigned IP". Why is that?
Also my IP address starts with 192 if that matters.
By the way, I actually got it to connect after restarting my router, but I'm not able to connect it anywhere else like I used too. The only thing is that whenever I close my computer or if it just shuts off, I lose my connection meaning that I have to restart my router all over again (every time). Then just today when I was connected, I got a random error saying that there's something wrong with my connection and then my internet just stopped working. I don't know whats going on because my brother has a mac too and his works just fine. Its only my computer that's having problems.
Why is that? What should I do?
Can't say why your machine is setup with a self-assigned IP, but it's not the default. Mine is self-assigned by choice though. To get your machine to connect to other routers you'll need to turn off self-assign, because you'll need to rely on the DHCP (which dynamically picks an IP for you that will work on the router). You likely can switch to DHCP for your home use as well.
Fixed my issues!!
This worked great for me. I was having the same issue as everyone else. I tried all kinds of things before finding this and things are good to go now! The only thing I did different then the above is Network>Airport>Advanced>TCP/IP>Renew DHCP Lease and then turn on and off my Airport. Oh and im using Leopard.
This worked great for me. I was having the same issue as everyone else. I tried all kinds of things before finding this and things are good to go now! The only thing I did different then the above is Network>Airport>Advanced>TCP/IP>Renew DHCP Lease and then turn on and off my Airport. Oh and im using Leopard.
pleasssseeeee help me. i'm extremely desperate.
i'm college student in my dorm. internet was working fine for 2 months until it just up and decided to self-assign its IP address. do not get wireless in my dorm, i have been trying everything for two weeks to fix this to absolutely no progress at all.
i have tried:
updating software (now running 10.6.4)
installing applejack & running it
resetting PRAM
firewall was never on in the first place
allowing access to keychain
deleting system configurations, network pref, etc
flushed ipfw
repaired disks
renewing lease, unchecking passive, EVERYTHING.
nothing has worked for me at all. every time i hook up to ethernet, it's the same thing. i've tried using my roommate's cable and jack, same thing. her laptop however (not mac) gets internet fine no matter what cord or jack she's using. i went to the apple store and they said there was nothing wrong with macbook, and to call university IT. called university IT, they said there was nothing wrong with the router or anything else, they even sent someone over to physically inspect the jacks and still nothing works.
PLEASE HELP ME.
i'm college student in my dorm. internet was working fine for 2 months until it just up and decided to self-assign its IP address. do not get wireless in my dorm, i have been trying everything for two weeks to fix this to absolutely no progress at all.
i have tried:
updating software (now running 10.6.4)
installing applejack & running it
resetting PRAM
firewall was never on in the first place
allowing access to keychain
deleting system configurations, network pref, etc
flushed ipfw
repaired disks
renewing lease, unchecking passive, EVERYTHING.
nothing has worked for me at all. every time i hook up to ethernet, it's the same thing. i've tried using my roommate's cable and jack, same thing. her laptop however (not mac) gets internet fine no matter what cord or jack she's using. i went to the apple store and they said there was nothing wrong with macbook, and to call university IT. called university IT, they said there was nothing wrong with the router or anything else, they even sent someone over to physically inspect the jacks and still nothing works.
PLEASE HELP ME.
Have you tried using DHCP with a manual address assignment? This used to fix my problems when it went haywire here under Leopard. If that went wonky, I would set it back to automatic. Basically, it didn't seem to like the Leopard firewall on resets despite it being set up properly. Turning it off seemed to fix things here and I see you never turned it on, but something could still be amiss. I don't think renewing the DHCP lease helped when that acted up, so give it a try. It couldn't hurt. You can always put it back on automatic.
I dual boot Win 7 and Snow Leopard. I have this problem on both OS. My recent solution is to turn off the computer, then turn off the on/off switch that is on the back of the computer, and wait about a minute. Then I turn it back on and boot. That seems to be fixing the problem for both OS. Perhaps rebooting twice helps. A restart does not clear all of ram, maybe that is a reason, or it is just random luck. I will soon try Lion and see if issues are resolved.
My first post was from Windows 7. This post is from SL. I did not boot twice, but turned off machine from Windows, then turned off on/off switch on back of computer, waited a minute, and booted into SL, where internet now works. GA-X58A-UDR5 revision 2, 12 GB MHz 1600 DDR3, i7-950, GT 9600 1mb, Corsair 650TX psu, Haf 932 Cooler Master case.
My first post was from Windows 7. This post is from SL. I did not boot twice, but turned off machine from Windows, then turned off on/off switch on back of computer, waited a minute, and booted into SL, where internet now works. GA-X58A-UDR5 revision 2, 12 GB MHz 1600 DDR3, i7-950, GT 9600 1mb, Corsair 650TX psu, Haf 932 Cooler Master case.
Last edited by a moderator:
For those who may come across this forum / thread in regards to having this very same issue, this is NOT router related but OS X SOFTWARE RELATED and, most are not thinking here and remain focused on a router problem as the root cause for failure. Such is not the case.
I've just encountered this after having a power supply go out on my Mac pro. Now, the hard drive that was mounted and operational during the power spike that took out the power supply has no network connection. However, ALL other drives (WIN XP, MAC HD CLONES) work fine using the same hardware setup and the same exact settings. It IS NOT router related but software related to where, there's a corruption of the software that needs to be repaired.
I found this out after running Tinker tool and, it reported that the OS was damaged. Most likely because of the crash when the power supply went out.
SUMMARY: I had net connection. The power supply went out. The OS got trashed and, no network connection upon installation of new power supply.
By confirming on three other backup drives IN THE SAME MAC PRO running 10.5.8- off the same Ethernet port, using the same exact setup and same router config file / settings, I have come to the conclusion that it is software related in OS X that leads to having a self assigned IP address and NOT ROUTER NOR HARDWARE based as the root cause for failure in my case.
I too, am hunting for a Terminal Fix to resolve this. Trashing PLIST Files, assigning manual addresses, re-booting the router etc etc, did not resolve the issue in my case at all.
WHile TRUE - a router can impose or induce the same failure, in this thread, it sounds as if lots of folks have the same issue as I do to where, the software is either corrupted or damaged to some extent.
EDIT: 12-12-2010. In my case, what had happened, was, corruption of the FIREWALL settings may have been the root cause for self assigned IP address.
WHAT WAS DONE:
By changing the selection from the third option "SET ACCESS...." to "ALLOW ALL..." etc, I was able to receive an IP address from the router immediately.
After discovering this, the setting was put back to the way I had it before: "Set Access for...." etc. Well, after leaving the machine on all night, in the am, it was noted that, there was no connection again.
The setting was changed back to the first option to "ALLOW ALL" etc, and, immediately, an IP address was assigned. After leaving it set to that setting for a while, (week) I have set it back to the last option and, so far, after two days, it hasn't reverted back to shutting off the connection.
I will report back if this is still an issue or not for me. END EDIT.
12-13-10: Problem came back. I had been on Paypal and closed and relaunched the browser and lo and behold, no network connection and, yet another self assigned IP address problem. I simply went to the firewall settings and changed it and, again, connection was restored without issue. There's some firewall issue on my machine that keeps hosing up. I'll get to the bottom of it soon enough now that I know where to start looking.
Last edited:
I seem to be having a variant of this problem and am hoping someone can help.
My imac running Leopard connects fine to internet when connected directly to cable modem. When i insert an Airport Extreme and run LAN ethernet cable to imac it reports "no ethernet cable connected". The airport is functioning properly (other devices on network work fine - all wired as I have not set wireless up yet as the imac is the only real computer in network), the port on the airport for the imac is fine, the ethernet cable is fine. The moment i connect the imac back to the modem directly it pulls an IP (and always the same one). Likewise, if i connect a laptop to the ethernet connection that the imac won't see, it works. So in short, the independent components work, but the imac refuses to see the ethernet connected from airport.
It seems that it is stuck on the one IP and won't pull a new one.
Have done the following:
1) reloaded (archive) OS X.
2) did the terminal command "sudo ipfw flush".
3) Firewall is set to "Allow all incoming connections"
4) Tried resetting PRAM (should it acknowledge this is done? - i pressed keys at startup no no indication of a reset)
5) Refreshed DHCP lease when connected to both the modem directly (still keeps old IP) and the airport (nothing happens).
6) Tried doing DHCP - Manual address by picking an IP one up from an IP an internet connected TV on network pulled - nada. Have not tried complete manual settings (gateway, dns, etc).
Called apple and that was a complete waste of time. They say hardware issue and bring to store - makes no sense as (a) airport works (b) imac works fine when connected directly.
Any help would be very much appreciated!
My imac running Leopard connects fine to internet when connected directly to cable modem. When i insert an Airport Extreme and run LAN ethernet cable to imac it reports "no ethernet cable connected". The airport is functioning properly (other devices on network work fine - all wired as I have not set wireless up yet as the imac is the only real computer in network), the port on the airport for the imac is fine, the ethernet cable is fine. The moment i connect the imac back to the modem directly it pulls an IP (and always the same one). Likewise, if i connect a laptop to the ethernet connection that the imac won't see, it works. So in short, the independent components work, but the imac refuses to see the ethernet connected from airport.
It seems that it is stuck on the one IP and won't pull a new one.
Have done the following:
1) reloaded (archive) OS X.
2) did the terminal command "sudo ipfw flush".
3) Firewall is set to "Allow all incoming connections"
4) Tried resetting PRAM (should it acknowledge this is done? - i pressed keys at startup no no indication of a reset)
5) Refreshed DHCP lease when connected to both the modem directly (still keeps old IP) and the airport (nothing happens).
6) Tried doing DHCP - Manual address by picking an IP one up from an IP an internet connected TV on network pulled - nada. Have not tried complete manual settings (gateway, dns, etc).
Called apple and that was a complete waste of time. They say hardware issue and bring to store - makes no sense as (a) airport works (b) imac works fine when connected directly.
Any help would be very much appreciated!
Self Assigned IP
I encountered this problem today, The Macbook Pro worked on the internet until the afternoon. All the settings look correct. All the other computers work on the network. I even plugged in a USB network adapter into the Macbook Pro and it picked up the IP address from the router, so I don't think rebooting the router would help. I am wondering if the nic card got damaged somehow.
I encountered this problem today, The Macbook Pro worked on the internet until the afternoon. All the settings look correct. All the other computers work on the network. I even plugged in a USB network adapter into the Macbook Pro and it picked up the IP address from the router, so I don't think rebooting the router would help. I am wondering if the nic card got damaged somehow.
Fix!
Follow these steps:
System Preferences > Network > Select Airport on left pane > Advanced > TCP/IP > Renew DHCP Lease.
Tip: Make sure the wireless network you are having the problem with is selected.
Thats it!
Follow these steps:
System Preferences > Network > Select Airport on left pane > Advanced > TCP/IP > Renew DHCP Lease.
Tip: Make sure the wireless network you are having the problem with is selected.
Thats it!
This issue just came up on my 2009 Mini this morning - ethernet port. It has been working via ethernet flawlessly for months.
- Running 10.5.8
- Tried rebooting and resetting router
- Did a Command-Option-P-R reset
- Firewall is disabled
- Tried Advanced-->Renew DHCP
- If I unplug the ethernet cable the network settings detects no cable
- Tried deleting com.apple.alt.plist but there is not one (also tried this through Terminal)
- Wireless works
Ideas??
- Running 10.5.8
- Tried rebooting and resetting router
- Did a Command-Option-P-R reset
- Firewall is disabled
- Tried Advanced-->Renew DHCP
- If I unplug the ethernet cable the network settings detects no cable
- Tried deleting com.apple.alt.plist but there is not one (also tried this through Terminal)
- Wireless works
Ideas??
i had the same problem after upgrading to lion.
what worked for me was to duplicate the service. one for a general use (like in a cafe or someone else's house) and one for my home wireless. it seem to work.
hope that helps!
what worked for me was to duplicate the service. one for a general use (like in a cafe or someone else's house) and one for my home wireless. it seem to work.
hope that helps!
Thanks for the suggestion. Unfortunately I have tried that as well and it didn't work either.
I've also tried deleting some firewall and network .plist files and rebooting to force the system to produce new versions. That hasn't worked either.