Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I moved a VMWare client (using the VMWare vCenter Converter) from a VMWare Workstation 7 host to an ESX V3.5 host. Everything seems to have gone correctly but when I power on the VMWare image the network devices don't load. I have tried removing the network device and re-adding it but always get the same results.

If I perform an lshw -C network it shows the that the networking is disabled.

share|improve this question
up vote 1 down vote accepted

You can also modify the following file...


If you want to make the "new" network adapter eth0.

So say you have entries for eth0, eth1, and eth2. eth0 and eth1 were nics on the server before migration. eth2 is the current nic.

You would delete the lines for eth0 and eth1, and then change the entry for eth2 to eth0.

Restart the machine and it would then work as eth0.

share|improve this answer
To make things easier, you can just delete that file. It'll be recreated when the server reboots with the correct device mappings. – rodjek Dec 31 '09 at 1:14
That would be easier. I will have to remember that for next time. :-) – Scott Keck-Warren Dec 31 '09 at 13:41

It turns out that the network adapter was showing up as eth2 instead of eth0 (which in hindsight makes sense). I changed eth0 to eth2 in the /etc/interfaces file and it worked right away.

share|improve this answer

Have you installed the ESX version of VMWare tools? If you do an ls mod do you see the pcnet32 or vmxnet modules loaded?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.