VMware Communities
midwest12345
Contributor
Contributor
‎08-17-2010 02:27 PM

Failed to connect virtual device Ethernet0. - New MacBook Pro Problems

Hello all,

I moved two VMs over to a new MacBook Pro that was brought online using Time Machine from my old MacBook Pro. Both of the VMs run, but one of them has lost internet connectivity. The Bridged option won't work at all while the LAN and Host only connect with limited connectivity and ultimately, neither work.

The error message is:

The network bridge on device /dev/ vmnet0 is not running

The virtual machine will not be able to communicate with the host or with other machines on your network.

Failed to connect virtual device Ethernet0.

Thoughts?

0 Kudos
8 Replies
midwest12345
Contributor
Contributor
‎08-17-2010 03:12 PM

I forgot to mention that both VMs are running Windows XP.

0 Kudos
midwest12345
Contributor
Contributor
‎08-17-2010 10:27 PM

Also, should I just switch to Boot Camp? VMware doesn't provide that good of support and if the community is also burnt out... not a good sign. There always seems to be something happening with the VM and it may not be worth the shared memory.

0 Kudos
intraxi
Contributor
Contributor
‎08-18-2010 03:24 AM

try:

sudo /sbin/ifconfig /dev/vmnet0 up

to make sure you have the vmware network if running...

midwest12345
Contributor
Contributor
‎08-18-2010 07:23 AM

Would that be in terminal on the Mac or the command prompt in the VM?

When I try in the command prompt, I get 'sudo' is not recognized as an internal or external command, operable program or batch file.

0 Kudos
midwest12345
Contributor
Contributor
‎08-18-2010 07:32 AM

In terminal, it asks for my password to do the sudo command. What would this command do?

0 Kudos
midwest12345
Contributor
Contributor
‎08-18-2010 08:14 AM

I reinstalled VMware this morning and the VM is now working just fine. Should have done this right away but I was frustrated. Thanks for the reply.

0 Kudos
intraxi
Contributor
Contributor
‎08-18-2010 08:30 AM

Ok sorry didn't see your new replies before.

The ifconfig command is to execute in osx terminal and makes sure the vmnet interface is running.

Glad you got it solved.

Cheers!

0 Kudos
topshot
Contributor
Contributor
‎11-28-2014 08:10 AM

Hello,

l just had a similar error on my vcenter server with version 5.5 update 2. l simply logon to the host machine where the vcenter is located. Then right click the vcenter server, clicked "edit settings", then clicked "network adapter". On the Network label, selected the vcenter server network vlan and clicked ok to apply changes.

Hope this could solve yours.

All the best.

0 Kudos