IP access Problems with "VMware Workstation Pro" DHCP

In fact my service has set a fixed IP address, but I will always see this annoying one (169. x.x.x, as shown), and directly affect my use of the situation. Initially, I was the problem with my Windows server, but the results told me it wasn't.

When I initiated the ad service, I didn't notice the situation, and all the machines under it didn't add up to the domain, OMG.

Network settings will also see

Try a Windows network reset, but I found that this feature doesn't work at all.

Later in the search, people said it was a DHCP server problem, and the problem was that I didn't have a DHCP server.

They also say that you can use this command, and the results tell me it's useless.

To think about it, I'm going to be a problem, adding a Web card to the server, and then seeing (169. x.x.x)

In order to be my service mirror has a problem, and then re-install one, the result is still seen (169. x.x.x)

Eventually returning to the place where the problem was originally discovered, IP,DHCP, decided to close VMware's DHCP, and still see (169. x.x.x)

OK, reset dhcp, subnet IP as you like any settings

The problem was resolved, and could never be seen (169. x.x.x) of the IP segment.

The IP settings of the network card are finally normal. In fact, VMware's DHCP, the general problem, directly reset it, may bring you unexpected results.

IP access Problems with "VMware Workstation Pro" DHCP