VMWare Virtual Machine Loss of Network on Reboot

I am running VMWare 5.5, my windows hosts will periodically on reboot fail to properly setup their network cards.  All the machines are assigned static IP addresses, however on reboot the machine will boot with a 169 IP address, like it it failed to receive DHCP.  Simply rebooting the machine or even just disabling the NIC and re-enabling corrects the issue.

I've seen it happen with all my MS operating systems Windows Server 2008 R2, Windows Server 2012 R2, Windows 7, etc...

Ideas?  This is getting rather annoying.

Thanks in advance!
RailroadAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
There is no MAC Address or IP Address conflict ?

Are you using the VMXNET3 interface and VMware Tools installed.
0
RailroadAuthor Commented:
There are no IP or MAC conflicts.  Using E1000.  Yes VMware tools are installed.

Guessing I should switch them all to VMXNET3?  What's the best way to do this?

What is the difference?  I always just used the default, which is E1000.

Thanks.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Remove and replace the network interface.

If you switch to DHCP does it get an IP Address ?

E1000 is a legacy interface which should just be used to install the OS, because Microsoft will not include the VMware driver in the OS.

VMXNET3 is a highly virtualized aware adaptor, which also runs at 10GBe, E1000 is an emulated adaptor, which also adds high overhead on the VM.

Best Practice is always to use the VMXNET3 after you've installed VMware Tools which always contains the drivers and software for it.
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
RailroadAuthor Commented:
Thank you for the help.  No real way to test until it reboots on its own for updates.
0
RailroadAuthor Commented:
So I finally figured this out.  It's a Windows OS issue, adding the below registry key to the system will fix the issue.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"IPAutoconfigurationEnabled"=dword:00000000

Open in new window

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.