Solutions for problems with the CentOS 6.0+ network configured with VMware

Reprint Please specify source: http://blog.csdn.net/l1028386804/article/details/46515975

Solutions to problems with the CentOS 6.0+ network configured with VMware first, the two common network connection modes and the difference between the following VMS are introduced: In this mode, the VMware virtual operating system is like a separate host in the local area network. It can access any machine in the network. In bridging mode, you need to manually configure the virtual system with an IP address, subnet mask, and a host machine in the same network segment so that the virtual system can communicate with the host machine. Also, configure the gateway and DNS addresses to enable access to the Internet through a LAN gateway or router. NAT Network: The use of NAT mode is to let the virtual system with NAT (Network address translation) function, the host machine is located in the network to access the public network. In other words, the use of NAT mode enables access to the Internet in virtual systems. The TCP/IP configuration information for a virtual system in NAT mode is provided by the DHCP server of the VMNET8 (NAT) virtual network and cannot be modified manually, so the virtual system cannot communicate with other real hosts on the local area network. The biggest advantage of using NAT mode is that the virtual system access to the Internet is very simple, only the host machine can access the Internet, you do not need to configure the IP address, subnet mask, gateway, but the DNS address should be filled according to the actual situation. Add a DNS address in addition to the network card properties, you can alsoVirtual MachinesIn the "Virtual Network Editor" in the Nat tab, click on the "Edit" button to add.    If you just let the virtual function on the Internet, the two modes can be, with the bridge if you have a legitimate address in the LAN, such as your ADSL cat is the leading way by the function, if it is in the unit, it will be network management to your legitimate IP (now the company is the Mac and IP binding). Now is the host and virtual machine interoperability, if your ADSL led by the function, that shut down the virtual machine DHCP, select Bridge, check whether 2 machine is assigned the same network segment IP, shut down the firewall. Instead, the bridge is the virtual machine that is the equivalent of a separate computer with its own IP address. NAT is the IP of the shared host machine to access the network, which is accessible to the primary host computer for access to the network. 1, the initial installation of CentOS configuration Network A, the use of bridging to connect the network (suitable for routing,SwitchUser), configure the static IP to achieve Internet access, intra-LAN communication vim/etc/sysconfig/network-scripts/ifcfg-eth0device= "eth0" Bootproto=none hwaddr= "00:23: 54:de:01:69 "onboot=" yes "type=" Ethernet "Userctl=no ipv6init=no peerdns=yes netmask=2 55.255.255.0 ipaddr=192.168.1.110 gateway=192.168.1.1 dns1=8.8.8.8 HWADDR, ipaddr, GATEWAY, DNS1 the actual configuration also requires Configure B According to your network environment, use NAT to configure the network vim/etc/sysconfig/network-scripts/ifcfg-eth0device= "eth0" hwaddr= "08:00:27:be:80:a6" NM_ Controlled= "yes" onboot= "yes" bootproto= "DHCP" Bootproto: Sets the way the network card obtains the IP address, the possible options are static,dhcp or BOOTP, respectively, corresponding to the static specified IP address, IP addresses obtained through the DHCP protocol, IP addresses obtained through the BOOTP protocol. Reboot #重启重启后也能正常上网了. 2. Clone clones AsystemConfigure the network environment cloning as the name implies is to copy an identical system from the original system, but we want to make the clone system connected to the Internet, you need to make some adjustments to the network environment when we have service network restart error message bringing up Interface eth0:  device eth0 does not seem to being present,delaying initialization.                    [failed]vim/etc/udev/rules.d/70- Persistent-net.rules record eth1 MAC address # PCI device 0x1022:0x2000 (pcnet32)  subsystem== "NET", action== "add", drivers= = "? *", attr{address}== "00:0c:29:96:50:1e", attr{type}== "1", kernel== "eth*", name= "eth0"    # PCI Device 0x1022:0x2000 (pcnet32)  subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "00:0c:29:d5 : 65:00 ", attr{type}==" 1 ", kernel==" eth* ", name=" eth1 "  then we need to modify the next  vim/etc/sysconfig/network-scripts/ Ifcfg-eth0   Modify the original device eth0 to eth1 and the corresponding MAC address device= "eth1"  hwaddr= "00:0c:29:d5:65:00"  nm_controlled= " Yes " onboot=" yes " bootproto=" DHCP "  service network restartping www.baidu.com can ping the instructions are connected

A variety of problem solutions for configuring CentOS 6.0+ networks with VMware