Intermittent Network Connectivity Loss During DHCP Lease Renewal

Hakim Ismail 40 Reputation points
2026-10-29T02:10:00.3866667+00:00

Hi everyone

Has anyone seen this behavior with Windows 11 clients and Microsoft DHCP Server on Windows Server 2022 where:

Clients obtain DHCP leases successfully.

Network connectivity works normally during regular operation.

When the DHCP lease renewal process starts, some workstations temporarily lose network connectivity or fail to renew their IP address.

The Microsoft-Windows-DHCP-Client Operational log records renewal attempts, while the DHCP server shows inconsistent lease activity for the affected devices.

As a result, it is unclear whether the failure occurs on the client, the DHCP server, or somewhere in the network path between them.

What is the best way to correlate DHCP client logs, server lease information, and potential network interruptions to identify exactly where the renewal process is failing ?

Windows for business | Windows 365 Business
0 comments No comments

Answer accepted by question author
Rukshan edirisinghe 2,850 Reputation points
2026-10-29T03:29:54.9566667+00:00

Hi @Hakim Ismail

One detail usually explains "works at first, fails at renewal". A client's first lease uses broadcasts that the router relays (IP helper) to the DHCP server. A renewal at 50% of the lease is a unicast REQUEST sent straight from the client to the server. If a firewall, ACL or Dynamic ARP Inspection/DHCP snooping on the path allows the relayed traffic but not direct UDP 67/68 between the client subnet and the server, renewals fail until the client falls back to rebinding.

To prove where it breaks, capture both ends at the same moment. This is Microsoft's own DHCP troubleshooting method:

  1. Install Wireshark on one affected client and on the DHCP server. Start both captures at the same time.
  2. On the client run ipconfig /renew (or wait for a natural renewal). Filter the client capture with dhcp, and note the Transaction ID.
  3. On the server capture, filter with dhcp.id == <that Transaction ID>.
  4. If the REQUEST leaves the client but never reaches the server, the network path is dropping it. Check firewall/ACL rules, DHCP snooping and DAI.
  5. If the server receives it but sends no ACK, or sends a NAK, check the server's events under Applications and Services Logs > Microsoft > Windows > DHCP-Server and the logs in %windir%\System32\Dhcp.
  6. If the ACK reaches the client but it still drops off, look at the client's System log and NIC power settings.
  7. If you use DHCP Failover or split scopes, check that both servers agree on the lease, since inconsistent lease activity often shows up there.

Microsoft's TSS tool also collects all of this in one go: TSS.ps1 -Scenario NET_DHCPcli on the client and NET_DHCPsrv on the server.

Are the affected clients on a different subnet from the DHCP server (using a relay)?

If the capture pinpoints the drop, please consider accepting it as the answer. If both captures look clean, let me know and I'll be happy to keep helping.

Reference:

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Newest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.