question

JensPeterPoulsen-8168 avatar image
0 Votes"
JensPeterPoulsen-8168 asked JensPeterPoulsen-8168 commented

DHCP server not relase ip-address on Microft Windows Server 2022 Datacenter

Version 10.0.20348 Build 20348

I have installed 2 DHCP server with failover, I have a scope with 4045 client IP-address an a lease time with 9 hours.
Now server says there is no IP-address available , but scope statistics say there should be 21% available.
If I check with Get-DhcpServerv4Lease on scope I can se all 4045 IP-address are in use. And more then 3700 IP-address where lease time has expired.

Why does DHCP server not release IP-address, after lease timeout. If we don't fix this, we need to roll back to 2016 server!!!!

windows-dhcp-dns
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

LimitlessTechnology-0326 avatar image
0 Votes"
LimitlessTechnology-0326 answered JensPeterPoulsen-8168 commented

Hi there,

This issue might occur because DHCP servers lease the IP addresses that are actually owned by some client after the migration. Then, these IP addresses are marked as BAD_ADDRESS. Check if you have updated the Server 2022 with all updates.

If the lease period expires and the DHCP client has not yet renewed its IP configuration data, then the DHCP client loses the IP configuration data and begins the DHCP lease generation process again

Below threads discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.

IPs are not released after the lease expires https://social.technet.microsoft.com/Forums/windowsserver/en-US/87f5fdef-1e6e-4b5f-8617-efcd471d0e9e/ips-are-not-released-after-lease-expire?forum=winserverNIS



--If the reply is helpful, please Upvote and Accept it as an answer–

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi

I can't see that link will help me, DHCP on 2022 server is acting different than the old 2012 and 2016 server. There are e.g. setting on the old server there is not available to import from 2016 to 2022 server.
I see leases with Get-DhcpServerv4Lease where timestamp has expired, and in MSC console it shows that they are active with a different timestamp.
If I clear lease it will show it is use immediately after, even lease time not increased.

0 Votes 0 ·