According to Princeton University, the iPad (and perhaps other iOS devices?) seems to have had various issues with DHCP that exist even on the current version (4.3.3). The current one involves the device keeping (and using) an expired DHCP lease under certain circumstances.

It looks like Princeton's course of action is to let the user know of the workaround they've devised and ban them from the network if the issue still persists. Their article also mentions:

Sites that do monitor for these problems closely are unlikely to encounter the issue if they assign DHCP leases with expiration times longer than about an hour.

I saw one article (having trouble finding it now) that mentioned configuring your DHCP server to ping addresses (to ensure no client is claiming it) before offering them to clients.

That said, these issues have supposedly existed for over a year now and I don't see much discussion (on here or Google) about dealing with it on a medium/large scale network.

  • Have you experienced any issues related to this on your network?
  • If so, how have you dealt with them?

1 Answer 1


Macs in general seem to have this issue a lot, I havn't played around with iphones and ipads a lot to be fair but I have a mac and have noticed that in some situations it causes clashes on a network or doesn't recieve an address at all.

If all of your devices are at least recieving a lease then why not give them reservations? This way even if the lease is stale it will stick with it's own IP. It's not ideal but at least you won't have multiple devices on the network with the same IP address.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.