VMware Workstation Installation Use notes

0. Operating Environment

VMware Workstation version: vmware-workstation-full-7.0.0-203739+ Perfect Chinese patch.

Host system Environment: Windows Server 2003 Enterprise Edition. Intel Pentium 4 Dual core cpu,1g memory, single physical network card, LAN connection, fixed ip:10.10.10.10/24.

Virtual machine system environment: Windows XP Professional SP3. Hereinafter referred to as "XP virtual machine".

1. Installing VMware Workstation and virtual machines

During installation, the serial number is generated by the registration machine, and the installation process is simple and smooth. After that, install a Windows XP Professional SP3 virtual machine system, set the memory to 256M, the other is the default setting, the installation process is slightly.

2.2 New Connection (virtual network card) in "Network Connection" after installation

(1) VMware Network Adapter VMnet1. Fixed ip:192.168.8.1/24 is used by default.

(2) VMware Network Adapter VMnet8. Fixed ip:192.168.150.1/24 is used by default.

In this way, the host has three network cards, respectively, ① physical network card, ②vmware network Adapter VMnet1 Virtual network card, ③vmware network Adapter VMnet8 virtual network card.

3.5 new services in system services after installation

(1) VMware Agent Service. It is possible to give services that are provided to enterprise-level users, and it is recommended that you close.

(2) VMware Authorization Service. Service Description: Authorization and authentication Service for starting and accessing virtual machines. VMware's certification services for product legitimacy, recommendations: close.

(3) VMware DHCP Service. Service Description: DHCP Service for virtual networks.

(4) VMware NAT Service. Service Description: Network address translation for virtual networks.

(5) VMware USB arbitration Service.

4. Run the program "Virtualnetwork Editor" to see the situation

There are vmnet0-9 a total of 10 virtual networks. which

(1) VMnet0 default is bridged type.

(2) VMnet1 default is host-only type. VMnet1 Network address is 192.168.8.0/24, the host in the network uses the DHCP service to assign IP, the scope is: 192.168.8.128/24-192.168.8.254/24. The VMnet1 webcast address is: 192.168.8.255.

(3) VMnet8 default to NAT type. VMnet8 Network address is 192.168.150.0/24, the host in the network uses the DHCP service to assign IP, the scope is: 192.168.150.128/24-192.168.150.254/24. The VMnet1 webcast address is: 192.168.8.255. The default NAT gateway address is: 192.168.150.2/24.

5. Implementing the virtual machine's communication in the VMNET0 network (bridged type)

Set the "Network Adapter" for the XP virtual machine to the bridged type.

Start the XP virtual machine and configure the fixed ip:10.10.10.12/24 (the IP address of the same network segment as the host). After that, the XP virtual machine is like a physical host on the same physical LAN as the host, and can communicate with the host (IP:10.10.10.10/24) and other hosts on the LAN. In short, the host has the same characteristics (in addition to IP), host can access the external network (such as the Internet), XP virtual machine can also be accessed.

The principle of bridged network is as follows:

6. Implementing the virtual machine's communication in the VMNET1 network (host-only type)

Set the "Network Adapter" for the XP virtual machine to the host-only type. Start the XP virtual machine and configure it to "Get IP address automatically". The VMware DHCP Service service automatically assigns an IP to the XP virtual machine, such as: 192.168.8.128/24, and the default gateway is empty.

XP virtual machine can access the host (IP:192.168.8.1/24), note that the host has three network cards, respectively, the ① physical network card, ②vmware network Adapter VMnet1 virtual network card; ③vmware Network Adapter VMnet8 Virtual network card.

VMNET1 is an independent network, in addition to the host (IP:192.168.8.1/24) can communicate with the outside, unable to actively communicate with the external.

However, if you install the appropriate routing or proxy software on the host, you can also communicate with the outside world (without experimentation) to enable packet forwarding.

The principle of Host-only network is as follows:

7. Implement the virtual machine communication in the VMNET8 network (NAT type) 7.1. Intranet Access Extranet

Set the "Network Adapter" for the XP virtual machine to the NAT type. Start the XP virtual machine and configure it to "Get IP address automatically". The VMware DHCP Service service automatically assigns an IP to the XP virtual machine, such as: 192.168.150.128/24, and the default gateway is 192.168.150.2/24.

XP virtual machine can access the host (IP:192.168.150.1/24), note that the host has three network cards, respectively, the ① physical network card, ②vmware network Adapter VMnet1 virtual network card; ③vmware Network Adapter VMnet8 Virtual network card.

XP virtual machines can access the host (IP:192.168.8.1/24), and XP virtual machines can access other virtual machines (such as 192.168.8.129/24) in a virtual network (VMNET1) connected to a host (IP:192.168.8.1/24).

The XP virtual machine can access the host (IP:10.10.10.10/24, physical network card), the XP virtual machine can access the host (IP:10.10.10.10/24, physical NIC) connected to the physical networks of other physical hosts.

However, the external physical host cannot actively access the XP virtual machine, and the virtual host in VMNET1 cannot actively access the XP virtual machine, that is, the host outside the VMNET8 network cannot actively access the XP virtual machine.

The principle of NAT networking is as follows:

7.2. External Network Access Intranet

The port forwarding function can be configured manually to enable the extranet host to access the XP virtual host.

Assuming that an XP virtual host deploys an HTTP Web site on port 80, a fixed port mapping (forwarding) policy needs to be added to "Port Forwarding" to enable the extranet to access the site on the XP virtual host. In the configuration shown, the TCP packets sent to the host 8080 port on the extranet are forwarded to the 80 port of the XP virtual machine (IP:192.168.150.128/24), and all TCP packets from the XP virtual machine 80 port to the host 8080 port are forwarded to the appropriate extranet. The communication process is illustrated as follows (note: Communication is initiated first by the extranet host):

External host (random port)<――> host (8080 port)<――>XP virtual machine (80 port)

Figure 8 NAT Communication Process

In this way, the host (physical host or bridged virtual machine) in the VMNET0 network (bridged type) can access the Web site in the XP virtual machine by entering "http://10.10.10.10:8080" in the browser address bar. Note: 10.10.10.10 is the physical NIC IP address of the host.

Virtual hosts in the VMnet1 network (host-only type) can access sites in the XP virtual machine by entering "http://192.168.8.1:8080" in the browser address bar. Note: 192.168.8.1 is the VMNET1 virtual network card IP address of the host.

Note: For the port mapping policy not to fail after restarting the XP virtual machine, it is recommended to set the IP of the XP virtual machine to a fixed IP, avoiding the IP inconsistency in the port mapping policy after the IP is automatically assigned.

7.3. Thinking

If you understand Figure 8, and then think back to the "7.1 Intranet access outside the Network" section, the external network host why can not access the host in the VMnet8?

The reason is that when an XP virtual machine accesses an extranet host, the host automatically dispatches a random port responsible for packet forwarding. Extranet users do not know this random port, so they cannot initiate an unsolicited visit. However, the communication program of the extranet host can identify the host communication port in the packet, so it knows the current random communication port of the loopback packet to the host, thus realizing the communication with the XP virtual machine.

The fact is: the party that initiates the visit needs to know the situation on the end.

It is known that the party can communicate.

Reference articles

[1] Jianwei Zhuge Wei. The construction of the network Attack and Defense experiment environment based on the third generation Honey Network (version 2010 20100920 update).

Xiachuntao [email protected]

October 12, 2012

VMware Workstation Installation Use notes