win2012 "autoconfiguration ipv4" on NIC with static address

Hi, on windows 2012 server (VM, on ESXi 5.5) , with 2 NICs, we are getting some times an "autoconfiguration ipv4" address, even though the NIC has a static IP assigned to it. It's a VMXNet3 adaptor.

I cant find out why this happens?
LVL 1
sk391Asked:
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.

JohnBusiness Consultant (Owner)Commented:
I would try re-configuring VMXNet 3 again. Perhaps delete it and re-create it.

Is there a Network Editor on ESX ?  There is in VMware Workstation. Sometimes resetting the VMware Network helps.
0
sk391Author Commented:
It's happening on several VMs, and it goes away after a reboot. It seems like an OS related issue, not something on the virtual infrastructure layer. I see quite a few threads about this when googling, but no resolution unfortunately!
0
JohnBusiness Consultant (Owner)Commented:
I am not why several machines would all have the same issue. Try a TCP/IP reset and DNS Flush on a machine to see if this fixes anything.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

sk391Author Commented:
Nope didn't help. it's fixed after a reboot but I need to find the root cause for this.
0
JohnBusiness Consultant (Owner)Commented:
Did you try resetting (delete, re-create) VMXnet3 ?

I have not seen an issue where a bunch of machines would all fail the same way like this. I don't think QOS would cause an IP failure.
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
JohnBusiness Consultant (Owner)Commented:
Also look at the host machine NIC's . Maybe they need new drivers or possibly replacing.  Are the NIC's interfering with each other?
0
sk391Author Commented:
havent had any luck with this, but I will close the question and investigate further
0
JohnBusiness Consultant (Owner)Commented:
@sk391 - Thanks and I will watch your questions.
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
Windows Server 2012

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.