Have to constantly renew DHCP lease

Same problem for me. So frustrating. There doesn't seem to be a fix, and it's clearly an issue with my MacBook. Other computers in the house or brought into the house have no problem.

Renewing the DHCP Lease automatically fixes the issues, then 10 minutes later have to do it again.

Same issue in a new user account, only on this MacBook.

Booo.

Exact problem!! Except it only works for 20 seconds or less. I have two routers and they both work for the other computers this one, so it is definitelly an issue with this macbook!

Has anyone been able to resolve this issue?

I have been thinking about reseting the mac and then using time machine to restore files.

I am running Mac OS X 10.6.8 on a 13" white MacBook

Having the exact same problem on a late 2012 Macbook Pro 13" using OS X 10.8.4.

It only happens at my workplace and it's extremelly annoying. I'm not even sure if it's a hardware or software fault, since sometimes after renewing my IP from a DHCP request it stays active for 2 minutes, while other times it can go up to 40 mins to more than 1 hour. Never had a day of full Internet access though...

Curious enough, on the same network configuration, with the very same clients connected, my "old" laptop (Windows 7) was just fine.

I've read about 30 pages from multiple threads, and haven't found a proper solution... thinking it may be about time to get it sent back for a proper fix, cause I can only think of faulty network adapter.

Some say the SSID Channel in the router settings can not only fix the issue for Wi-Fi but also for a wired connection, due to some sort of interference, but haven't tired it out. It doesn't make much sense though, since I keep my WiFi card turned off (or do I really?...).

Now, it looks to me as if this is some sort of sleep/idle issue, as many others have found. What I found curious is that after having all this trouble, I started to renew my IP using the terminal. And the thing is, if I renew it while having an active connection (meaning my MBP ethernet didn't die on me) I don't have to insert my user password (since I am already with high privilege). However, when I am forced to do the DHCP renew because I lost connectivity, I do have to input my password. I'm not keen into how everything works on the MBP, but could it be possible that the network adapter shuts itself down, because only the "su" can acess such interface?

I have just tried to set the su timeout to infinite, after googling it today, so I will keep an eye for results tomorrow when I get to my workspace. Sad thing is, this attempt could make a bit more sense wouldn't it be for my MBP keeping a good and steady connection at home, which has way more devices communicating inside the network.

I was having this problem the other night after I finished doing a massive upgrade to our Home Network (New Router, Modem, Cabling, Etc)

I had to reset my DHCP lease every few minutes, in the end I found it was the IP Address kept setting itself to other items on the Network, I have some items coming through on wired (ethernet) and some were checking in on WiFi (Airport Extreme) the Mac Mini would grab an IP address that it thought was available and then we would have a clash.

I was watching the items on my Routers Attached devices screen, The Mac Mini would show up on the page with its new address (after hitting the DHCP Renewal button) then something else would check in with that exisiting IP Address, clash and the Mac Mini would need the DHCP lease renewed again.

I'll be the first to admit my Networking knowledge is limited (and I'm learning more all the Time) but I simply went into the preferences panel and set the IP address manually.

1. I went into preferences and selected Network

2. Set Configure IPV4 to: using DHCP with manual address

Now it helped I had my NetGear Routers "Attached devices" Page open here so I could see the address of everything else on my network (I went and switched everything on that was web connected so it would be logged in and running on the network) I looked at the last digit or 2 of every item on my network and then set my new IP address.

3. To ensure I wouldn't have any more clashes I set my new IP address far away from the the others* your only changing the last digit or 2 of the IP address, so in the case of my Mac Mini it went from

xxx.xxx.02 to xxx.xxx.0.52 (note the x's are normally your IP address numbers)

*I originally set it to xxx.xxx.09 but I since found the TV had that IP address (The one thing I forgot to check the previous night) so I this is when I decided to set it far away from the rest of the bunch by setting it to .52 (No specific reason for 52, that was just the 1st number to pop into my head)

Now that was over a week ago and since then I have had no more issues on my Network, so far everything is running smooth and fast.

This is probably not the ideal way to fix this issue, but so far it is working, hopefully someone with quality networking experience can chime in with a more permanent solution.

APPLE COMPUTER COMPANY!

I see lots of complaints by lots of customers but I don't see anyone from Apple responding with a solution. What's going on? I would be sufficient to simply acknowledge the fact that people are seeing a problem and would like some resolution.

B.T.W. I'm having a similar problem with my brand new MacBookPro Retina. I makes developing client/server iOS applications a pain in the ***.

Reggie Carey

MadMacs0 wrote:

And you never will.

Actually, that's no longer true as there are some limited circumstances where a modest amount of Apple help has been authorized, but I would not expect them to show up here any time soon, especially since it's an eighteen month old thread.

Cool. I can get behind using a Genius bar for problems or the Feedback page as you suggest. I was under the misconception that this was a forum for Apple to communicate directly with their consumers.

That being said, does anyone have a solution to the problem I'm facing? In particular, my MBP will complain that someone else on my DHCP network is using my IP address. This happens many times during a given day. My DHCP service is not handing out my machines IP address to other computers on my network and no other machine on my network is suffering this problem. It appears that this computer MBP is not recognizing its DHCP signature (if there is such a thing) when it tries to restablish after a sleep cycle (screen save mode) or other event of unknown origin. There seems to be some incompatibility with this MBP and my DHCP service that does not show up on either of my older iMacs, my other MacBookPros, my iPhones, iPads, AppleTV, or iPods.

I'm going to visit the Genius Bar unless there's some magic solution someone has come up with.

Thanks!

Reggie Carey

Might i suggest trying to set your ip manually as i point out in the post above, i was getting the same error as you, constant errors saying something else on my network was using my ip, so i gave up on the auto allocation of an ip and set my own manually, so far so good, it has been working fine, no more errors, no more dramas.

I can only assume the DHCP lease renewal has a problem in OSX, because every time i used it within minutes i got the error message stating that i had an ip clash.

So before you make a trip to the genius bar try manually setting your ip, cant hurt to try.

I have had the same problem with my macbook r during a staying abroad as I had to input several adresses (hotel, office, ...). But everything have been solved when I decided to allocate each new adress a new configuration (not in the automatic list), so my mb does nto choose for me the right adresses.

To do this just open in the internet preference panel (sorry my OS is in french and I amnot sure about the english translation), then choose "modify the configurations" to add a new adress (outside the automatic list). Then as after choosing the name you may use DHCP or manual configuration to set up this new configuration.

I suspect that would solve the problem for at least a portion of people with this problem.

The thing is that Apple is really not very clear with how to configure the Internet adress. At least in my case I understood only recently (and probably quite incompletely) what meant this automatic configurations...

I have exactly the same problem with my Mac Pro on a wired connection - whereas my wife's MacBook doesn't seem to suffer the same issues. As with the other posts, renewing the DHCP lease from the network control panel brings the connection back but I found this blog post today which looks like it might be a viable workaround.

http://info.michael-simons.eu/2012/01/05/mac-os-x-lion-loses-network-connection- after-sleep/

I've yet to try it as I'm just trying to get my head around it but I'll repost if I have any results.

This seems to be the only work around that works so far, manually setting an IP address, I have suggested this work around to a number of friends with the same issue and so far everyone has had success.

It would be better if we didn't have to set our ip's manually, and the DHCP renewal button worked, but such is life.

Set your IP manually, set it far away from everything else on your network and you should be fine.

See my post 4 or 5 posts back to get a step by step guide. Again, can't hurt to try.

OK I think I have this fixed - been stable so far today on my Mac Pro wired connection after several sleeps! 🙂

Problem seems to lie in the automatic location setting in the network settings, so here's what I did...

1. Network settings - Location - Edit Locations

2. Add a new location .. "Home" for example

3. With home selected, click the cogwheel below the network services and choose "Set Service Order"

4. Reorder the services so your preferred connection type is at the top

5. After that, select each service in turn (assuming you have a few - like Bluetooth PAN etc)

6. Make the services you are not using inactive

7. Apply

Please post if this works for you - it's been dragging on far too long and needs sorting out by Apple but if this is a good workaround for people then it will do for now.

My solution which is also SpankyMK's is still working - over 24 hours now. Don't forget that after changing the DHCP on your computer you also need to tell your router that it is a static IP.

The only thing I haven't tested is when my wife gets back from hol and two new devices are added to the network.

I will keep you posted.

jrnano wrote:

I had - iPad, iPhone, iMac, wireless printer. My iMac uses ethernet to a small netgear switching router which is connected to my powerline ethernet. The powerline ethernet goes downstairs to another powerline ethernet that my Airport Extreme is wired to. My Airport Extreme is a wireless extension of my Airport Express. My Airport Express is linked via ethernet to my O2 wireless router.

So by my account you have three wireless routers here which means you either have two Wi-Fi networks or you have put the O2 in bridge mode, is that correct? Since most 2.4 MHz Wi-Fi channels overlap, having two networks in the same house could be causing a lot of interference or is there a 5MHz router involved? I'll also observe that it's unusual to have your Extreme be an extension of the Express, since it probably has greater capability as routers go. I'm used to seeing Expresses used as the extension, but not sure it would make any difference.

I also changed IPv6 to local link only in case that was causing issues (I can't think why it would but it was some positive action I could take).

It has worked for many users. In some cases it was problems with their ISP's implementation of IPv6 and in others it fixed a known issue with some models of Airport Express, but that usually involved AirPlay.

Apple - just tell every one a fix - Please!!!!!

You do know that Apple may not even be reading this, right?

This Fix has got things working for me.

I have reprinted this response from a earlier post I have made (Repost) A number of people were asking me about my fix, so I have expanded my response to hopefully offer a little more clarity.

I was having this problem the other night after I finished doing a massive upgrade to our Home Network (New Router, Modem, Cabling, Etc)

I had to reset my DHCP lease every few minutes, in the end I found Mac Mini's IP Address kept setting itself to other items on the Network, I have some items connected on wired (ethernet) and some were connected on WiFi (Airport Extreme) after clicking the DHCP Lease Renew the Mac Mini would grab an IP address that it thought was available but then another item on my network would "check in" then we would have a clash, The Mac Mini was grabbing what it thought was an available IP address, the DHCP Renew button was not setting the Mac Mini's IP number far enough away to stop the clash.

I was watching the items on my Routers Attached devices screen, The Mac Mini would show up on the page with its new address (after hitting the DHCP Renewal button) then something else would check in with that exisiting IP Address, clash and the Mac Mini would need it's DHCP lease renewed again.

My Network consists of:

- Mac Mini (Wired)

- Acer Laptop (Wired)

- PS3 (1) (wired)

- Apple TV (wired)

- Airport Extreme (wired and looking ater WiFi duties throughout the house)

- PS3 (2) (WiFi)

- TV (WiFi)

- iPad (WiFi)

- Nexus 7 (WiFi)

- Printer (WiFi)

I'll be the first to admit my Networking knowledge is limited (and I'm learning more all the Time) but I simply went into the preferences panel and set the IP address manually.

1. I went into Preferences and selected Network

2. Set Configure IPV4 to: using DHCP with manual address

Now it helped I had my NetGear Routers "Attached devices" Page open here so I could see the address of everything else on my network (I went and switched everything on that was web connected so it would be logged in and running on the network) I looked at the last digit or 2 of every item on my network and then set my new IP address.

3. To ensure I wouldn't have any more clashes I set my new IP address far away from the the others* your only changing the last digit or 2 of the IP address, so in the case of my Mac Mini it went from

xxx.xxx.02 to xxx.xxx.0.52 (note the x's are normally your IP address numbers)

*I originally set it to xxx.xxx.09 but I since found the TV had that IP address (The one thing I forgot to check the previous night) so I this is when I decided to set it far away from the rest of the bunch by setting it to .52 (No specific reason for 52, that was just the 1st number to pop into my head)

Now that was over a week ago and since then I have had no more issues on my Network, so far everything is running smooth and fast. (It has now been over 3 weeks since I posted this, and everything is still working perfectly, I suggested this solution to 2 friends having the same issue and it also fixed there problems as well)