So this bug is still not fixed ?
The new installer of VMplayer 3 has this bug since the earliest Betas ...
You must run the setup again - this time with the extract option - then search the extracted files for a network.cab - extract this and you find the tool vmnetcfg.exe
VMware-player-3.0.0-203739.exe /e .\vmplayer
that command worked for version 3.0 - replace with current buildnumber
The Virtual Network configuration tool is also missing from VMWare Player 3.1 for Linux. Unfortunately it doesn't seem to be included in the installation package; at least I can't find it.
Anyway I've found a way to get vmnetcfg for Player on Linux (its not pretty).
Before installing Player, download Workstation 7 for the same platform. If you have already installed Player you need to uninstall it.
Make a suitable directory structure in ~/tmp:
mkdir -p ~/tmp/usr/bin
mkdir -p ~/tmp/usr/lib/vmware/bin
cp /usr/bin/vmware-netcfg ~/tmp/usr/bin
cp /usr/lib/vmware/bin/vmware-netcfg ~/tmp/usr/lib/vmware/bin
zip -r ./netcfg.zip *
Uninstall Workstation: sudo vmware-install -u vmware-workstation
Then "install" vmnetcfg:
sudo unzip ~/tmp/netcfg.zip
You can now run /usr/bin/vmware-netcfg to reconfigure yourvirtual network for Player.
If you want to set up a desktop or menu launcher then the vmware-netcfg icon IS installed with VMWare Player (clever hey? install the application icon but not the application). Its at /usr/lib/vmware/share/icons/hicolor/22x22/apps/vmware-netcfg.png
I'd like to be able to make the extracted binaries for vmware-netcfg available for download but I would assume that would be illegal, so you have to go through the ridiculous steps above.
Hope this helps someone.
I would suggest to uninstall VMplayer and instead install Workstation without licence.
That gives you the features you would get with a VMplayer without all the bugs.
The correct answer to your question is
run the setup again with the option /e .\temp
then look for a network.cab - it has the required files - just copy them to the install-directory of vmplayer.
Or just use the attached network.cab
You also find me in the support crew of PHD Virtual Backup
network.cab 2.9 MB
Well, I send the way I did it. Yes, it will look more than silly but it works from vmplayer 3.0 to my current 3.1.4 !!
Background: It seems that vmplayer does everything through a program called "appLoader" . The rest (most) are symbolic links to it. I persume that the program recognizes how it is called and acts accordingly.
You have to go to the real vmware directory (should be /usr/lib/vmware/bin ) and there create a symbolic link to appLoader with name vmware-netcfg.
As I said sounds silly but it works for me.
So : (everything done as root, i.e. su in normal Linux/Unix or sudo in Ubuntu flavours)
ln -s /usr/lib/vmware/bin/appLoader vmware-netcfg
ln -s /usr/lib/vmware/bin/vmware-netcfg /usr/bin/vmware-netcfg
That's all. Then, you call vmware-netcfg and voila !
Just to let you know that I've used the mgr01 method and worked great, although the second command I didn't really understand and it actually didn't work (just the second command) after I've created the las link to the /usr/bin directory everythng worked great and I was able to launch the network configurator.
Two thumbs up for your method mgr01
If you mean the link within the vmplayer bin directory:
that's there because vmplayer does most links so, just to follow their way, and
because probably some other vmware program may call it from there.
It also may depend upon your Linux distributiion: Ubuntu-flavours use other directories than openSuSE and
tarballs may use different than repository-based auto-installation.
The UI comes already along with the player
go to the vmware-directory and run in elevated cmd.exe-box
rundll32.exe vmnetui.dll VMNetUI_ShowStandalone