Windows systems communicate with VMware virtual machines through host mode

VMware's friends know that VMware has 5 network connectivity modes,

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/86/3C/wKiom1e5rciTBqB-AAAbW-20f24213.png "title=" 1.png " alt= "Wkiom1e5rcitbqb-aaabw-20f24213.png"/>

Perhaps everyone is more familiar with the bridge mode, Nat mode, only the host mode, usually for the experiment will be the virtual network set as a bridge mode, this may direct communication. Today we are talking about the 4th, custom mode.

The first step, create a new VMware Virtual network card, you can see, I vmnet2 not turn on DHCP, and then you can also use the VMNET1 because the type is the same. About this host-only mode is the use of VMnet1, using this online our normal use of the system is no way to communicate with the virtual machine your computer.

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M02/86/3C/wKioL1e5rkCReHoTAABpEQ2TmQY171.png "title=" 2.png " alt= "Wkiol1e5rkcrehotaabpeq2tmqy171.png"/>

But sometimes we experiment with the need to create a virtual network environment that belongs to us without affecting our actual network usage. You need to use this. Inability to communicate is also its disadvantage. That's why I chose to customize instead of just using the host, I wanted to create a new network environment instead of using a virtual DHCP network service. Of course if you close VMnet1 DHCP can also use the VMnet1 directly, the result of using VMnet1 is the back I use VMnet2 place all to Vmnet1.

The second step is to add the virtual network card to the system.

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/86/3C/wKioL1e5sGHSmbLbAACnTZS6YlI063.png "style=" float: none; "title=" 3.png "alt=" Wkiol1e5sghsmblbaacntzs6yli063.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/86/3C/wKioL1e5sGHh6aF1AAA_5QP3tEw951.png "style=" float: none; "title=" 4.png "alt=" Wkiol1e5sghh6af1aaa_5qp3tew951.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/86/3C/wKioL1e5sGLCF30uAABR-syCPqk209.png "style=" float: none; "title=" 5.png "alt=" Wkiol1e5sglcf30uaabr-sycpqk209.png "/>

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/86/3C/wKiom1e5sGPizx04AAB0OC-epc4692.png "style=" float: none; "title=" 6.png "alt=" Wkiom1e5sgpizx04aab0oc-epc4692.png "/>

The above step is to add a local loopback, the network knows the classmate may ask, that is not the use of the machine, it is true, but we do not forget that we are new, the system has been added before we have a loopback port, and will not affect the system, so rest assured that add

Step Three

Open "Network and Sharing Center" to find the NIC for Vmnet2 and the local loopback port we added, press CTRL double Select right click to choose Bridge to generate a bridged network

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/86/3D/wKiom1e5sgDwEd-gAADaQ9xPF5g839.png "title=" 7.png " alt= "Wkiom1e5sgdwed-gaadaq9xpf5g839.png"/>

Fourth Step

Configure the IP address on the bridged network and the network in the virtual machine to work properly. This network is independent, inside and outside of the communication is through our infrequently used bridge

This article from "Rookie Small white" blog, please be sure to keep this source http://changelee.blog.51cto.com/4581245/1840904

Windows systems communicate with VMware virtual machines through host mode