vmxnet3 is recommended as the preferred NIC by VMware and also by VMware's Health Analyzer. I always try to use vmxnet3. However, I have come across a very strange issue I really can not explain. Building out my vSphere infrastructure I'm at the point of installing the View Connection Server, Windows 2008 R2 OS. Added the VM to my AD domain, added my CIFS shares fine, surf the internet fine.
Problem: When adding vCenter to the Connection server it fails with a "Not Found" error? I struggled for hours trying to figure out what was going on; network issue, DNS, nslookups, pings? Everything network related worked except adding vCenter to the connection server. As a last straw I shut down the connection server, removed the vmxnet3 NIC, added the e1000 NIC, powered on and re-assigned the correct IP address. I can now add vCenter to the connection server? Why? Being curious, I shutdown the connection server, removed the e1000 NIC and added the vmxnet3 NIC. After removing vCenter from the connection server I can NOT add it back using the vmxnet3 NIC. Going back to the e1000 driver again all is good. Very ODD.
Thinking about removing the vmxnet3 NIC from my 2008R2 template and replacing it with the e1000 NIC.
Thanks
Tom