Many friends use VMware to test different systems. I am in conjunction with my own experience. I will refer to network settings. Please correct it. Bridge: This way is the simplest, directly connecting the virtual Net Bridge to a physical network card, and Linux next network card binds two different addresses,
In order to set the network card to a mixed mode, it can achieve the ability to listen to multiple IPs. In this mode, the network card inside the virtual machine (such as the ETH0 under Linux) is directly connected to the network where the physical network is located, you can imagine For virtual machines and host
The machine is in the right position, equally on the network relationship, no one behind the problem. It is very simple to use this way, the premise is that you can get more than 1 address. For friends who want to make various network experiments Too suitable, because you can't make virtual
The simultaneous network is controlled, it goes out. NAT mode: This mode has a virtual network card VMNet8 in Host (by default), if you have experience in the NAT server, here
VMNET8 is equivalent to the NIC connected to the intranet, and the virtual machine itself is equivalent to the machine running on the Internet, the network card in the virtual machine (Eth0) is independent of
Vmnet8. You will find that in this way, VMware's own DHCP will be loaded on the VMNet8 interface by default, so that virtual machines can use DHCP services. More important
The VMware has brought the NAT service, providing address translation from the VMNet8 to the external network, so this is a real NAT server running,
It is only for virtual machine. It is clear that if you only have an external network address, this method is very suitable. Hostonly: This should be the most flexible way, if you are interested, you can carry out various network experiments. And NAT unique Different, in this way, there is no address conversion service
Therefore, by default, virtual machines can only go to host access, which is also the meaning of Hostonly's name. By default, there will be a DHCP service to be loaded on VMNet1. This virtual machine connected to VMNET8 can still be set to DHCP, convenient system
Set. Is there any way to connect to the external network, of course, in fact, this way is more flexible, you can use your own way, thus achieving the most
Ideally configure, for example: a. Use your DHCP service: First stop VMware's own DHCP service, making DHCP services more uniform. B. Using your own NAT, easy to join the firewall .Windows Host can do NAT method, Simple intends, complex, such as Windows XP
As the NAT service in Windows Server. C. Use your own firewall. Because you can fully control the VMNet1, you can join (or experiment) the firewall between the VMNet1 and the external network. From the above, Hostonly mode Similar to ordinary NAT Server with the internet access, so you can make it easy to do with
Off experiment, such as fire and strong settings, etc.
1, Bridge mode (everything is like Host, only IP cannot be the same with Host) IP 192.168.39.222Netmask: 255.255.252.254primary Nameserve: 192.168.39.252
2, NAT mode first views VMNET8 IP (EG 192.168.255.1) in Host. Start VMware, point EDIT under Virtual Network Setting ..., pop up the Virtual Network Editor dialog box; look at the NAT tab, record NAT Gateway IP Address: 192.168.255.2 In Config, fill in: IP: 192.168.255.5 (Different addresses with 192.168.255.1 in the same network segment) NETMASK: 255.255.255.0 (same as 192.168.255.1) Gateway IP: Fill in VMware NAT gateway 192.168.255.2primary Nameserver: Fill in the same gateway 192.168.39.252 as the host, so you can surf the Internet. If you fill in 192.168.255.1, you can't connect to the outside network. You can not stop here, in short, you can't write mistakes. address
3, Hostonly mode (1) View the properties of your connection network card, select "Advanced" tab, set to allow sharing, and set the allowed network interface to VMNet1
(2) Take a look at your VMNet1 properties, look at the TCP / IP protocol settings, you have found that it has been automatically set to 192.168.0.1/255.255.255.0,
(3) The settings under Windows are completed, transfer to the virtual machine running Linux. Set the IP address of your ETH0 to static (if there is no static when installing)
Press Red Hat Icon -> System Settings -> Network (or other you understand) IP: 192.168.0.2 (or other address on this segment) NetMask: 255.255.255.0 Default Gateway: 192.168.0.1 (VMNet1 address DNS: Enter your own DNS (DNS in Host) Save Setup. If you haven't set a host name yet: CD / ETC / Sysconfig Vi NetWork Edit Hostname CD / ETC VI HOSTS Join: 192.168.0.2 YourHostname Restart Service SU / SBIN / Service Network Restart (4) Test the gateway: ping 192.168.0.1 DNS: Ping DNSSERVER
=========================================== in this way, the IP of the virtual system can be set to the native system In the same network segment, the virtual system is equivalent to a separate machine in the network, plugging with this unit.
On a HUB, other machines within the network can access the virtual system, and the virtual system can also access other machines in the network, of course, the two-way access to the unit system is not
Problem. (2) NAT mode can also achieve two-way access to the virtual system in this way. But other machines in the network cannot access the virtual system, the virtual system can pass the system
IP address configuration method for other machines in the network in the network: Virtual system automatically obtains IP addresses with DHCP, the VMware Services in this unit assigns a virtual system
IP, after you want to use fixed IP every time you start, you can set this IP directly in the virtual system. (3) Host-Only Method Requests This method can only perform network communication between virtual machines and hosts Other machines in the network cannot access virtual systems, and virtual systems cannot access
Ask other machines. (4) NOT USE is not only using the network, the virtual system is a single machine.
In general, Bridged methods are most convenient to use. But if the unit is Win2000 and the network cable is not plugged (or there is no network card), the network is likely to be unavailable (
Most of the machines with the PCI network card are like this), at this time, you can only use the NAT mode or Host-Only, the two virtual network cards mentioned before, to adapt to these two networks.
The support is prepared.
