I've come across this problem now and again where OSX wont wait for a DHCP server to respond. Its come up again today with a new wireless access point I installed at work. The WAP does a DHCP relay to our Windows DC which is on another subnet. Windows machines get IPs just fine, and an older mac I was using seemed to get one too. But my boss is demoing a MacBook air for shits and giggles and when I try to get that thing connected it connects, but then says no ip.

I've googled it and it appears to be a widespread problem, but since mac users are all total faggots the responses to this question are "obviously you have it set wrong because apple could never fuck up something like this". I saw one fucking response where a guy was like "oh yea definitely a DHCP timeout problem. I know how to change it, but I wont post the details here". I'm not even kidding. google that shit if you want your eyes to bleed.

If it were a real *nix system i'd be able to edit dhclient.conf, but its not where it would normally be. Does dhclient.conf exist somewhere else on the system or is there any way to inrease the DHCP timeout?

Its not exactly a pressing issue as we'll be shipping it back at the end of the trial, but since Im sure its going to come up in the future I'd still like to know how to fix it.

3/20/2008 2:55:55 PM

I believe one of these two programs can make the change.
I've used the "LeopardCacheCleaner" before, just not for network stuff.

http://www.northernsoftworks.com/leopardcachecleaner.html
http://www.sustworks.com/site/prod_iptx_overview.html

3/21/2008 7:55:26 AM

I'll give it a try. Thanks.

3/21/2008 8:09:25 AM

i've had this problem too and usually just put in a static IP because i didnt wanna f with it

3/22/2008 10:33:31 PM

Quote :

"I've googled it and it appears to be a widespread problem, but since mac users are all total faggots the responses to this question are "obviously you have it set wrong because apple could never fuck up something like this". I saw one fucking response where a guy was like "oh yea definitely a DHCP timeout problem. I know how to change it, but I wont post the details here". I'm not even kidding. google that shit if you want your eyes to bleed."

i laughed

3/23/2008 5:42:42 PM