SECURECRT Unable to connect to virtual machine linux-Virtual network adapter (NAT) IP (169.254.xx.xx) Invalid problem __linux

Problem background:

A long time useless notebook, suddenly brought back to use when the SECURECRT unable to connect to the virtual machine Linux problem, has also encountered this problem, basically this problem is caused by the following:

1. Virtual machine Linux firewall is not closed;

2. Virtual machine Linux does not have SSH service installed;

3. Virtual machine Linux SSH service port (port 22nd) is not open;

4. Virtual Machine Linux Network configuration is not correct, the gateway configuration is not correct, IP configuration is not correct;

All these problems, Baidu has a corresponding solution, here no longer one by one repeat. Today I'm going to talk about a new problem: Virtual Machine network card (NAT) IP invalidation problem. The situation: to review my painful experience in order to solve this problem, SECURECRT can not connect to the virtual machine Linux, I first thought of the beginning of the four cases, I tried to verify the results are not the above problems. The problems I have when I check the network status of the virtual machine Linux and host are as follows: 1. Virtual machines can ping the host, but the host cannot ping the virtual machine:
2. The host cannot ping the virtual machine:
Later, after questioning, the steps above are wrong. Virtual Machine network card if it is NAT way not to see the wireless network connection, but look at the VMNET8 virtual network card. Unless a USB wireless card is used in the virtual machine. Or to ping the wireless network card IP went. 3. View the network configuration of the VMNET8 virtual network card as follows:
Later, after the guidance of other people know that it is the virtual machine of their own virtual network connection errors, was assigned an invalid IP. In the computer network mentioned in the 169.254.xx.xx beginning of IP are invalid IP ... or the foundation of the computer network did not play firm AH. I was taught this time ... Workaround: 1. Open Network and Sharing Center
2. Configure the Virtual network card (Nat way) VMnet8 IP, gateway and other information:
3. The configuration of the virtual network card depends on the actual situation:
OK, in accordance with the above steps can solve the problem, think back to the original solution process, Baidu said is that I started to mention the four kinds of situation, did not find the solution to this problem, it is a pain ah, then consulted the high man, solve the problem.