VM cannot contact it's domain controller after cold migration across clusters
Article ID: 443522
Updated On:
Products
Issue/Introduction
After a cold-migration (vMotion of powered off VMs) to a new vSphere cluster, the Windows VMs that were previously successfully connected to it's domain, can no longer connect to their domain controller.
Additionally, the firewall profile inside the Windows VM shows "Default" instead of "Domain".
Running "gpupdate" inside the VM yields no results and "gpupdate" remains running until you abort it using "Ctrl-C".
Environment
VMware ESXi 8.x
VMware NSX 4.2.x
Cause
This is a result of inconsistent MTU configuration in the top of rack switch in the new vSphere cluster.
Resolution
Ensure that the MTU configured globally in the top of rack switch is also applied specifically to each VLAN that's defined in the switch. Some switches use a default MTU of 1500 on VLANs despite a global MTU defined that's much higher.
Additional Information
Feedback
