Hi,
On ESXi5.5 we have installed 2 Windows 2012 R2 servers.
ESXi and Windows server all have latest updates.
We face the issue that the servers random lose network connection to each other all explained in VMware KB2058692 VMware KB: Possible data corruption after a Windows 2012 virtual machine network transfer
We allready tried to change network adapters of the virtual machine to vmxnet3 or e1000 instead of the default e1000e adapter, and disable TSO on the guest Windows 2012 R2 OS.
All with no succes.
Is there any other workarround for this problem?
Kind regards,
Gjalt Kootstra
Did you ever find a solution? We're having the exact same issue with Windows 2012 R2 dropping network connectivity randomly. A simple reboot fixes it, but only temporarily.
No, we've created a workarround to move all data to the terminal server instead of domain controller.
any news on this?
i have the same problem that my network connections stops working in windows 2012R2
my setup is on a vcloud director 5.5.2 with vsphere 5.5
i already deinstalled vmxnet3 drivers and running on E1000 NICS
i dont have esx5.5 U2 yet
with regards
Hi everyone,
did you check your vmkernel / virtual machine's logs after this occurrence appeared to see anything going on? Have you tried running wireshark for any suspicious traffic/packets causing this disconnect? Is your VMware tools up-to-date to cope with the vmxnet3 adapter change? Maybe increasing receive/transmit buffers would help as well? Maybe you can use some tricks from this post http://buildvirtual.net/tuning-esxi-host-networking-configuration/
hi
i enabled vmware tools logging to see its a driver or proces problem
i think its a windows problem because i see the same on microsoft community running hyper-v VM's
anyway i disabled ipv6 also cause that could be a problem it seems cause my edge gateway isnt configured for ipv6
i hope this works
disable the IPv6 and try it and update the nics drivers in ESX level also.,
As a default I disable all network protocols I do not need, therefore IPv6 is the first to go
Hi,
there are some known issues with Broadcom BCM5719 and BCM5720 NICs caused by NetQueue feature.
You can try to disable it on the affected NICs or try to update Broadcom driver, for more details see:
VMware KB: Broadcom 5719/5720 NICs using tg3 driver become unresponsive and stop traffic in vSphere
Hi there,
can you try assigning a vmxnet3 NIC to the VM and enabling RSS on the adapter as another troubleshooting step?
for now the vm's running ok
im gonna wait until after the weekend and see if its still loosing connections
but i think disabling ip v6 will do the trick
ok so friday the problem came back
here is what ive done that didnt help
changed from vmxnet3 to E1000 drivers
disabled ip v6
netsh int isa set state disabled
and i know its a driver problem cause in the event log came up event 16001 source AFD
A TDI filter (\Driver\vnetflt) was detected. This filter has not been certified by Microsoft and may cause system instability.
here is what ive done that so far is stable for me
removed any E1000 or vmxnet3 adapters
added only a E1000E
removed any hidden network drivers and tunneling adapters also
setup ip correct again and rebooted
i didnt disable ip v6 and also left isa state disabled
hope it stays stable now.
I have the same problem in one server with W2012 R2.
hello
just an update
my last solution is still stable for my configuration
hope this helps someone too in the future
I'm having the same issue with vmxnet3 vnics on W2k12R2 deployments. What is the co-relation with Netbackup Snapshots. It seems to happen post snapshot.
update for those with Windows 2012 R2 VMs with E1000/E1000e adapters >>>
Same problem here for me.
After around a week the Network on a Windows Server 2012 R2 is not reachable any more.
Rebooting the Server solves the problem for another week.
The VM is on a ESXi 5.5 update2 and is an vmx-10 vm with VMXNET3.
The ESX Server uses Broadcom 5720 with actual drivers.
did you see the post from vNEX? You probably need to update your 5720 drivers..
VMware KB: Broadcom 5719/5720 NICs using tg3 driver become unresponsive and stop traffic in vSphere
fix the adaptor to vmxnet3 & update vmware tool.Observe it for few hours !
As I described before I am already using actual drivers.