VMware Player 3.0 and Network Configuration

29 Oct 2009
October 29, 2009

I updated VMware Player to the latest version (3.0) on my home machine last night[1]. Wanted to check out the latest version and get a first hand look at the new features.

I pointed it to my trusty Xubuntu “security” virtual machine and booted up. I ran into a snag pretty quickly though. Seemed that the client couldn’t get an IP address to get on the network.

I’ve seen and fixed this before. VMware Player seems to like to grab my Hamachi “personal VPN” network adapters instead of the local Ethernet one – it will never get an IP from the Hamachi network!

That’s when I hit the next snag: the new version of VMware Player doesn’t include the vmnetcfg network configuration that I’ve always used to fix this in the past. I poked around a bit but it wasn’t there and I didn’t see anything that looked like a replacement.

I ended up fixing this in a bit more of a low-tech fashion. I simply disabled the Hamachi adapter and then booted the VMware client. Client got an IP and I then re-enabled the Hamachi adapter.

Disabling a network adapter

Of course, after my low-tech solution I went looking for better options… Turns out I’m not the first one to notice that vmnetcfg went missing. I found discussion and the answer in a forum post:

The vmnetcfg.exe is included in the installer, but won’t be installed.
1. Run the installer with /e option. For example:
VMware-player-3.0.0-197124.exe /e .\extract
All contents will be extracted to “extract” folder.
2. Open “network.cab” and copy vmnetcfg.exe to your installation folder,
typically “C:\Program Files\VMware\VMware Player\”.

Well there you go. Even better.

[1] – Past mentions of VMware Player.

Tags: , , ,
36 replies
  1. Ramon says:

    Thanks for the post!
    Finding vmnetcfg.exe helped me a lot!
    Strange they don’t extract it anymore.

    Reply
  2. Jason says:

    This is very much appreciated, I can’t believe they keep hiding valuable tools like this.

    Reply
  3. Carlos says:

    Thank you! I was struggling with this for some time and now that I decided to solve it I found your post. Very Useful.

    Reply
  4. Nits says:

    Wow…this was awesome solution. I am trying to get the bridged networking work for Guest OS(WIN XP) and read so much on google… everyone pointed to keep checking automatic bridging as a problem but no one tell a word about how to get there. Without this I would have banged my head with wall…lol Thanks so much for the great and very well explained solution..i wonder why VMware freeks hide this at first place…huh

    Reply
  5. RM says:

    I think that going to the Himachi adapter properties and turning VMWare Bridge Protocol off would also fix the problem.

    Reply
  6. dsanger says:

    Thank you! this is a major problem with Player 3.0

    Reply
  7. wylis says:

    Thank you for posting this info!

    Reply
  8. kAtAlA says:

    Thank you!!!!!!!!!!!!!!!!!!!!!

    Reply
  9. bruce says:

    Thank you for your effort and insight. I thought I would point out that the newest player, released 5/25/2010, now installs the whole network.cab. I was running into a similar problem with the 3.0.1 version and found that by updating my player to 3.1 and using NAT, I got a physcial connection without any muss.

    I wanted to point out that I was not able to get bridged mode to work for the new player but the NAT, using the host’s network address, works great.

    Reply
  10. abubasim says:

    If you use vmnetcfg.exe to update NAT IP address then it may not configure the gateway address correctly. This can be fixed by editing C:\Documents and Settings\All Users\Application Data\VMware\vmnetnat.conf using your favorite text editor and then rebooting.

    Reply
  11. Dennison Uy says:

    Thank you for posting this!

    Why on earth did they not include this tool in the first place is beyond me.

    Reply
  12. Andres says:

    Thank you for the tip!

    Reply
  13. Corey says:

    OMG THANK YOU CHRIS!!!!!!!!!!!!! I’ve been looking for several days now!

    In VMware 2.x it was so easy… VM is really shooting themselves in the foot with this Player “non-sense”. We’re running a large cluster of ESX at work and i sold it using the free desktop versions.

    Don’t look now but M$ is coming up quick VM…. not is not the time to get greedy.

    Reply
  14. Julian says:

    Regarding Bruce’s comments, I’ve got the latest Player download installed on Windows 7 x64 and it definitely didn’t install vmnetcfg.exe. This post was a lifesaver, thanks.

    Now if only Sharepoint 2010 wasn’t such an astonishing resource hog I might be able to install a dev VM. It’s not looking good for me today though…

    Reply
  15. cocodonald says:

    thanks for this very useful information!!! It is so helpful for me !!!

    Reply
  16. Ryan says:

    @Julian – I feel you on SP 2010! Thanks for this post btw. I am astonished by the nonsense of VMware to not include this by default.

    Reply
  17. Richard Dunne says:

    Great Solution, thanks

    Reply
  18. breed says:

    Thanks – this was a great tip, helped me immensely.

    Reply
  19. Thawat says:

    Great man! Thanks for your post.

    Reply
  20. nodmonkey says:

    Thank you so much. Using this tool, I have finally been able to get NAT working in VMWare Player with Windows 7 host using this tool by following instructions here: http://florianlr.wordpress.com/2009/07/09/5/

    Reply
  21. ade says:

    thank you, thank you, thank you!!!

    Reply
  22. Frank says:

    Thanks soooooooooooooo much!!!!!!! This is exactly what I needed

    Reply
  23. debadatta says:

    it was really helpful… thanks lot!!

    Reply
  24. Wolfgang says:

    Thank you very much! This is much easier than manually editing the .conf files and changing registry entries. I used VMWare Server before and missed the network config program now. I need it because I MUST use specific networks for my clients (dependencies in the installed software).

    Reply
  25. Wolfgang says:

    Oh, by the way: I’m using VMWare Player 3.1.4 !!!! The program still is not installed automatically!

    Reply
  26. kevin says:

    And after all of this time it still isn’t fixed. Awesome info.

    Why are they being so stubborn. Fairly simply fix.

    Reply
  27. Lapi says:

    Thank you. Fixed my problem.

    Reply
  28. Frederik says:

    Been looking for this solution for hours, thx!

    Reply
  29. bazkar says:

    VMwarePlayer 4.0.1 again omits the vmnetcfg.exe :(
    Thanx again for the solution

    Reply
  30. Bill says:

    VMwarePlayer 4.0.2 again doesn’t extrace the vmnetcfg.exe. That does not make sense. They extract everything in the “network.cab” except vmnetcfg.exe.
    This post helps me. Thank you.

    Reply

Trackbacks & Pingbacks

  1. [...] get a DHCP IP…. It surely annoys me enough for me to turn to VirtualBox until I found the blog ( VMware Player 3.0 and Network Configuration ) which states the following: The vmnetcfg.exe is included in the installer, but won’t be [...]

  2. [...] Install the Virtual Network Editor coming with VMPlayer (but not installed automatically check this post). Edit the VMnet8 interface and change the subnet to your needs. Mine was 192.168.38.0 Ok and [...]

  3. [...] Startup I thought I’d hit most of the potential VMware Player challenges by now (most recently network configuration) but I’ve been wrestling with a new issue for a while now. It was only happening on one [...]

  4. [...] è possibile configurare il nat e il port forrwarding OutOfTheBox. Cercando per la rete ho trovato questo utilissimo post che spiega come risolvere il problema. In pratca l’installazione omette lo strumento di [...]

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>