Aaaaah, this is because of the internal module vShield installs on the ESX server. All VM traffic need to be redirected to this module to be filtered, and problems like this can happen if the VM is on a non-vShield ESX server. Glad to know you resolved it.
↧
