Shulou(Shulou.com)06/02 Report--

Problem description: the Nic file / etc/sysconfig/network-scripts/ifcfg-eth0 of the linux system has been configured before, and the public network can be accessed normally depending on the NAT service. However, after the computer was shut down unexpectedly, VMware was forcibly shut down, and when the VMware was booted again, it was found that the remote connection tool could not connect to the linux in the virtual machine, and ping each other's ip address in the cmd and the virtual machine. It was found that the ping could not be connected and the linux could not access the external network.

Solution: two solutions have been found so far

(1) after shutting down the linux system, click the "Virtual Network Editor" button under the "Edit" option in the menu bar in the VMware, then figure 1 will appear and click to restore the default configuration (remember to close the linux system here, otherwise you can't click; sometimes open this window will be very stuck, you can close and open again).

Figure 1

After clicking the button above, the VMware software will automatically reinstall (uninstall and then install) the network adapter located in windows, as shown in figure 2.

Figure 2

This process needs to wait 1-2 minutes (the specific time varies according to the performance of the PC), and then configure the ip address in the ifcfg-eth0 on the same LAN according to the subnet ip address in NAT mode in figure 1, and then you can ping the extranet.

(2) there is no need to reset the VMware network, just restart the 4 VMware-related services in the task manager (the Workstations Server corresponding to VMwareHostd is a shared service for VMware software, never mind). (the second method is recommended)

Specific steps: 1. Use the shortcut key Ctrl+Shift+ESC to bring up the task manager interface (of course, you can also open it with the right mouse button on the taskbar under the desktop, but the shortcut key), and select the last "service" after opening, and the interface shown in figure 3 will appear.

Figure 3

You can find that the services related to VMware have stopped working. Here, it should be that these services are shut down abnormally after VMware is forcibly shut down, and then cannot be started automatically after starting VMware; so you need to manually right-click to "start" these services, and then you can magically find that the linux system can connect to the external network normally again, as shown in figure 4.

Figure 4

Conclusion: after VMware is accidentally forced to shut down, the relevant services can not be automatically turned on when it is started again, resulting in the failure of linux using NAT services to connect to the Internet. I feel that this is a "eight elder brother" of VMware. (note: the VMware version here is 10.0.0 build-1295980, and other versions have not been tested for this problem. )

The above is the whole content of this article, I hope it will be helpful to your study, and I also hope that you will support it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.