Because Snowball Was Taken

After a recent shut-down of all our systems which include physical and virtual machines, the vm’s running under VMWare Player would not connect to the network. Our vm’s use the bridged network method since they provide services, and this method stopped working.

I googled “diagnose vmware player networking” and found several good articles

The VMWare articles were informative, but misleading. My guest OS is Ubuntu, but I did not have the /usr/bin/vmnet-bridge process, and I did not ever find a VMnet0 adapter to correct (under Windows 7 and Server 2008). I have a VMnet1 and a VMnet8, but no VMnet0. Reinstalling the VMWare Player did not change this. I installed a fresh Ubuntu VM and configured it using bridged networking and verified that the network was working and still I did not find the vmnet-bridge process or the VMnet0 adapter.

The best solution path seemed to be using the Virtual Network Editor. Since it’s no longer installed by default, you must manually extract it from the install exe.

Create a folder named “extract” and run the installer with the \e option.

D:\Users\mbelor>mkdir extract
 
D:\Users\mbelor>VMware-player-5.0.0-812388.exe /e extract
 
D:\Users\mbelor>cd extract
 
D:\Users\mbelor\extract>

In the extract folder, open the core.cab file, or network.cab file for versions 3 and 4,
and copy vmnetcfg.exe to your VMWare Player folder. (C:\Program Files (x86)\VMware\VMware Player). Use 7-zip or WinRAR if you have trouble opening the *.cab file. For version 5, the core.cab file may not contain the vmnetcfg.exe file. In that case, will have to download Workstation 9 and repeat these steps with that installer.

D:\Users\mbelor>mkdir extract
 
D:\Users\mbelor>VMware-workstation-full-9.0.0-812388.exe /e extract
 
D:\Users\mbelor>"c:\Program Files\7-Zip\7z.exe" x extract\core.cab vmnetcfg.exe
 
7-Zip [64] 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18
 
Processing archive: extract\core.cab
 
Skipping    vm_generic.ico
Skipping    vmnetAdapter.sys_64
Extracting  vmnetcfg.exe
 
Everything is Ok
 
Files: 3
Size:       5013302
Compressed: 189838755
 
D:\Users\mbelor>

With bridging, the problem that can occur is the VMWare Player will attach to the wrong network adapter for the bridged network. The Virtual Network Editor allows you to specify what network adapter to use.

When I ran the network editor, all the settings looked correct. I had only one network adapter available for bridging so there did not seem to be a possibility for confusion. Just to have something to try, I changed it from Automatic to my phyiscal ethernet adapter.

I also tried rebooting the virtual machine, changing the network from bridged to NAT, re-installing the VM Tools. None of these appeared to help.

I tested the network connection by opening a terminal in the guest OS and pinging the gateway. Since the network connection is bridged, I have specified the guest’s IP address, mask, gateway and DNS. After changing the bridge from Auto to my network adapter, the ping worked.

Changing the bridge back to Automatic did not cause the networking to stop working. So, I do not know what caused the problem. But it appears that using the Virtual Network Editor gives you a tool to smack the network connection that reinstalling VMWare Player or VMTools doesn’t provide.

In a related post, Ian McShane says that “auto detect” fails and the solution is to choose a network adapter.

Version 4 Caveat

For one release of version 4 of the VMWare Player, the extraction method described above did not work. It is working as of 4.0.2. If it does not work, try this approach.

  • Open your temp folder and remove all the files so you have a clean folder. Try Start / Run / %temp% to quickly get a shortcut to your temp folder.
  • Re-run the VMWare Player, version 4 installer. It unpacks to a folder in you temp folder. Once it’s done unpacking, the installer waits for you to proceed.
  • Look in your temp folder for a new folder named something like vmware_1321116371.
  • Now, look in that vmware folder for the network.cab. Once found, you can proceed as described above.

In one release prior to 4.0.2 of version 4 of the player, there already was a file in the VMWare Player folder called vmnetcfg.exe. However, it would not run (neither as user nor as administrator). The fix was to extract the Virtual Network Editor from the network.cab file as described above.

Version 5

In version 5, the vmnetcfg.exe is in the VMWare Player folder, but running it does nothing. I get an “This program has stopped” error. According to this thread, you must download Workstation 9 and grab vmnetcfg.exe from the core.cab file.

VirtualBox and VMWare Player 5

I had just installed VirtualBox and now my VM running in VMWare Player 5 was not connecting via the bridged network connection. After poking around a bit, I clicked Configure Adapters under the network settings and found this wonderful screen that was so much effort to display previously.

Kudos to VMWare for this improvement!


I unchecked the VirtualBox and Microsoft miniport entries and the network began working.

See Also

Comments

No Avatar
Visitor (not verified) on Fri, 26 Aug 2011 - 2:08am

Thanks Mate,

This issue has been happening off and on with a couple of my computers here. I had read several articles that did not seem to lead to a solution. But I have managed to struggle through, with either a fluke fix or a work around.

This afternoon it happend to a VM which was intergral to a mission critical job that has to go out tonight. Stopping 5 people from working.

Your solution fixed it straight away, now i can go home and let the others enjoy (cough suffer cough) their Friday evening of work.

Cheers again!

No Avatar
Visitor (not verified) on Thu, 6 Oct 2011 - 4:25pm

That’s ridiculous. I feel like such an idiot, now. Spent the last 2 hours beating my head against this issue, that suddenly popped up. Thanks a bunch!

No Avatar
Visitor (not verified) on Thu, 19 Jul 2012 - 8:21pm

Great help!
Nothing was working until I came here.

IMPORTANT NOTE!
For me the above fix would not play.
I kept getting a message something like
“all available adapters are already bridged”.
Clicking “Restore Defaults” uninstalled all the vmWare adapters and reinstalled three (including the previously missing vmNet0.
After that, everything worked perfectly with bridging left set to automatic.

I had also installed virtualbox, so maybe that was the issue.

Clive

No Avatar
Visitor (not verified) on Fri, 5 Oct 2012 - 3:29pm

This is not working for Me what did i do wrong I will cry

No Avatar
Visitor (not verified) on Fri, 5 Oct 2012 - 3:39pm

how can i do that???????

Create a folder named “extract” and run the installer with the \e option.

VMware-player-3.0.0-197124.exe /e extract

No Avatar
Visitor (not verified) on Sat, 29 Dec 2012 - 2:10pm

thank you

when i reinstall vmware workstation i have always the same problem with dhcp or static address :

when the host go to suspension or hibernate guest network go down e the problem is the automatic setup in the network editor for the vmnet0 . But whenever i don’t remember the problem …

thank you again

No Avatar
Visitor (not verified) on Fri, 25 Jan 2013 - 5:32am


!!!Permanent solution!!!

The only thing you have to do is:
For each network adapter which should NOT be used by VMware:

  • Goto Properties
  • Remove the check next to ‘VMware Bridge Protocol’ (or remove the service completely

    For each network adapter which should/can be used by VMware:

  • Goto Properties
  • Check the entry ‘VMware Bridge Protocol’
  • If this entry is not available, use the button ‘Install …’ and select the service.
  • No Avatar
    anonymous (not verified) on Wed, 17 Jul 2013 - 5:12am

    this is the best and simplest solution, it worked for me .

    No Avatar
    MDLufie (not verified) on Tue, 18 Mar 2014 - 5:26am

    In the end!!!, I check out the reason, this problem happened while DNS have some problem(like my dns Pacific SuperNet 202.14.67.4 202.14.67.14 /NetFront 202.81.252.1 202.81.252.2 has the problem)
    , just remove all the dns settings and test VMWare, good dns will be ok.

    No Avatar
    Visitor (not verified) on Mon, 21 Nov 2011 - 1:04pm

    Many thanks: worked like a charm.
    Used extraction method, which is still valid with Player 4.0.1-528992.

    No Avatar
    Visitor (not verified) on Wed, 25 Jan 2012 - 4:17pm

    That’s a great solution!! We owe you a steak dinner and a large beer!

    No Avatar
    Visitor (not verified) on Wed, 15 Feb 2012 - 9:55am

    Fantastic help page. Helped me find out what happened to my computer. Turns out installing Oracle Virtual box on the same computer as VMware Player breaks the Bridge Network capability. Thanks

    No Avatar
    Visitor (not verified) on Wed, 15 Feb 2012 - 9:55am

    Fantastic help page. Helped me find out what happened to my computer. Turns out installing Oracle Virtual box on the same computer as VMware Player breaks the Bridge Network capability. Thanks

    No Avatar
    Visitor (not verified) on Wed, 29 Feb 2012 - 4:29am

    Must have been VirtualBox indeed. These two don’t play well together. The vmnetcfg trick in the above article was a lifesaver!

    Wim

    No Avatar
    Visitor (not verified) on Fri, 2 Mar 2012 - 5:27am

    This worked like a charm for me, thanks a lot!

    My problem was that bridged connection was not working on wireless. (It was working alright wired. But wired was not a good option because in that case Kaspersky firewall blocked the traffic between guest and host! Considered this one easier to tackle than Kaspersky ;) I have both Windows XP and Oracle Enterprise Linux 5.7 guests, so the problem wasn’t related to the VM settings or anything like that.

    Like many other commentators I’ve also got Virtualbox installed, maybe there’s a conflict between the two software.

    When running the vmnetcnf.exe my network adapter selection for Bridged was “Broadcom 4313 802.11b/g/n #2 - Virtualbox Bridged Networking Driver” - sounds scary, and another hint that something gets mixed up between VMWare and Virtualbox. “Normal” network adapters would not show up, just the ones from Virtualbox, and Bluetooth, so had to select among them the best looking option.

    Thanks a lot Michel, and thanks also for updating the entry, I can see that you already added information about VMW Player 4.0.2. I’d never-ever have figured this out without your blog entry!

    Cheers,
     Ilmari

    No Avatar
    Visitor (not verified) on Wed, 25 Apr 2012 - 10:53am

    Thanks for the post, worked perfectly even with 4.0.0 build-471780.

    No Avatar
    Visitor (not verified) on Tue, 15 May 2012 - 6:16pm

    I just found this page after days of Googling. Your fix worked after a restart of the VM. Thank you!

    No Avatar
    Visitor (not verified) on Tue, 29 May 2012 - 12:38am

    thanks a lot, man. You saved the day =)

    No Avatar
    Visitor (not verified) on Sun, 3 Jun 2012 - 5:59am

    Indeed you are a star !

    This will save so many hours around the globe for more than one hundred of my colleagues !
    I can’t imagine the cumulated amount of money saved !

    Please allow me to propose this little automatic batch script (with some tricks) when need to do this on multiple machines or just send the full operation to a friend :

    @echo off
    echo:&echo Extracting Virtual Network Editor from VMware-Player (takes a few seconds)...
    mkdir extract
    VMware-player-4.0.3-703057.exe /e extract
    cd extract
    "C:\Program Files\7-Zip\7z.exe" x network.cab vmnetcfg.exe
    echo:&echo Moving Virtual Network Editor...
    move vmnetcfg.exe "C:\Program Files (x86)\VMware\VMware Player"
    echo:&echo Generating Shortcut for Virtual Network Editor...
    echo Set WSHShell = WScript.CreateObject("WScript.Shell") > MyShortcut.vbs
    echo DesktopPath = WSHShell.SpecialFolders("Desktop") >> MyShortcut.vbs
    echo Set MyShortcut = WSHShell.CreateShortcut(DesktopPath ^& "\vmnetcfg.lnk") >> MyShortcut.vbs
    echo MyShortcut.TargetPath = WSHShell.ExpandEnvironmentStrings("C:\Program Files (x86)\VMware\VMware Player\vmnetcfg.exe") >> MyShortcut.vbs
    echo MyShortcut.Save >> MyShortcut.vbs
    cscript.exe /nologo MyShortcut.vbs
    cd ..
    rd /s/q extract
    echo:&echo Launching Virtual Network Editor...
    start c:\users\%username%\desktop\vmnetcfg.lnk
    echo:&echo Exiting...
    ping -n 5 localhost > nul

    Mapa

    No Avatar
    Visitor (not verified) on Sun, 1 Jul 2012 - 8:09pm

    Thank you, from Argentina!!!!

    No Avatar
    Visitor (not verified) on Wed, 13 Jun 2012 - 8:22am

    Many thanks. The article is spot on and very insightful. I tried almost everything for the last 2-3 days but was going no where. Wouldn’t be a big deal for me if I had not invested considerable time in building the VM. Don’t know why vmware guys have not figured this out yet. Also, worth mentioning… google rulzzz…as ever. this page was 3rd listing. keywords: vmware bridged not working for ubuntu.

    R

    No Avatar
    Visitor (not verified) on Sat, 16 Jun 2012 - 8:12pm

    Fantastic info! Only site with useful information on the topic. I tried everything just like you and nothing worked. Running that config and manually setting the NIC to use for internet worked perfectly after a VM reboot. Thanks for the info!

    No Avatar
    Visitor (not verified) on Mon, 16 Jul 2012 - 5:39am

    Great info.
    thanks a lot

    Kydu

    No Avatar
    Visitor (not verified) on Sat, 18 Aug 2012 - 5:04pm

    Worked for me too. Thanks so very much for taking the time to post this, I don’t know how I would have figured it out otherwise.

    No Avatar
    Visitor (not verified) on Mon, 20 Aug 2012 - 4:50pm

    You are awesome !! I was breaking my head for several days to get this working and now its resolved thanks to you.

    • Kumar.

    No Avatar
    Visitor (not verified) on Wed, 21 Nov 2012 - 7:27pm

    Thanks mate. I downloaded and installed the WM Workstation and It automatically installed the Virtual Network Editor, it showed the bridged VMnet0 is wrongly bridged to my Virtual-box Adapter. so i change it back to my REAL network adapter, and everything works fine! Thanks you VERY MUCH for the pointers. Will bookmark this page for future reference.

    No Avatar
    Dean (not verified) on Tue, 13 Aug 2013 - 3:05pm

    vmnetcfg.exe doesn't appear in VMware Player 5.0. To launch the network config dialog do the following:
    1. Extract the installer: VMware-player-5.0.2-1031769.exe /e extract
    2. Extract the msi inside the installer: cd extract&msiexec /a vmwareplayer_x86.msi /qb TARGETDIR=c:\absolutepath\to\outputdir
    3. Change dir to the output directory: c:\absolutepath\to\outputdir
    4. Run the net ui dll: rundll32.exe vmnetui.dll VMNetUI_ShowStandalone

    Note: You'll need to run the dll as Admin to make any real changes.

    No Avatar
    manfer (not verified) on Mon, 3 Feb 2014 - 7:32am

    Just in case someone read this comment I suggest not doing that. Read the last part of the article that explains that VMware Player 5 and above has and integrated way to edit the bridged network.