Comments on: Force vmware to configure a network interface

By: dinu

dinu — Wed, 26 Oct 2011 19:37:00 +0000

thanks… worked perfect for me!!!

By: gabriel

gabriel — Sat, 06 Mar 2010 02:22:30 +0000

when the vmnetX interface does not came up it’s because that IP is already being used.

By: Ray

Ray — Sun, 16 Nov 2008 15:59:03 +0000

This was a huge help.

I am not sure if the following line should read:
# ifconfig vmnet1 xxx.xxx.xxx.xxx up

instead of:
# ifconfig vmnet xxx.xxx.xxx.xxx up

When I used it on my vmnet2 (with the number) it worked.

By: Darrell

Darrell — Sun, 14 Sep 2008 15:29:42 +0000

This may not be your problem, but it’s worth noting that it is normal for the vmnet interfaces not to appear until 30 seconds or more after you start the vmware service. (That’s why it says “background” when initializing vmnet1 — the initialization is continuing in the background after the service starts.)

By: shao

shao — Fri, 06 Jun 2008 02:57:05 +0000

I use the command you give above to set up a v-net between 2 computers under linux, but when I use ping in one of them to another, it got something wrong. Why?
vmnet-netifup and ifconfig, there is no error.