Host and VMware Virtual Machine Communication (XP edition)

One, with the host to share ADSL link/wireless network (virtual machine within the Internet)

After installing the virtual machine, there are two new links under the network link, including the VMware Network Adapter VMnet1 and the VMware Network Adapter VMnet8, in addition to the local links. Where VMnet1 is not very useful here, we mainly focus on VMnet8, because VMnet8 is used to share the IP address of the host.

A Virtual machine settings: Menu-Virtual machine-Removable devices-Ethernet-edit-Custom-vmnet8 B virtual machine XP system settings: Local link tcp/ip-auto get IP address C host XP system settings: ADSL Properties-Advanced-allow other computers to-vmnet8

Second, share the directory file with the host

Method One: The use of local area network communication tools, such as flying Pigeon book software, so that the two machines can pass the file (of course, do not do method two, the system does not have this communication tool, but can be shared by means of the ADSL link to download a network)

A Virtual machine settings: Menu-Virtual machine-Removable devices-Ethernet-edit-Custom-vmnet default bridging B host XP system settings: Local link tcp/ip-configuration IP (eg:192.168.0.1) C virtual machine XP system settings: Local link tcp/ip-Configure IP (eg:192.168.0.2)

Method Two: Set the domain name, workgroup, access the shared directory via IP

A host XP system settings: My Computer Properties-computer name-change-Enter computer name (EG:XP)-Enter Workgroup (eg:home) B Virtual machine XP system settings: My Computer Properties-computer name-change-Enter computer name (eg:test)-Other-Enter the primary DNS suffix (note: You must enter the host computer name, EG:XP)-Enter Workgroup (note: Must be set with host, Eg:home)

C Restart the virtual machine XP system, and then you can see the shared directory in the Network Neighborhood (first set up a shared directory on the host), instead, the host can also see the virtual XP system share directory in the Network Neighborhood, in addition, through IP can also access

3.

The host is the WindowsXP system, and the Linux operating system is installed in the VMware virtual machine. After VMware is installed, there are two new connections in the host's network connection, the VMware network Adapter VMnet1 and the VMware Network Adapter VMnet8. The system installed in the virtual machine is connected by these two virtual network cards. such as

Similar antiarp firewall on the host must be turned off or the virtual machine will not be able to surf

There are several options: 1, bridged (bridge) mode: If the host is Internet access through the LAN, the virtual machine can be used with the host network segment, gateway and DNS, such as the same settings, choose a valid LAN IP.

Bridging mode enables virtual machines <---> Host virtual machines <----> Internet communications (Hosts and VMS can be seen as two machines on the same LAN). However, bridging requires a separate IP address that differs from the original machine, which is difficult to do in some cases (IP and Mac bindings, network management does not agree). And the host unplug the network cable, the virtual machine can not communicate with the host over the Internet way. And the latter few do not have this problem. So we don't use bridging.

1) IP information of the host

2) Set the VMware network connection to bridged

3) Virtual machine system Network settings

Multi-nic bridging when I have dual NIC, although vmnet0:bridged to an automatically chosen adapter (in VMware edit->virtual network Settings ... Open Virtual Network Editor)

However, I tried, the virtual machine can only bridge "local connection" (via network card), cannot bridge "local Area Connection 2" (Realtek network card)

In the virtual Network Editor, Automatic bridging tab

If we want to bridge the "local Connection 2" (Realtek network card) need to "Exclude adapters" add "via Network card" (local connection), so that "local connection 2" can be bridged. However, "local connection" (via network card) is not possible, even in "Exclude adapters" remove "via network card" is not, I guess VMware only support a first not excluded Nic Bridge!

It's okay, we can select the Realtek network card in the virtual network Editor, Host Virtual Network Mapping tab, VMnet2

At this point, we go back to the virtual network Editor--Automatic bridging tab and found that VMnet0 removed the Realtek NIC

When bridging the "local Connection" (via network card), VMware chooses VMnet0,

When bridging "Local Area Connection 2" (Realtek NIC), VMware chooses VMnet2

Virtual machine on the network corresponding to the settings on it.

2. Nat mode: Using the NAT and DHCP services provided by VMware, the virtual machine uses the virtual network card VMnet8 as the gateway in the host, and the TCP/IP settings follow the DHCP and NAT settings of the program regarding VMNET8. such as IP must be between its DHCP settings StartIP and ENDIP, the gateway needs to use its NAT settings for the Gateway IP. Nat means virtual machine <---> host communication, but virtual machine---> Internet is only able to access the Internet by virtual machine, but if you want to use the virtual machine as a server, Internet access is not allowed. However, if you have more than one network card, the virtual machine can access multiple network cards connected to the Internet without changing the settings. 1) Set up VMware Network connections as Nat

2) in the virtual machine, Linux network settings, just choose to automatically get the IP, you can!

Of course, can also be set manually: IP settings and vmnet8 same network segment, gateway,netmask,broadcast settings and vmnet8, the same DNS settings as the host. We are in the host network connection as follows, do not see the gateway (such as)

Don't worry, at VMware's edit->virtual Network settings ... , there are related content.

These tabs contain many of the advanced settings of VMware and are interested in research.

3.host-only mode: Default to use Vmnet1, the virtual machine IP settings and vmnet1 same network segment, gateway set to Vmnet1 IP, the rest of the same settings as VMNET1, the same DNS settings as the host such as Vmnet1 IP : 192.168.101.1 Virtual machine settings: ip:192.168.101.100 gateway:192.168.101.1 This enables virtual machine <---> host communication, but virtual machines <---> The Internet is still unable to communicate 1) Choose VMware's Host-only

2) Local connection of the host

3) in virtual Machine Linux, set up the network

4. How to share the host's Internet connection (if the host is a Win98 system may not be applicable): share an Internet connection in the advanced of the local Area Connection property of the host. If you choose the VMNET1 virtual network card, then the Ethernet settings in VMware need to choose Host-only, if you choose VMnet8, then the Ethernet setting requires NAT. After you share the connection, The selected virtual network card IP will default to be set to 192.168.0.1 (if the host is also through the LAN 192.168.0.1 gateway to the Internet, you need to set this virtual network card as a different network segment IP, such as 192.168.1.1) the virtual machine inside can be the virtual network card as a gateway to the Internet 。 is actually a simple route NAT, so the NAT mode is not discussed, we only take host-only as an example. Shared host-only mode enables virtual machine <---> host communication, but virtual machine---> Internet is only able to access the Internet by virtual machines, but if you want to use the virtual machine as a server for Internet access, it is not possible. 1) Select VMware's host-only

2) Set local connection properties for the host

The IP of the selected virtual network card is set to 192.168 by default. 0.1, and of course it can be changed. And after the shared connection is canceled, it also changes back to the network settings before the shared connection.

In virtual machine Linux, set up the network:

Summarize:

Share connection mode and NAT mode, can realize virtual machine <---> host, virtual Machine---> Internet communication, Nat mode is easy to set up, and can access multiple physical network card simultaneously. Bridging mode enables virtual machines <---> Host virtual machines <----> Internet communication, which is only possible if the virtual machine is a server. However, a separate IP is required for the virtual machine, and if the physical network card is disconnected, the virtual machine and the host cannot connect. The Host-only method only implements virtual machine <---> host communication, which is generally not used alone.

Like me in the virtual machine under the development of embedded, virtual confidential to the Development Board to provide NFS services, the use of bridging mode to connect the embedded network card. If you sometimes want to download the software, check the data, you can use the NAT method, very convenient

Host and VMware Virtual Machine Communication (XP edition) (RPM)