VMware Cloud Community
prutter
Enthusiast
Enthusiast

VM getting incorrect IP address on Reboot

There are times when we reboot VM's that have STATIC IP's assigned to them and after reboot they have connection issues.  When we logon to teh console and do an IPCONFIG we find that the VM has a 169.xx.xx.xx address.  Once we reboot again it goes away.  Has anyone ever heard of or seen this??

Running ESXi5.1 on Dell 620's on an Equalogic SAN.  Any comments or suggestions are welcome.  Thanks

Perry

0 Kudos
5 Replies
abhilashhb
VMware Employee
VMware Employee

Could never figure out why this happens. You could check a couple of things though.

Do you have IPv6 enabled? If not in use, disable it.

Is the same IP used by any other server across the network?

I usually remove the NIC and re-add it. Configure with new static IP.

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

0 Kudos
JarryG
Expert
Expert

What kind of VM is it? Do you use persistent network-device names (including your networks-scripts)?

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! 😉
0 Kudos
BharatR
Hot Shot
Hot Shot

Hi,

VM is running which operating system? and which network adapter is assigned to the affected VM?.

Best regards, BharatR--VCP4-Certification #: 79230, If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
Paltelkalpesh
Enthusiast
Enthusiast

Which OS is using ?

Shutdown the VM

Remove the NIC completely

Boot the VM

Go to this key in the registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces)

Delete out the interface ID of the one that has the X.X.X.X address you are seeing or delete out all interface IDs under the \Interfaces key.

Shut the VM down again. 

From the VM properties, add the NIC back, connect to correct virtual switch, VLAN ID etc...

Boot VM.

0 Kudos
prutter
Enthusiast
Enthusiast

Running Win2K8 R2 server with VMXNTET3 NIC

0 Kudos