Home > Virtualization > How to Use the Missing Virtual Network Editor in VMware Player

How to Use the Missing Virtual Network Editor in VMware Player

March 13th, 2013 Leave a comment Go to comments

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, 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).

Time to learn how to "Google" and manage your VMware and clouds in a fast and secure


I found the subnet for NAT network is not consistent. One of my VMware Player installation has on VMnet8; the other 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.

Categories: Virtualization Tags: ,
  1. March 13th, 2013 at 00:33 | #1

    How to Use the Missing Virtual Network Editor in VMware Player (DoubleCloud) http://t.co/qxghAZlXqZ

  2. March 13th, 2013 at 12:25 | #2

    You can even make that into a start menu item if you save your command in a simple batch file (remember those?) Then create a windows shortcut to the batch file and select “run as administrator” on the shortcut tab, under advanced button. Move that shortcut into your menu and you’re done. Cheers!

  3. March 13th, 2013 at 12:45 | #3

    Thanks for the tip Wil, it surely make it easier. :-)

  4. March 13th, 2013 at 15:31 | #4

    How to Use the Missing Virtual Network Editor in VMware Player – http://t.co/bSzut5Os4B

  5. March 14th, 2013 at 07:41 | #5

    How to Use the Missing Virtual Network Editor in VMware Player – http://t.co/tOfY8t2jSz http://t.co/tOfY8t2jSz

  6. March 19th, 2013 at 07:30 | #6

    Is there any difference between VMnet8 and others such as VMnet1,VMnet2?

  7. March 22nd, 2013 at 10:46 | #7

    I don’t think there is any material difference but rather a convention. I think you can change the VMnet1 to NAT with the editor.

  8. June 11th, 2013 at 10:12 | #8

    BIG THANKS,,,,

  9. Phil Gardner
    June 29th, 2013 at 08:51 | #9

    When I try “rundll32.exe vmnetui.dll VMNetUI_ShowStandalone” with VMware Player 5.0.2, in an elevated command prompt in Windows 7 (64-bit), I get the error message “There was a problem starting vmnetui.dll The operating system cannot run %1”. Has anyone else encountered this? Any thoughts on how to solve it?

  10. July 1st, 2013 at 18:54 | #10

    I tried the command again and it worked fine on my computer. The command should be run in the VMware Player folder, i.e. C:\Program Files (x86)\VMware\VMware Player\, or include the path in the PATH environment variable.
    Good luck!

  11. Rafael Koike
    September 5th, 2013 at 13:22 | #11

    The last update to VMware Player 6 the .dll doesn´t exist anymore :-(
    Any ideas how to configure the vmnet now?

  12. September 6th, 2013 at 22:09 | #12

    Thanks for the update. Sorry to hear that it’s no longer there. I haven’t tried VMware Player 6 yet…


  13. Sandeep
    October 14th, 2013 at 16:28 | #13
  14. Thierry
    February 3rd, 2014 at 13:40 | #14

    I confirme for the linux settings
    I just needed to add the last link to get it.
    Many thanks.

  15. February 3rd, 2014 at 23:43 | #15

    Thanks Thierry! Whoever wants to try it will have higher confidence in the settings. :)

  16. Dan
    March 22nd, 2017 at 11:23 | #16


    Also worked for me on Gentoo Linux, but I had to amend the symlinks to take into account Gentoo’s install location for VMWare: /opt/vmware/lib/vmware/bin/appLoader

  17. April 27th, 2017 at 14:24 | #17

    This was a huge help. It took me a minute to realize that you have to do this on the host machine, and that your command prompt needs to first change directory to where the VMPlayer is installed so that the vmnetui.dll file is local. But once I figured that out, I was off to the races.


  18. Prof
    May 8th, 2017 at 13:28 | #18

    I didn’t have to create these symbolic links. They already existed in my installation of the free version of VM Workstation.

  1. March 13th, 2013 at 09:19 | #1
  2. April 24th, 2013 at 13:08 | #2