VMware Cloud Community
Super6VCA
Expert
Expert

ODD Network Config Issue DHCP and Static numbers

Good Afternoon all,

I have an issue where some servers, upon reboot, are getting a 169 IP address even though they are set to a static number.  It happens to the vcenter server just about every time.  Once i reboot the server then it's fine.  If you look at the pic attached you will see what i mean.  Both IP's show up under IPCONFIG.  I am going to see if changing from the VMNET3 nic to a different one helps this out at all. Has anyone heard of this before?  Any help or suggestions are welcome.  Thanks!

Sorry for the post.  Found this.  http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=201264...

Thank you, Perry
0 Kudos
4 Replies
rcporto
Leadership
Leadership

You're getting APIPA address because the IP address 10.0.70.50 is duplicated on your network... try find the another device with this IP address and remove from him.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
Super6VCA
Expert
Expert

I realize that it says that  on the pic but can't be the case.  Can't ping that number at all.  Not even when i disable the nic on that server plus that address is not in the scope range on the DHCP server.  That's why I am posting.  one thing I did notice that i am not certain about is the type of Reg keys that were in the registry.  Went through that KB article and this is what happened after.  (See pic)  No duplicate IP address but yet a 169 address.

IP Add2.JPG

Thank you, Perry
0 Kudos
rcporto
Leadership
Leadership

If you're not sure about registry keys, you can remove all virtual network interfaces from VM, delete the ghost network adapters inside the VM using devmgmt.msc, add a new virtual network adapter and set the IP again.

Remember that to see ghost adapters on devmgmt.msc, you will need do the following using the command prompt:

> set devmgr_show_nonpresent_devices=1

> start devmgmt.msc

Once on Device Manager, go to View -> Show Hidden Devices.

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
Super6VCA
Expert
Expert

Something very strange is going on and it only seems to be with the vmnet3 nic. When vmnet3 is installed sometimes it will not show the gateway, sometimes it will show up with the 169 address even though it's static.  It's a bit more stable when i use the E1000 nic.  I'm going to open a case with vmware to get this figured out.

Thank you, Perry
0 Kudos