SDSimonsen, Have you confirmed that the nic is in the approved hardware list for that version of ESX? Here is the link to go to to determine if it is: http://www.vmware.com/supp
Main Topics
Browse All TopicsI am having big problems with a virtual windows 2003 server running on VMware ESX 2.5.3. I tryed to update the nic to a vmxnet virtual device, but now I only get an unknown device VMware PCI Ethernet Adapter. It just does not appear as a networkdevice.
I have tryed do uninstall the VMware Tools, removed the device from the windowsmachine and changed the type agen in the MUI removed all virtual network adapters, and even tryed to create new ones, but all get registered as unknown device in the virtual machine
Has anyone a sugestion how to resolve this trouble?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
SDSimonsen, Have you confirmed that the nic is in the approved hardware list for that version of ESX? Here is the link to go to to determine if it is: http://www.vmware.com/supp
Did not se jennsteve3's remark.
It is not the esx server that has the problem, but one of my virtual machines running within it. It is at win2003 server, and all my other virtual machines are running with the same operatingsystem and drivers.
They all were running with the default vlance virtual device which emulates the amd driver, and I changed them them to the vmxnet to get more performance, and it worked for all the other machines.
Hi I solved my problem last night by this manner:
Made a copy of my VM, Exported the registery on the VM copy :-)
Uninstalled VM Tools
Removed the nic
Started the VM
Deleted all entries that i could find for VMware PCI Ethernet adapter
Closed the virtual machine
Added the nic and started the VM
Exported the entries regarding the VMware PCI Ethernet adapter from an other VM to a virtual floppy, and imported them to the registery on the VM copy
Rebooted the VM, installed the VM Tools, and reebooted
The nic showed up as it should, but would not appeare as a network connection. Not even when I ran the "netsh int ip reset logfile.txt", so i imported the WinsockXPFix.exe and running it fixed the machine.
Have not tryed the sysprep, so I do not know if would have helped, but if I have time I will try it on the original version of the VM. LindyMoff's comment on copying the drivers while the installing the tools got me thinking of mounting a virtual floppy, and in that way get registery entries and tools imported the fastest way.
This experience will change my Best Praktice to in future to have a virtual cd with all repair tools ready.
If I would have had the virtual cd ready I would have been able to fetch the registery from a backup onto the cd and then repaired the registery on the failed VM
Business Accounts
Answer for Membership
by: LindyMoffPosted on 2007-09-14 at 21:09:57ID: 19896429
Sounds like you may have previously had an "AMD PCNET" adapter before, and the configuration changes modified its identification as a "VMware PCI Ethernet adapter".
There's a chance that even if you installed vmware tools, you still need to manually add the NIC driver after this happens. Can you run the tools install again, but while the virtual CD-ROM is still loaded, copy the driver?