Hello every one,
May be this help other.
I have a Windows Server 2008 (SP2) on ESXi 5.0 with VMXNET 3 (VMware tools installed), everything was working fine until tried to enable Routing and Remote Access, as soon I clicked OK, the network gone, even ping not work, I get in via the VM console, and the Network Adapter looks enable without any error, but there was not connection and the network can’t be disabled, a couple of times the Windows Server stop responding, after restart works fine for about a minute and then the network goes again. I’d review everything on the Windows server, but apparently there were not problems, so I checked the VM Settings and change the Ethernet Adapter from VMXNET 3 to E1000 wuala!! problem solved, now Routing and Remote Access can be enable and disable. It supposes that VMXNET 3 its better, but who wants this kind of surprises on their Domain Controller?
Experiencing same problem with Workstation 8 on Windows server 2008.
It appears that there is a network traffic loop occuring when the routing and remote access service is started. This builds up until the machine becomes unresponsive. On my machines this takes a couple of minutes and using a network monitor I can watch it happenning.
Disabling VMNet1 and VMNet8 host adapters and disabling the VMWare NAT and routing services appears to reduce the speed of build up but not stop it.
I will try your solution of changing to the E1000 adapter on the guest.
After lots of heart-ache and testing I found the following...
VMWare have so far refused to acknoledge this as a problem with their software even though packet prioritisation is a normal (albiet uncommon) function to perform on a server.
Hope this helps some people with the same problem.