VMware does not have VMnet0, VMnet8 on the host, the solution

  At the beginning, I sat on the computer and experimented, but I couldn't figure out why the client on the virtual machine could ping its own IP or its own IP, but the host could not ping the guest of the virtual machine, nor could it ping the virtual machine. gateway.

After trying various questions, I also found a lot of questions:

   1. On the host, there is nothing in the Ethernet properties. The box used for connection + this connection uses the following items (o), and there is nothing in it. When you click on the configuration, there is still nothing.

 

Solution: 
1. Enter the registry [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}] and export it for backup first.
2. Check the [item] (0000, 0001 to 00xx) under it one by one, and see which item on the right has the [value]: "DriverDesc"="VMware Virtual Ethernet Adapter for VMnet1".
3. After finding it, add a "DWORD" value (32 bits), the name is "*NdisDeviceType" (* is required), and the data value is changed to "1".
4. In the same way, find VMnet8 again, repeat steps 2~3, and add the value.

 

 but! ! ! !
There is no "DriverDesc"="VMware Virtual Ethernet Adapter for VMnet1" key in my registry

 

   2. From question 1, I led to question 2, the Network setup server in the service is always turned off automatically,

    To this end, I have checked countless ways, only one is effective, for me, that is to start the Network setup server,

At the same time, click the properties of Ethernet, but it still disappears after clicking OK. It is said on the Internet that it is good to try several times. I tried several times and restarted the computer. It is really OK, but! ! ! Whether the "Connect the host virtual adapter to this network" on the virtual machine is automatically unchecked

 

 

 

 When you face the problem, face the continuous blows for several days, and think about reinstalling the system, the most surprising thing is:

                                      This problem is actually very simple, it is just a problem with your software VMware, just fix VMware! ! ! ! ! ! !

 

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325017232&siteId=291194637