Categories

CUC (6) CUCM (27) Jabber (6) Python (2) Routing (3) Solarwinds Orion NPM (4) switching (1) Video (6) voice (3)

Saturday, 18 August 2012

VMWare Player 4.0.4 Bridged network Editor, vmnetcfg.exe

Not necessarily a Cisco post, but I came across a connectivity issue when building Cisco Unified Presence server vritual machine. I was building the virtual machine using a bridged network and for the life of me was unable to ping it from anywhere within my network. As always the solution was simple, but the research extensive.

The problem was that my host machine has multiple network interfaces as most machines do; loopback, wireless, and ethernet, if not more). Under the hood, vmware player uses vmnet0 as the virtual interface that bind to an interface on your host machine. Contrary to vmnet1 (used for host-only), and vmnet8 (used for NAT), vmnet0 is not displayed when going into your host's control panel. The problem with connectivity not working in bridged mode is that the vmnet0 interface was binding to the wrong host interface.

To change this (as it is set to automatic per default), you will need to obtain a file called "vmnetcfg.exe". For some reason, this file is NOT installed when installing vmplayer.

Obtain it as follows:

extract the installer file (for 4.0.4 ; VMware-player-4.0.4-744019.exe), from a command prompt;

 C:\Temp\vmware>VMware-player-4.0.4-744019.exe /e extract

this has just extracted the installer file in a directory called "extract".

Browse to the extract directory and search for an archive called "network". The vmnetcfg.exe file is in it, so just extract it out of that archive, like you normally would.  Stick the vmnetcfg.exe file into

C:\Program Files (x86)\VMware\VMware Player

 Now it can be run and edited as the screen shot below shows, manually bridge it to the network interface you want, changing it is instantaneous. Good luck


No comments:

Post a Comment