Help Center > > FAQs> Network Configurations> Others> Why Cannot I Use DHCP to Obtain a Private IP Address?

Why Cannot I Use DHCP to Obtain a Private IP Address?

Updated at: Jun 23, 2020 GMT+08:00

Symptom

DHCP cannot be used to obtain a private IP address. The symptom varies based on the OS.

  • For Linux, a private IP address cannot be assigned.
  • For Windows, a private IP address is changed to an IP address in the 169.254 network segment, which is different from the private IP address displayed on the ECS console.

Solution

  1. Check whether dhclient is running in the ECS.

    1. Log in to the ECS and run the following command:

      ps -ef | grep dhclient

    2. If the process is not running, log in to the ECS, and restart the ECS NIC or initiate a DHCP request.
      • Linux

        Run the dhclient eth0, ifdown eth0 + ifup eth0, or dhcpcd eth0 command.

      • Windows

        Right-click a local area connection and choose Disable from the shortcut menu. Then, choose Enable.

  2. Handle the issue if the DHCP client fails to work for a long time (for example, the issue recurs after the NIC is restarted).

    1. Configure a static IP address.
    • Windows
      1. Right-click Local Area Connection and choose Properties from the shortcut menu.
      2. In the displayed dialog box, select Internet Protocol Version 4 (TCP/IPv4), click Properties, and modify parameter settings.

    • Linux
      1. Log in to the ECS and run the following command to modify parameter settings:

        vi /etc/sysconfig/network-scripts/ifcfg-eth0

        BOOTPROTO=static
        IPADDR=192.168.1.100 #IP address (modified)
        NETMASK=255.255.255.0 #Mask (modified)
        GATEWAY=192.168.1.1 #Gateway IP address (modified)
      2. Run the following command to restart the network:

        service network restart

    2. Select an image in which DHCP runs stably.
    • Native Windows series, such as Windows Web Server 2008 R2 64bit, Windows Server Datacenter 2008 R2 64bit, Windows Server Enterprise 2008 SP2 64bit, or Windows Server Enterprise 2008 R2 64bit
    • CentOS series, requiring you to add PERSISTENT_DHCLIENT="y" in /etc/sysconfig/network-scripts/ifcfg-ethX
    • Ubuntu series, such as Ubuntu1004

  3. If the fault persists, obtain the messages log in /var/log/messages on the affected ECS, use the MAC address of the affected NIC to filter the desired log, and check whether there is any process preventing DHCP from obtaining an IP address.
  4. If the fault persists, contact customer service for technical support.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel