mdnsresponder and configd

I am having the same problem since I had a battery problem and had to reset my PMU and PRAM. I have to shut off my firewall to get a DHCP config then turn the firewall back on. This usually happens each morning when I startup. Apparently both of those apps are needed to pick up DHCP settings, but the firewall on strict settings won't let them thru. I cannot find a way to permanently allow them through. Hopefully someone will figure out a solution for us all.

I have the exact same problem with mdnsresponder and configd and nmblookup. nmblookup will eventually show up in my allowed list in the firewall settings, but the other two will not. It all started for me when I restarted after running boot camp and the date and time needed to be reset. (The time needs to be reset every time I use boot camp - another bug - but the date usually is fine.) I got a warning that some things may not work correctly if I didn't reset the date, which I did immediately. Ever since then each time I restart I have to either allow them or allow all incoming connections to get networking to function.

One of the above posts mentions that com.apple.kerberos.kdc and com.apple.systemdefault need to be replaced. Could this be done from a time machine backup? If so where are they supposed to live exactly? I tried deleting the network keychain items and re-entering them but it did not help.

I, also, never had problems with Tiger and have had a number of things like this occur with Leapord that seem not to be able to get resolved. Very disappointing.

Reading this article, <http://support.apple.com/kb/TS1452>, it says that the com.apple.kerberos.kdc certificate is machine-specific, so I suspect that even if you could export it from another Mac, that won't help you.

Looking at my own Macs, I can see the certificate is indeed different on each one. So is the systemdefault certificate.

That obviously makes sense and is an easy fix, but how do you get mac hidden files to show up in the list so you can select them. Even when I have hidden files showing up in the finder they will not show up in the firewall system preference list so I can choose them. nbmlookup showed up for me on its own and when I click "reveal in finder" it brings it up in a separate window and shows it even though it is hidden, but I cannot get there to add new ones. I also tried dragging it from the finder but that did not work. Thanks for your help.

Okay, Wendy so I was in totally the same boat as you, with no idea how to do this. After playing around though this is how:

1. Download Main Menu ( http://www.santasw.com/)

2. Install and then it puts an icon in your menu bar. Click it, highlight finder (in the menu) and then click show invisibles. Finder will restart.

3. Clear the deksotop and open finder. Go to Machintosh HD (they'll be lots of folders, including the crucial usr folder).

5. Open system preferences, go the firewall section.

6. Click the add button and then in the finder window that you opened drag the usr folder onto the window (see this image: http://img122.imageshack.us/img122/9158/howtoue6.jpg)

7. Then naviagate to /usr/sbin/mDNSResponder and you can select it. This can also be repeated for configd (it was giving me problems).

8. Voila, problem solved.

Charles,

I'm glad my tips have been able to get you up and functioning again. Did you find you only got the prompts following a waking from sleep? This was my main problem (although occasionally I did get these messages at startup - though not everytime) If so:

Appleinsider wrote:
Among the latest improvements is a fix for an issues that prevented some Mac systems from properly rejoining an AirPort wireless network after awaking from sleep.

http://www.appleinsider.com/articles/08/04/18/appleoffers_developers_weekend_10_5_3seed.html

I guess we'll see what 10.5.3 brings, but yes, clearly there is a problem in 10.5 that Apple needs to address and we'll have to wait until .3 to know if they have sorted it. The workaround I posted is a lot of hassle (although it appears a onetime fix). Nonetheless, something we shouldn't have to do. Fingers crossed it is fixed for I'm sure there are numerous people out there that haven't found this (or any other fix) to their problems and are using their firewall in a way they find less than satisfactory.

Interestingly I was getting these issues when booting up from a shutdown system, ie it was not connected to waking from sleep.

Also, I first noticed this problem when connecting with AirPort but yesterday (before applying the fix) I found I was also getting the same symptoms when connecting with a wired ethernet line. I am not sure if anyone else with this issue has tried connecting through an ethernet cable but I suspect it is not an AirPort problem. I am therefore not sure whether 10.5.3 will address this.

Interestingly I'd not really ever noticed these problems on a LAN network, until today.

I have found that with my fix applied when I connect to the network I can only see windows "workgroups" in the Shared (network) folder.

If I turn the firewall off (allow all incoming connections) I can see the individual apple computers on the network. Possibly a bonjour problem?

I have looked and compared activity monitor when firewall is off and when I choose my fixed firewall and the processes seem to be exactly the same.

Lots of photos have been taken and documents collected. I'm going to try take this in to Apple this week (if I can get a genius appointment) and have them take a look (though I'm sure they'll not be able to do anything).

I'm still keeping my fingers crossed for a fix in 10.5.3 but now I'm unsure this will help.

That's odd, even though I added configd and mDNSResponder to my firewall list, I am still prompted to accept incoming connections for them after rebooting.

Also, I am informed that my computer name is already in use, and it is automatically renamed (a number is appended). This happens on each boot. Eventually I can connect to my AirPort router.

In my case, all these problems started happening after the logic board was replaced in my MacBook Pro.

Unfortunately, just like Krakatos, even having successfully added configd and mDNSResponder to my firewall's allowed list, I am still asked whether I want to allow incoming connections for them on rebooting. I am also being told that my computer name is already in use right after allowing these, and it is automatically renamed with a number being appended.

I am trying to get my local Mac store to fix this, hopefully this weekend. Will let you know if I have any success.

Same issues here.

My strongest hunch is that this has something to do with Microsoft Messnger 7.0. I never had this problem at all until I installed Messenger. Although I have trashed Messenger, maybe there are some related files I did not get. Any ideas if there are any related messenger files I could delete which would make this go away? Is it even possible that this is related to messenger?

I added configd and mdnsresponder to the list in the firewall tab of the Security pref pane and have it set to "allow incoming connections".

I also, as suggested by lstnmysphr, removed the com.apple* files.

Even though trying the two steps above, I still have the problem when either waking from sleep OR rebooting. My only workaround is to go into Firewall tab of Security pref pane and check "allow all incoming connections", close the pref pane, reopen the pref pane, then click on 'set access for specific services and applications".


I have not yet attempted reconfiguring the kerberos certificates.

Thanks for the help.

Confirmed - PMU reset did it!

This solution has a certain symmetry: the cause of my troubles has been that the battery power drained totally during sleep. I also thought some of the earlier file-based solutions work, but that may have been interferences with other attempts.

After the reset, I logged in first as an administrative user (not sure if that makes a difference), and got firewall-related dialog boxes for mDNSresponder and configd. Clicked "Allow", and that's it. The time got of course lost as well, but ntpd manages to fetch it, once the "Time and Date" Preference panel is opened.

Michael

Well, success was short-lived.

After putting the PowerBook to sleep for a day and waking it up, DHCP does no longer work - Airport gets a self-assigned IP, and only if the firewall is opened temporarily will it work.

Apparently, there's some sort of timeout active. After I applied the PMU reset, DHCP worked after sleep/wake and after reboot. But not after more than, say, 20 hours.

Back to square one. miffed.

I have gotten all back to normal (by "normal" I mean my wireless works upon restart and wake from sleep without having to manipulate the firewall settings in order for wireless to actually have internet access) although not sure what actually did it.

One thing I did do which seems to have been a positive step was to repair the permissions in Disk Utility. I first verified disk permissions and then did the repair disk permissions. I have heard/read differing reports on the effectiveness of repairing disk permissions, but this seems to have done something which was/is positive.

Agreed 10.5.3 seems to have settled it for me thus far. I've been on a few different networks already today and pre 10.5.3 I would have noticed this bug by now I'm sure. I'll keep an eye on it but it does indeed seem like it's been resolved (and not a moment too soon).