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

SELF-ASSIGNED IP??? (ethernet)

Connectivity...

I just looked at the firewall logs and it registered the folowing message😀ec 19 21:40:25 Mac-Mini Firewall46: Deny configd data in from 192.168.0.1:67 uid = 0 proto=17
The IP address above is my wireless router's address. so the firewall is indeed blocking the connection from my router.
you may obtain this information by going to System prefs>security>Firewall>Advanced>enable login.
I found this hint on how to disable the blocking, Im testing it now so look out for further posts:
http://discussions.apple.com/messageview.jspa?messageID=5993303&stqc=true
Also macrumors has posted that Apple has seeded to developers an update (10.5.2) standing at a titanic 350Mbs
Also guys and gals thanks for the support and hopefully we can come to solutions to this dilemma
 
Also...

Another hint...
Is to open keychain Access and by selecting your network password>select access control and set it so it could be accessed by all applications.
Also I set the computer to sleep and it regain the connection on its own, maybe its as simple as this?
 
another thing...

Update and an old hint...
The connection had no problems, when I would put it to sleep and wake it up it would find the appropriate network, except when the computer went to sleep on its own, then upon waking it, it would not find the network, there was something else missing, since we all have narrowed down that one of the connectivity issues (Wire and wireless) is due to a firewall anomaly It actually made me remember that early Panther 10.3 had a Firewall issue as well, we could not alter the firewall settings and ports because the feature was locked or greyed out, so in a forum like this one it was figured out that Panther had by default 2 firewalls active: (ipfw) and the one from Sys Prefs, this little bug could of creeped out again in Leopard, so I managed to input in the Terminal App the following command:sudo ipfw flush , entered my password then input y for yes. this flushes any rules set by the 'other' firewall, This could of been creating conflict by blocking the router's connection protocol. If we set rules with one it would be difficult to set rules for the ipfw that I believe it only accesible through Terminal, ipfw as we've seen in Console still has it own log file. After I did the flush command I restarted and tested to see if it retain the connectivity, then when the computer fell asleep on its own, it did reconnect to my network!, after several restarts it connected and when I put it to sleep manually it reconnected also. I wont cry Voila just yet, but I would like to read of others trying these hints.
 
Overnight...

I left the computer to sleep on its own, and this morning my mini lost connectivity, I went to test my laptop and it picks up my network instantly.
So im back to square one but I do feel that answer is closer than before.
 
So, got on the horn with Apple again....long story short, they attempted to transfer me to a engineer, and after 30 minutes I gave up. So...I then power cycled everything *AGAIN* and the connection then again worked. That frustrated me to no end, there is NO WAY I am going to reset my entire network every time I want to connect my MBP on my network. So...I flashed the firmware on both my wireless switch and my router, it so happens that my router's firmware upgrade listed unspecified DHCP fixes in the upgrade (Could it be????).

The most frustrating thing I found was that my connection works just fine at work (I maintain a 12,000 node residential network on a University campus), and I maintain several different types of connections there (Wireless with no encryption, WEP, WPA2, WPA, Enterprise encryption, local encryption, wired etc.). Everything works fine there. Its after a few days of coming back and forth that the connection at home just craps out, mind you when this "problem" occurs my other machines running Tiger and XP are connecting just fine both wired and wirelessly. I am hoping the firmware update did the trick. I would suggest that any of you with this same problem try the firmware upgrade. To me it seems that Leopard is just unable to accept DHCP offers from older routers (whatever "older" means), for whatever reason. Without speculating too much, it could be just the way the REQUEST, OFFER, ACK is used by older routers, perhaps the new firmware addresses this? Now, I never did a packet capture or got geeked up enough to plow through DHCP logs on my router, but it is working now. If I have problems again then I will plow through the logs (trying to avoid that if I can...I hate logs).

Oh, I almost forgot...my favorite part of the tech support conversation was when I told the tech all the things I had already done to troubleshoot the problem, he paused, and said "Gee, you seem to know what you are doing, I really don't know what to do next *pause*...have you ever thought about going back to using Tiger?".... $250 for three years of Apple Care for that? Thanks, I'll figure it out on my own. I guess that $250 covers hardware repair then right?

I'll keep you updated.
 
Logs...Firewall Logs...even worse...

my firewall log read:
12/20/07 8:41:13 AM com.apple.launchd[85] ([0x0-0x30030].com.opendoor.doorstopx[370]) Exited: Killed
12/20/07 8:42:13 AM Spotlight[92] Invalid kMDItemPath for DoorStop X 2.2

This was a leftover from a Firewall app called DoorstopX, that I deleted when I was troubleshooting the connectivity issue, under the library>application support I found the Doorstop deamon, this even when thhe app is trashed it keeps on working, still theres no proof that this makes the connectivity crash but I wanted to test it in a non-contaminated manner so I left the computer to sleep on its own, it went to sleep and it reconnected fine, this test was after I deleted this deamon, now im back to test mode, I will let it sleep again, go to work and when I get back I'll see if it reconnects and see if long term sleep affects it, it could be that upon self-sleep it does not log out the connection, thus causing the drop.
 
A general commentary...

I've been keeping up with this issue and I've been also tracking the Apple Supports forums as well, I believe that the issue is starting to point out towards Leopard's hastily designed Firewall, the combination of System Preferences not retaining settings and configurations, the Utility Disc App that seems that its been dumbed down in this iteration, unable to fix certain permissions therefore bugs and anomalies never go away, the inability of Leopard to discard old caches that truly affect system performance, the ipfw (a secondary Firewall?) which I believe is an old Panther app and bug that's back?, A Keychain Access App. that maybe prone to errors, my laptop is different, why? could it be that the intel version of Mac OS X has slightly more glitches? you also need to remember that Apple is new at developing for intel processors, and its a good possiblity that they may have overlook a lot, so be patient and see if the upcoming update can resolve our woes or if collectively we can come to various solutions.
 
ipfw: the invisible culprit...

I had a reply from the Apple Support forum that confirmed for me that Leopard indeed has a secondary Firewall, The Infamous ipfw! the same one that showed up in panther, well it occured to me that if its set to a default setting how are we to now what it denies or allows access to? your router's ip address may be being denied connection because ipfw is set to a specific address different from the Systems preference Firewall. How do we check its configuration? do the following: in Terminal type: sudo ipfw list _then enter
in one of the lines it shows what ip addresses are being allowed, like this:"allow any from 192.168.0.0 to 24" if this is different from your router then flush the rules with the following command: sudo ipfw flush _then enter
it should configure an address closer to your router's. check to see if the connection behaves as it should.
 
ipfw list returns 65535 allow IP any to any.....NOPE, doesn't solve my problem.

FWIW, I came home tonight, 169 address again, power cycled the routers AGAIN *sigh*

Also called MAC support AGAIN, they have nothing *sigh*
 
issues...and testing...
So far so good, I have not lost connectivity since last I posted, I am testing a new account and its also running well, I believe that migrated accounts transfer poorly under this iteration of Leopard, mainly because of the transferred prefs, unresolved permissions and caches. Once you get over these small hurdles it seems to open the time to keep on testing other performance related matters, I think we must abandon the notion of carrying over our prefs to a system that likes to write files under it's own environment.
My compilation of fixes include the following if not already listed by others: Turn off ipv6, in SysPrefs>energy saver: turn off "put disc to sleep", flush the ipfw, under the Firewall app. (under essential or specific items)include to allow widgets the need the internet, browsers, messengers, mail clients,quicktime or any video players. under the network pane input the dns numbers, also I found this old hint from macosxhints to make system prefs remember:
"Mac OS X Networking Problems? Try deleting these preference files
We previously noted this procedure as part of a workaround for users who were unable to use AirPort functionality after applying one of Apple's firmware updates.
MacFixIt reader Colin writes "I had a bizarre problem where my network settings were screwy. Although I don't use it PPPoE was checked and every time I unchecked it, it would re-enable itself."
If you are experiencing a problem similar to this, or an issue where Network Preferences cannot remember other settings, delete the following files using the Terminal's "sudo rm" command:
/var/db/NetworkInterfaces.xml
/var/db/SystemConfiguration/*.xml
(jan 2003, issue with panther)
 
Hi All!

I just wanted to share my story of this problem and what I did to fix it. Hopefully it will help someone.

I have a Power Mac G5 (dual 1.8) a Dell Laptop, and a new (Intel) Mac Book connect to my network. The Power Mac is where my internet problem was and it was connected to a Linksys router (the one with the built in 4 port switch). I was not able to get an IP address from the wired connetion.

The dell and the Mac Book both connected to a Cisco AP that is connected to my Linksys wired router. The Cisco AP has DHCP disabled so that the Linksys router hands out the IP addresses.

This problem started for me about the same time as we had an ice store that caused many power outages (ie light on for 5 minutes, then off again all night). My Power Mac was connect to a UPS but the network was not. I figured that the power outages could have somehow cause a power spike that killed my built in network card.

To solve this proble I went out and bought an airport express card and everything worked perfectly, untill last night. (It had worked just fine for about 2 weeks). I was ready to buy a new Power Mac untill I read this thread.

I went into network perfs and told the firewall not to black anyhting and both my wireless and wired connections came back.

Hope it help! If anyone wants more specifics on my setting or anything let me know. I am glad to help where I can.


Doug
 
Hi wondered if anyone has anymore news about this. I posted a topic earlier today with an issue, and just found this thread in google and think it might be the same problem I have a few added variations;

ethernet wise it states its unplugged for ages then after leaving it alone for an extended period sometimes a while sometimes a very short time it connects directly or i get the whole self assigned ip address thing.

if it can connects to the wifi it seems to work, i think this could be a range issue as the signal is off and on. But usually use the wire because of this very thing, wifi has always been dodgy cause of range.

Using a netgear router. I am writing this on my ibook with leopard and doesn't seem to be effected and strange have been running leopard since it was released on my imac until yesterday had no problem. Also tried taking it to the apple store and worked there however also did the cable unplugged for a while until it suddenly picked up, worked straight off with wifi. I questioned the delay and the guy said that sometimes happens and blamed it on their network. Reformatted the machine and same on off connection.

Seems ridiculous...Anyone know when this update will come? Is it worth just rolling back to tiger now? Really not great timing got so much work on and have wasted now most of two days trying to work this out!
 
Connectivity

When you installed Tiger did you do all the updates on it? are you running 10.4.11 ? because Tiger itself had some connectivity issues within the first iterations. I have noticed also that the network settings are not as robust as they should be, they are very meticulous for each type of setting or connection, if you select the ethernet connection you must bring this setting all the way to the top of "selected services" and delete the rest for that particular setting, if you are connecting via wireless then do a location like:"wireless home" or "wireless work", if ethernet then "ethernet home" or "ethernet work" etc, whenever you establish these settings for the first time in the network settings you need to restart the computer and if posssible the router...avoid the 'automatic' set-up... also in the keychain app, there's a function where upon you can check for its stability (keychain first aid) try and see if there's an issue with the Keychain Access app.If I think of anything else i will post it
 
I am still having the same problems with the MBP wired and wireless. For a week I will have no problems, but this weekend every time I went o use my MBP I had to go down in the base ment and reset the router and the AP. Since my last post I upgraded my other two macs (Intel iMac and a quicksliver) to Leopard, the iMac uses wireless and the quicksilver is connected hardwire. Neither of these machines have any problems, they retain IP addresses (both are configured to static addresses and do not dynamically pull an address like my MBP). I can not configure my MBP that way due to the fact I move from network to network, and besides I tried that and even with DNS and router defined I could not get off of my network (as stated before).

I have a call into Apple Care still but of course I have heard nothing.

Still looking for the answer. Hopefully the promised 10.5.2 update will have a fix even though it seems that no one at Apple recognizes that there is a problem.
 
well i've had a very similar problem. i had this problem with an Airlink router, and i took it back for a belkin router, but am having the same problem with it.
 
my solution

For those of you still having trouble with airport after installing leopard, the problem seems to lie in the timeout settings configured in the new OSX operating system. It seems that the reason airport switches to self-assigned IP is that the operating system has a really short search time for an IP and DHCP froma wireless router. still no real solution from Apple but i have spent the last week trying to fix my own computer since Apple has been unable to help. i Have tried everything from renewing the DHCP to even entering my own IP. i even changed routers at one point just to make sure. So finally, i went into the network preference pane, and clicked ASSIST ME. I then went to Assistant, came up with a random location name, and chose the router i had set up in my dorm. after a short spinning of the pinwheel, the Airport changed to connected and the dreaded self-assigned IP address is gone. My Internet works now regardless of whether it is plugged in or running on battery and works after waking from sleep. Not sure if this will work for all but have used this method for four other people in my dorm with the same problem
 
It appears as though it only happens with certain models of computer/airport... I have a "new" core 2 duo MBP and I have problems with both wired and wireless on that machine but my "old" iMac 1.8 core duo, never has the problem wired or wireless.

Based on my experiences and testing I am 99% sure it has something to do with the hardware/software combo in the affected mac, and nothing to do with actual DHCP from the router. I have removed and added points of failure and it all comes down to the combination of my MBP and Leopard.

Core 2 Duo 2.16 MBP and Leopard= problems with 169 address (both when wired and wireless from time to time)
Core 2 Duo 2.16 MBP and Tiger (prior to upgrade)= no problems
Core Duo 1.83 iMac and Tiger= no problems
Core Duo 1.83 iMac and Leopard= no problems
G4 933 Quicksilver and Tiger= no problems
G4 933 Quicksliver and Leopard= no problems

The newest item I have added to my test list...I just changed my network log-in in keychain to allow all programs (as posted above by Mlobo01 in #52)...so far so good (48 hours later), we will see how it goes.
 
So... a week later and still running. It looks like this problem is directly related to the permissions listed in the keychain as stated earlier.

I was able to speak with a Apple Product Specialist today (after being on hold for an hour), and it seems that he agreed that that was the problem. He stated that when you upgrade you may have been asked to accept that ol' pop up box regarding the keychain access. If at any point you did not choose to accept ALL changes it could have changed the permissions on the keychain item for your network, thus causing the problem.

I hope this solves the problem...we will have to wait and see.
 
wldcrd1088 said:
For those of you still having trouble with airport after installing leopard, the problem seems to lie in the timeout settings configured in the new OSX operating system.
Click to expand...
I've have seen in the Console logs, time adjustments up to 1.2 seconds long, I know that in computer lingo this is a very long time, I would say long enough to disrupt connectivity, I have had a stable connection for about 10 days now since my last fix up.
 
yep

I had the same issues with a Linksys wireless router.

Just set it for DHCP with manual address.

Set the last set of numbers with any number besides 100-200.

voila.
 
keychain...

Ted400 reports the following: "So... a week later and still running. It looks like this problem is directly related to the permissions listed in the keychain as stated earlier. I was able to speak with a Apple Product Specialist today (after being on hold for an hour), and it seems that he agreed that that was the problem. He stated that when you upgrade you may have been asked to accept that ol' pop up box regarding the keychain access. If at any point you did not choose to accept ALL changes it could have changed the permissions on the keychain item for your network, thus causing the problem. I hope this solves the problem...we will have to wait and see."
I did recently deleted all the keychains, keychainprefs.plist and in the keychain app, whenever you redo your settings go back and highlight the key for your wireless network and double click and under the Access Tab select the "allow all apps to access this key"
 

Attachments

  • Key01.jpg
    Key01.jpg
    57.2 KB · Views: 251
appleretailguy said:
I had the same issues with a Linksys wireless router.

Just set it for DHCP with manual address.

Set the last set of numbers with any number besides 100-200.

voila.
Click to expand...

Read the thread (from the beginning!)....that didn't fix the problem...if you are having the same one. Plus if you have a laptop, who wants to change from static to assigned IP address every time you leave /come home. Not a viable or practical solution, nor does it actually fix this problem.
 
Aloha everyone,

I have experienced this issue, but only a few times in the past few years. I switched from the PC to the Mac in August of 2006, but this issue occurred both on a completely Windows XP network as well as a mixed Windows XP/Vista/Mac OS (Tiger/Leopard). What I have noticed is that I experienced some of these issues following a power spike, as has been noted earlier in this thread.

Not to sound too basic, but the 169.254.x.x IP assignment is called APIPA - Alternate Private IP Address (or assignment), which normally occurs a computer's NIC does not receive an IP assignment from its designated router or DHCP server. Once a computer's NIC is assigned an APIPA, no routing takes place. For example, the client computer can no longer ping its normal gateway (the router), nor any other computer on the network, even if also assigned an APIPA (this was covered in a class I took, but I have never independently attempted to ping two separate client computers in this scenario).

I first look at the, in my case, cable modem to router connection. I have found that simply powering down the cable modem and router, powering them back up (after waiting 30 seconds or longer - the cable modem first), then finally connecting the router to the cable modem normally solves the issue. On one occasion, however, have I been forced to reset the router back to the factory default configuration.

I have experienced this issue twice since switching to the Mac, one while on Tiger and once while on Leopard, but only once on each. In my experience, this issue is NOT related to the OS, but to a failure of the router and the NIC of the affected client computer to effectively communicate the DHCP IP assignment. As I posted above, I have experienced this issue on Windows XP, Vista (my brother-in-law's computers), Tiger, and Leopard. In every case, the issue lay with the router and/or the cable modem (my ISP suffered network connectivity loss on three occasions). I think it is unfair to lay the blame for this issue solely with Leopard. That being said, I have experienced some other issues with both Tiger and Leopard, but they have primarily been of the PEBKAC (problem exists between keyboard and chair) variety. 😀

HawaiiMacAddict
 
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