During the installation of the centos6.5 learning Linux system using VMware workstations, one day Linux was unable to acquire the IP correctly, the following situations occurred.
650) this.width=650; "title=" 1.png "src=" Http://s3.51cto.com/wyfs02/M02/74/BB/wKioL1YoScPC0dLFAAENyXMVTvc731.jpg " alt= "Wkiol1yoscpc0dlfaaenyxmvtvc731.jpg"/>
There are many answers on the internet.
First, the error is
Bringing up interface Eth0:device eth0 does not seem to be present,delaying initialization
650) this.width=650; "title=" 2.png "src=" http://s3.51cto.com/wyfs02/M02/74/BE/ Wkiom1yosz6r8rn2aadghwavpks536.jpg "alt=" wkiom1yosz6r8rn2aadghwavpks536.jpg "/> error reason, is because the Linux network adapter binds the original MAC address to cause
Workaround for
1. Use Ifcnfig-a to view the current host MAC address
650) this.width=650; "title=" 3.png "src=" Http://s3.51cto.com/wyfs02/M01/74/BB/wKioL1YoS7bQm_FAAAHoM0USj_Q077.jpg " alt= "Wkiol1yos7bqm_faaahom0usj_q077.jpg"/>
2. Modify the eth0 NIC hardware address to the current address
Vi/etc/sysconfig/network-scripts/ifcfg-eth0
650) this.width=650; "title=" 4.png "src=" http://s3.51cto.com/wyfs02/M02/74/BE/ Wkiom1yotbscgt4laacwewscgkg959.jpg "alt=" wkiom1yotbscgt4laacwewscgkg959.jpg "/> Save Exit
3. Delete the 70-persistent-net.rules file
Rm-rf/etc/udev/rules.d/70-persistent-net.rules
4. Rebooting the system
Reboot-h now
The problem is that when transferring Linux systems, different native machines produce different MAC addresses.
Second, the error is
Determining IP information for eth0 failed;no link present. Check cable?
Online answers are as many as:
Down to/etc/sysconfig/network-scripts/ifcfg-eth<n>.
/etc/sysconfig/networking/devices/ifcfg-eth<n> where <n> represents the identification number of the Ethernet adapter, typically 0. When it's zero, it's/etc/sysconfig/network-scripts/ifcfg-eth0.
/etc/sysconfig/networking/devices/ifcfg-eth0 These two files are added
Check_link_down () {
return 1;
}
In addition, if a/etc/sysconfig/networking/profiles/default/ifcfg-eth0 file exists, you can also add this section to it, and then restart the system.
This solution is to add code, constantly go to get the IP address, start, will be a little slow, for reference only.
Thirdly, the problem that I have appeared, these have not solved. is a native problem with installing the virtual machine.
It is possible that an optimization software has disabled the service from booting. That's the service.
650) this.width=650; "title=" 5.png "src=" Http://s3.51cto.com/wyfs02/M02/74/BF/wKiom1YoUJWyFH7UAAF2fFf6YKQ334.jpg " alt= "Wkiom1youjwyfh7uaaf2fff6ykq334.jpg"/>
Start and set up the two services as self-booting, use Dhclient to regain the IP, and restart the service using service network restart, or use the Ifup eth0 to start the network card to obtain IP automatically
VMware workstations uses NAT network connection mode cannot obtain IP in several cases