Figure: DHCP Server Client troubleshooting method

In the previous article, we explained the troubleshooting ideas of the DHCP service. I don't know if you already have a clear understanding of it? Here we will focus on the client issues.

Client troubleshooting:

DHCP faults mainly involve two aspects: client problems and server problems. First, we will introduce the troubleshooting methods on the client.

Step 1: Go to Start-> Run-> Enter CMD in the task bar to enter the command line mode.

Step 2: Enter ipconfig in command line mode and press enter to check whether the IP address can be automatically obtained.

TIPS: before performing the first two steps, ensure that the IP Address Allocation Method of the client is set to automatically obtain the IP address.

Step 3: If you can obtain the correct IP address, it means that DHCP is normal. If you find that the address is incorrect, it includes 169. 254. *. * In this form, run the ipconfig/release command to release the currently obtained network parameter information.

Step 4: Release the network parameters and run ipconfig again. We can see that the current network parameters are empty and all information is changed to 0.0.0.0. 1)

Figure 1

Step 5: Release the error message and execute ipconfig/renew to automatically obtain the new information. 2)

Figure 2

TIPS: If you run ipconfig/renew without executing the command to release IP information, you will not be able to obtain IP information again. Therefore, step 3 is indispensable.

Step 6: after obtaining the IP information again, we can view the current address parameters. If we cannot obtain any information, we should start from the local machine to solve the problem, if an error message is returned, find the DHCP server and check it.

Step 7: Disable the local Nic and enable it again. Perform the preceding steps again.

Step 8: If you know the ip address of the DHCP server, you can run the ping command "ping SERVER ip Address" on the client to view network connectivity.

Step 9: search for any fault records related to the DHCP service in the system "Event Viewer. Choose Start> Control Panel> Administrative Tools> event viewer ". 3)

Figure 3

Step 10: Go to Start> Control Panel> Administrative Tools> services to open the service settings window and find the dhcp client service in the service list. 4) double-click it, click the stop button, and then click the start button to restart it. If the service is not enabled, the root cause of the fault is displayed. You can directly start the service and set the startup mode to "automatic. 5)

Figure 4

Figure 5

Step 2: enable the local connection of the network to fix the problem. The solution is "network neighbor-> properties-> Local Connection-> Repair ". The system automatically clears the ARP cache and NETBS information, and then updates the DNS and DHCP service components and related information. 6)

Figure 6

Step 2: If the problem persists in Step 11, we can only use static IP addresses and DNS and other network information to configure the Local Machine for detection. If you have configured the static IP address to access the Internet and connect to the LAN, the problem lies in the connection between the client and the DHCP server or the DHCP server itself. We need to place the cause of the problem on the DHCP server.

TIPS: Sometimes you can set another user for the client and use the user to log on to the client to solve some DHCP faults. In addition, you can use lspfix.exeor winsockxpfix.exe to fix stack errors in the tcpip, scanning the system file again with "start-> Run-> input sfc/scannow" produces unexpected results.