This past week as part some activity we powered off some Virtual Machines and after some time when powered on those VMs again, I was surprised when the network would not come up for two VMs. I tried to ping them but VMs were not reachable so I logged-in on one of the virtual machine via VM console to check the IP configuration etc and found Network Card was showing limited connectivity (yellow sign on NIC icon) however the IP information was correct, then tried to ping from inside the VM without success. I also the rebooted the VMs again but that didn’t fix the connectivity issue.
I did remember few months back we had faced a similar issue however at that time default gateway was not turned on and ipconfig was showing an APIPA address like 169.254.x.x. To fix that issue we had to reconnect the VM network card so tried the same here too and it worked.
To fix the issue what you need to do is, Select the affected VM and go to Edit VM settings => select the vNIC adaptor =>Deselect Connected => Now click OK to apply the setting
Now Navigate again to the Edit VM Settings => select the vNIC adaptor =>Select Connected => And click OK to apply the setting.
Once settings applied, VM came back to network again.
On another VM just to test if a cold reboot would work here, I powered off the VM and once it powered off, powered it on again and voila VM was accessible again.
Thus we can fix this issue either by a cold reboot or by reconnecting the virtual network card.
Update: Today I came across the same issue again, this time it was a MS Server 2012 R2 OS VM and a cold reboot didn't fix the issue, one more thing sometime in order to fix the issue, you may need to repeat the vNIC disconnect process.
Update2_25/02/2016: Sometime the above wouldn't work at all, then what you can do is: login to the affected server via VM console => Go to Network card properties and disable, re-enable the network card from inside the OS and hopefully server would come back to network again.
The other thing you can do is Change the IP assignment setting from Static to Dynamic, it would pick an IP from APIPA, then change it back to Static and it should work now.
Note: For further detail about the issue, you may refer to the related VMware KB#2012646.
That’s it... :)
I did remember few months back we had faced a similar issue however at that time default gateway was not turned on and ipconfig was showing an APIPA address like 169.254.x.x. To fix that issue we had to reconnect the VM network card so tried the same here too and it worked.
To fix the issue what you need to do is, Select the affected VM and go to Edit VM settings => select the vNIC adaptor =>Deselect Connected => Now click OK to apply the setting
Now Navigate again to the Edit VM Settings => select the vNIC adaptor =>Select Connected => And click OK to apply the setting.
On another VM just to test if a cold reboot would work here, I powered off the VM and once it powered off, powered it on again and voila VM was accessible again.
Thus we can fix this issue
Update: Today I came across the same issue again, this time it was a MS Server 2012 R2 OS VM and a cold reboot didn't fix the issue, one more thing sometime in order to fix the issue, you may need to repeat the vNIC disconnect process.
Update2_25/02/2016: Sometime the above wouldn't work at all, then what you can do is: login to the affected server via VM console => Go to Network card properties and disable, re-enable the network card from inside the OS and hopefully server would come back to network again.
The other thing you can do is Change the IP assignment setting from Static to Dynamic, it would pick an IP from APIPA, then change it back to Static and it should work now.
Note: For further detail about the issue, you may refer to the related VMware KB#2012646.
That’s it... :)
I got this issue after IP conflict and did the same thing.
ReplyDeleteMost of the time, Disable / Enable the NIC from inside OS fix the issue.
ReplyDeletebut that didn't work here...
Deletehttps://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2012646
ReplyDeleteThis kb article is already listed in this post...anyways thanks
DeleteI am also having the same problem. Did you ever find the cause and possibly a solution?
ReplyDeleteAFAIK all possible solutions are already listed here, except one related to reg edit...this issue is kind of we face once in months and not permanent...this is whats VMware thinks causing the issue, kb#2012646....This issue occurs because the IP address registry values are incorrectly overwritten by a newly added IP address, instead of the whole list of IP addresses.
DeleteI am having the same problem. Have you found out what's causing the problem? Or any possible solution?
ReplyDeletethis is whats VMware thinks causing the issue, kb#2012646....This issue occurs because the IP address registry values are incorrectly overwritten by a newly added IP address, instead of the whole list of IP addresses.
DeleteWhat is the permanent solution?
ReplyDeletewhat is the permanent solution, all the entries are correct
ReplyDeleteThis is not something one would see every now and then...you rarely come across this and in that case this is what worked for me and hopefully the same would be applicable in related cases....
ReplyDeleteSaw this today on 3 VMs
ReplyDeleteESXi 6.7
first two are older 2008 R2 servers (going away), each with static IP
last was Server 2019, brand new VM built from MS Server 2019 standard. VMXnet, vmware tools installed. No connection until disco/reconnect - and THEN it obtained IP automatically.
This is something we don't see frequently...So, good to know that you were able to fix it 👍
Delete