VMware Virtual Machine Getting 169 IP Address After adding Second NIC

Hi,

I'm having an issue when adding a second Virtual NIC to the new Virtual Machine I created.  After the Virtual Machine gets created, I set the static IP on the 1st NIC.  Everything registers with the Domain, DNS, etc...When checking in VMware Tools on the VM it shows the new static IP I set.

The second NIC that I have to add to this VM is going to be set as Static as well but on a different network.  The second NIC has to get to other resources on a different network.  The only configurations that I have to set in the 2nd NIC are static IP and Subnet.  

When adding the second NIC I make sure I select what Virtual Network it's going to be part of in the Edit Settings section on the VM.  Then I go into the VM and set the static on the second NIC.

After a little while, on the Summary section of the VM in vCenter, it shows a 169 address.  I already checked for Hidden NICs in the Device Manager but there aren't any.  I already went into the registry to see if I have any Interfaces that show 169 that have to be deleted but again there aren't any.

I don't understand when adding the second NIC and setting the static IP on it of another Network, it decides to turn to 169 Address showing in the Summary section of vCenter.

Any thoughts?

Thanks
LumiousAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Michael DyerSenior Systems Support AnalystCommented:
It sounds like it is trying to pull a DHCP address and failing.  Do you have DHCP configured and enabled?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you are using a static IP Address on the network interface, and it changes to a 169, it could be a IP Conflict ?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David Johnson, CD, MVPOwnerCommented:
remember only 1 adapter can have a gateway defined.
0
LumiousAuthor Commented:
Hi,

When you say IP Conflict, are we talking about an IP Conflict on NIC 1 or NIC 2?  The 169 Address shows up under VMware Tools right after I add the second NIC and put a static inside with an IP and Subnet.

Please let me know when you get a chance.

Thanks
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
IP Address Conflict, with the IP Address you have statically assigned to NIC2 in the VM.

if you login to the host, and check the IP Address, what is it ?

VMware Tools only reports what IP Addresses it detects/finds in the VM

ipconfig
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.