大网数据广告活动
网络与域名解析

Troubleshoot problems on the DHCP client

· 52CE 我爱测

Introduces how to troubleshoot problems on the DHCP client and collect data.

[!div class="nextstepaction"] <a href="https://vsa.services.microsoft.com/v1.0/?partnerId=7d74cf73-5217-4008-833f-87a1a278f2cb&flowId=DMC&initialQuery=31806271" target='_blank'>Try our Virtual Agent</a> - It can help you quickly identify and fix common DHCP issues.

This article discusses how to troubleshoot problems that occur on DHCP clients.

Troubleshooting checklist

Check the following devices and settings:

  • Cables are connected and working.
  • MAC filtering is enabled on the switches to which the client is connected.
  • The network adapter is enabled.
  • The correct network adapter driver is installed and updated.
  • The DHCP Client service is started and running. To check this, run the net start command, and look for DHCP Client.
  • There is no firewall blocking ports 67 and 68 UDP on the client computer.

Event logs

Examine the Microsoft-Windows-DHCP Client Events/Operational and Microsoft-Windows-DHCP Client Events/Admin event logs. All events that are related to the DHCP client service are sent to these event logs. The Microsoft-Windows-DHCP Client Events are located in the Event Viewer under Applications and Services Logs.

The Get-NetAdapter -IncludeHidden PowerShell cmdlet provides the necessary information to interpret the events that are listed in the logs. For example, Interface ID, MAC address, and so on.

Data collection

We recommend that you collect data simultaneously on both the DHCP client and server side when the problem occurs. However, depending on the actual problem, you can also start your investigation by using a single data set on either the DHCP client or DHCP server.

To collect data from the server and affected client, use Wireshark. Start collecting at the same time on the DHCP client and the DHCP server computers.

Run the following commands on the client that is experiencing the problem:

ipconfig /release
ipconfig /renew

Then, stop Wireshark on the client and server. Check the generated traces. These should, at least, tell you at which stage the communication stops.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。