As is references in the Vmware kb article 2012646, virtual machines are obtaining an IP address of 169.254.x.x even though their network properties are set to a static address. If I disconnect and reconnect the nic in the vmware console, it will set the proper IP address but these servers are rebooted often and this does not appear to fix whatever the root cause of this issue is.
This is running in a vmware 5.0 environment. VMware tools are up to date.
This seemed to happen a couple weeks ago for no apparent reason. Does anyone have any other suggestions other than the KB article referenced above?
I have checked for hidden devices and see none in device manager. I have used the command prompt to show non-present devices prior to starting device manager.
Have you checked the Event Log for any IP conflict messages ? There are more than one server getting this problem ? Have you tried remove the virtual network adapter (including the ghost adapter on Device Manager), add a new virtual network adapter and set the static IP address again ?
I do get this issue on more than one machine. The NIC type is vmxnet3. I have not tried to remove the adapter but I can do that and then check again for the ghost adapter. As for upgrading the VM hardware, I'll have to check with the client to see if they have access to do that.
Thanks for the ideas. I'll try installing a new NIC and see what that does.
Can you check whether there is no IP conflict happening?
As you are assigning a static IP and still not getting it:The only reason I can think of is network conflict.
Make sure that the static ip is not in use anywhere else.
Or try assigning a new static IP.
Hope this helps!!