Script house Common server software
Quick navigation
Your location: Home page > Operating system > Other systems> can't host vmware virtual machine

Vmware virtual machine can't ping the host of the solution

Release date: 2022-09-08 14:09:59 author: unknown I want to review
What Can I Do if the vmware VM fails to ping the host? First of all, we need to know the reasons, in order to correspond to the solution, below we analyze from many aspects, please see the details below

This article mainly introduces the causes and solutions of vmware virtual machine ping failure, which is a problem that troubles many users. The article is very detailed, interested users must read it!

1. Vm hosts cannot ping each other

Problem 1: Firewall

Omit, it is recommended that both the host and the host turn off the firewall and turn off seLinux (Linux security system).

Fault 2: The network adapter has not taken effect

expression

If the output NIC information does not contain inet [ip address], the NIC does not take effect.

After the NIC takes effect, it becomes:

The solution:

This is caused by an incorrect network adapter configuration file. CentOS7 System NIC configuration file path:

/etc/sysconfig/network-scripts/ifcfg- [NIC name]

The NIC name is the leftmost column of the ifconfig command output

eg: /etc/sysconfig/network-scripts/ifcfg-ens32

Configuration file contents:

If you have not modified this file, then you only need to add the IP address related to IPADDR NETMASK GATEWAY DNS1, and preferably change the green dot configuration to enable boot.

If you have multiple network cards, the red dots configure different items for each network card. If a UUID is lost, run the uuidgen command to regenerate it. The author mistakenly added the synchronization option -s when obtaining the ens34 network card through cp copying the ens32 network card, resulting in the loss of the ens32 UUID, and the network card took effect after the modification.

Problem 3: IP address, gateway, DNS facility

Specific how to set up online tutorials many. In short, it is

The IP address of the Windows virtual network adapter VMnet8 and the subnet IP address of the VMWare virtual network adapter VMnet8 are in the same LAN as the IPADDR of the network adapter configuration file.

The gateway and DNS address of the Windows virtual NIC VMnet8 are the same as those of the VMWare virtual NIC.

All of the above are in the same LAN (the third number of IP addresses, here 80).

Host Settings:

To set the VM, go to Edit > Virtual Network Editor

2. The VM cannot ping the host, but it can ping the Internet

Fault 1: Virtual NIC VMnet8

The communication between a VM and a host is implemented through the VMware Network Adapter VMnet8. For details about its functions, see the following experiment to disable the virtual network adapter:

Control Panel -> Network and Internet-> Network and Sharing Center -> Change Adapter Settings

If VMnet8 is disabled, the host cannot communicate with the VM, but can communicate with the external network (because the VM and the host share the same network adapter) as follows:

If VMNet8 is not disabled, also cannot rule out its problems, may be it is a problem with the Settings, a see.

Fault 2: Network switchover during VM startup

If the ladder is hung, switch the WIFI. This operation makes the gateway change, the essence is still the cause of virtual network adapter VMnet8.

Question 3: the firewall

It is recommended to turn it off.

The above is about the vmware virtual machine ping host of various reasons analysis and solutions, I hope you like, please continue to pay attention to the script home.

Related recommendations:

What to Do about the Green Screen of Windows 11 VMS? Windows 11 startup Vmware VM green screen solution

  • Tag: VMware virtual machine host

Related article

Latest comments

Follow the wechat public account

扫一扫