MacBook 2.0 GHz Aluminum, 4 Gigs memory, OS X 10.5.6 with all updates, etc--Great machine (new as of Feb).
About 2 or 3 weeks ago I began to have trouble with wireless connection. Originally, I had set up wireless to connect to an unprotected network at the office (a university campus) and at home with a WPA encryption passphrase (WPA personal; I had also tried WEP). Airport is set to use DHCP (it needs to in my office). Firewall is on and set to Set Access to Specific Programs and in stealth mode. Both networks were in the profile Automatic and I had checked "Remember this network".
This worked flawlessly until 2 or so weeks ago. That is when upon boot or upon turning on Airport, signal would show strong in the menu bar applet but I was not connected to the internet. Looking in System Preferences/Network would be the message "...self-assigned IP..blah blah" with an IP of 169.other stuff. Not cool.
At this point the only thing I could do is go kill the firewall, wait about 3 seconds, and then turn it back on. Needless to say not an ideal solution.
I have searched these and other forums and tried various suggested solutions including (at home) repowering everything (Cable modem, wireless router (NETGEAR) and computer), deleting certain file in
/Library/Preferences/System Configuration, etc. NONE of these worked.
One solution I have found is to delete my two wireless networks from System Preferences/Network/Advanced, uncheck the box for the computer to remember all networks it connects to. Now upon boot or upon starting Airport, it will connect but a pop up window appears with the question: Do you want to allow "configd" to accept incoming network connections? (I hit enable button).
The other solution is to simply leave the firewall turned off, one I do not like.
The first solution is acceptable to me as I tend to turn off Airport so I do not get annoyed with email, chat stuff, etc when I am working. It just means that everytime I boot or awake from sleep and want the internet, I have to choose the network to connect to from the menu bar applet--no big deal.
Anyone else experienced this?? Is there a better solution??
Evidently something changed with the update to Mac OS X 10.5.6 a few weeks ago and configd is not seeing through the firewall as it should, hence dhcp cannot see out.
About 2 or 3 weeks ago I began to have trouble with wireless connection. Originally, I had set up wireless to connect to an unprotected network at the office (a university campus) and at home with a WPA encryption passphrase (WPA personal; I had also tried WEP). Airport is set to use DHCP (it needs to in my office). Firewall is on and set to Set Access to Specific Programs and in stealth mode. Both networks were in the profile Automatic and I had checked "Remember this network".
This worked flawlessly until 2 or so weeks ago. That is when upon boot or upon turning on Airport, signal would show strong in the menu bar applet but I was not connected to the internet. Looking in System Preferences/Network would be the message "...self-assigned IP..blah blah" with an IP of 169.other stuff. Not cool.
At this point the only thing I could do is go kill the firewall, wait about 3 seconds, and then turn it back on. Needless to say not an ideal solution.
I have searched these and other forums and tried various suggested solutions including (at home) repowering everything (Cable modem, wireless router (NETGEAR) and computer), deleting certain file in
/Library/Preferences/System Configuration, etc. NONE of these worked.
One solution I have found is to delete my two wireless networks from System Preferences/Network/Advanced, uncheck the box for the computer to remember all networks it connects to. Now upon boot or upon starting Airport, it will connect but a pop up window appears with the question: Do you want to allow "configd" to accept incoming network connections? (I hit enable button).
The other solution is to simply leave the firewall turned off, one I do not like.
The first solution is acceptable to me as I tend to turn off Airport so I do not get annoyed with email, chat stuff, etc when I am working. It just means that everytime I boot or awake from sleep and want the internet, I have to choose the network to connect to from the menu bar applet--no big deal.
Anyone else experienced this?? Is there a better solution??
Evidently something changed with the update to Mac OS X 10.5.6 a few weeks ago and configd is not seeing through the firewall as it should, hence dhcp cannot see out.
