Problem:
- Windows 2008 R2 or Windows 2012 servers have no network access after a reboot
- Not all VMs affected, but multiple VMs and mulitiple hosts.
- Windows Network configuration shows the correct info
- Ipconfig shows a 169.254.x.x IP address
- Disabling and re-enabling the guest NIC fixes the issue. Also, a VM disconnect/connect fixes the issue.
Things I have tried:
- Switch vNIC from E1000 and E1000e to VMXNET3 (per VMware support). This appeared to work for a while, but the problem continues.
- Updated VMware tools (appeared to help at first)
- Updated hypervisor (appeared to help at first)
- Today I opened a new VMware support ticket
A similar question on serverFault proposed a solution of turing off power management in device manager. I will see if this helps, but I doubt this will help. I do not think the OS is trying to save power during the bootup process.
Best Answer
I cannot confirm yet, but I believe I found a solution. I say this because the symptoms are very very close to what I am seeing.
VMware KB: False duplicate IP address detected on Microsoft Windows Vista and later virtual machines on ESX/ESXi when using Cisco devices on the environment http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028373
Duplicate IP Address 0.0.0.0 Error Message Troubleshoot - Cisco http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/8021x/116529-problemsolution-product-00.html
Note: I am trying this combination of Cisco commands
ip device tracking probe delay 20 ip device tracking probe interval 45
one of those two command may have took down my network for a minute or two. :-/
You might want to do this during a maintenance window!!!