Vmwarevm Nic mode resolution

VMWARE is a good tool for self-learning.
We can use VMWare to create an independent virtual server in the LAN to provide network services for LAN users.
You can also create a virtual system that is isolated from other machines in the network for special debugging.
To make good use of the virtual machine, you must know how to select the NIC mode of the Virtual Machine www.2cto.com

(I) VMWARE Nic Mode

① Bridged (Bridging Mode)

In this mode, the Virtual Operating System of VMWare is like an independent host in the LAN.
It can access any machine in the LAN
In the bridge mode, you need to manually configure the IP address and subnet mask for the virtual system, and also be in the same network segment as the host machine.
In this way, the virtual system can communicate with the host machine.
At the same time, because this virtual system is an independent host system in the LAN
You can manually configure its TCP/IP configuration information to access the Internet through a LAN gateway or router.
The relationship between a virtual system in the bridge mode and the host machine is like connecting two computers on the same Hub.
If you want them to communicate with each other, You need to configure the IP address and subnet mask for the virtual system. Otherwise, the communication will fail.
If you want to use VMWare to create a virtual server in the LAN to provide network services for LAN users, you should select the Bridge Mode www.2cto.com

In this mode, the IP address of the Guest OS can be set to the same network segment as the Host OS.
Guest OS is equivalent to an independent machine in the network. Other machines in the network can access Guest OS.
Guest OS can also access other machines in the network. Of course, the two-way access to the Host OS is not a problem.
In this way, it is the most convenient, because Guest is like a physical computer in a LAN.
You can even obtain the IP address ② NAT from the DHCP server of the LAN (network address translation mode)

The NAT mode enables the virtual system to use the NAT (Network Address Translation) function to access the public network through the network where the host machine is located.
That is to say, you can use the NAT mode to access the Internet in a virtual system.
In NAT mode, the TCP/IP configuration information of the virtual system is provided by the DHCP server of the VMnet8 (NAT) Virtual Network and cannot be manually modified.
Therefore, the virtual system cannot communicate with other real hosts in the local area network.
The biggest advantage of using the NAT mode is that it is very easy for the virtual system to access the Internet. You do not need to configure any other configurations, but only need the host machine to access the Internet.
If you want to use VMWare to install a new virtual system, you can directly access the Internet without manual configuration in the virtual system. We recommend that you use the NAT mode.

NAT can also achieve two-way access between Host OS and Guest OS.
However, other machines in the network where the Host is located cannot access the Guest OS. The Guest OS can access other machines in the network through the Host OS NAT protocol.
The nat ip Address Configuration method is to assign an IP address to the virtual DHCP server of VMware.
The route has been set in this IP address, which is to point to the host-only (host mode) of 192.168.138.1)

In some special network debugging environments, you must isolate the real environment from the virtual environment. In this case, you can use the host-only mode.
In host-only mode, all virtual systems can communicate with each other, but the virtual system and the real network are isolated.
In host-only mode, the virtual system and the host machine system can communicate with each other, equivalent to the two machines connected through twisted pair wires.
In host-only mode, the TCP/IP configuration information of the virtual system (such as the IP address, gateway address, and DNS server)
All DHCP servers in the VMnet1 (host-only) virtual network are allocated dynamically.
If you want to use VMWare to create a virtual system isolated from other machines in the network and perform some special network debugging, you can select the host-only mode.

In this mode, the DHCP server allocates the IP address of Guest.
And communication can be maintained between 192.168.222.X.
But on the Guest machine, the address 172.16.1.210 of the Host cannot be pinged.
Because the communication is restricted on the Host (so it is called Host Only)
This method looks like NAT, but in this mode, Guest can only communicate with the Host, but cannot communicate with the computer on the LAN, unless the HOST is forwarded or the routing prompt: the above mentioned VMnet8 Virtual Network in NAT mode, VMnet1 Virtual Network in host-only mode, and VMnet0 Virtual Network in bridged Mode
They are all generated based on the automatic configuration of the vmwarevm and do not need to be set by the user. VMnet8 and VMnet1 provide the DHCP service, while VMnet0 does not provide the network configuration path on the VM: view the network configuration on the local machine: