I know that this is not a VMware blog, I however felt compelled to blog this.
A. Because if it can help someone then it has been worth it.
B. The issue is around Windows 2012.
Anyway – VMware issued a support KB article on this issue a few weeks ago, Though I have yet to read about this anywhere. In short, any data flowing through the VM network stack may get corrupted – including file copies, remote clients interactions with databases, any client-server or multi-tiered apps.
The issue may occur on any Windows Server 2012 VM with the default (E1000E) NIC adaptor running on ESXi 5.0 and 5.1
The easiest workaround is to change the NIC type to VMXNET3 or E1000 or disable TCP Segmentation Offload in the guest operating system.
Anyway, If your runningVMware with Windows 2012 VM’s please take caution and make sure that your not running with the default NIC and TCP SEgementation Offload.
Many thanks to GOSTEV from Veeam for bringing this issue to our attention.