For most people who use the VMware Player, DHCP is good enough for the NAT network. That means the IP addresses of your virtual machines may change after each powering on.
What if you want to have static IP addresses? It’s pretty easy as long as it’s in the same subnet. For example, if the VMnet8 has IP address of 192.168.47.1, your virtual machines should be configured in the same network say 192.168.47.x, where X can be any value from 3 to 254 (2 reserved for gateway, 255 broadcast by default).
Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.
I found the subnet for NAT network is not consistent. One of my VMware Player installation has 192.168.47.1 on VMnet8; the other 192.168.16.1. I think the subnet value is randomly picked by installer as I don’t remember it’s prompted anywhere.
Given that, your virtual machine with static IP address may not run as it’s moved from one VMware Player to another even of the same version. To solve the problem, you can either change your VM network setting to fit into the new VMware Player, or change the subnet setting for VMware Player.
After searching the Internet, I found the Virtual Network Editor can do the job. Unfortunately it’s exposed only in the VMware Workstation, not the VMware Player. It’s understandable because VMware wants you to upgrade from the free VMware Player to the paid VMware Workstation.
With more research, I bumped into a blog article with a few steps to hack out the editor from the installer package. Within its comment, a much simpler solution is offered with a link back to a posting at VMware Community. It basically says it’s hidden but it’s there for you to use. The command to bring up the Virtual Network Editor is as follows:
rundll32.exe vmnetui.dll VMNetUI_ShowStandalone
This command has to be run under the name of administrator, not just a user with administrator privilege. Because my home computer is OEM Windows 7 Home Edition, I don’t have administrator account enabled. Therefore, the “RunAs” command does not work for me.
The easiest way to work around it, as I found from this page , is to right click Command Prompt from Start button and pick the “Run as administrator” from the context menu. The command window then has title “Administrator: C:\Windows\System32\cmd.exe.” In this window you can type in the command to the “Virtual Network Editor” as shown in below. From there, you can change all sorts of network settings.
If you use Linux version of VMware Player, you can do something similar according to this page. The related commands are:
cd /usr/lib/vmware/bin ln -s /usr/lib/vmware/bin/appLoader vmware-netcfg ln -s /usr/lib/vmware/bin/vmware-netcfg /usr/bin/vmware-netcfg
Note that I haven’t tried these commands by myself. Please feel free to leave a comment if you have tried it.