Solved

VMWare Virtual Machine Loss of Network on Reboot

Posted on 2016-08-16
5
81 Views
Last Modified: 2017-02-14
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!
0
Comment
Question by:Railroad
  • 3
  • 2
5 Comments
 
LVL 119

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 41757984
There is no MAC Address or IP Address conflict ?

Are you using the VMXNET3 interface and VMware Tools installed.
0
 

Author Comment

by:Railroad
ID: 41758007
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
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 41758018
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
 

Author Comment

by:Railroad
ID: 41758344
Thank you for the help.  No real way to test until it reboots on its own for updates.
0
 

Author Comment

by:Railroad
ID: 42008282
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

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

HOW TO: Install and Configure VMware vSphere Hypervisor 6.5 (ESXi 6.5), Step by Step Tutorial with screenshots. From Download, Checking Media, to Completed Installation.
In this article, I show you step by step with screenshots to assist you - HOW TO: Deploy and Install the VMware vCenter Server Appliance 6.5 (VCSA 6.5), with some helpful tips along the way.
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…
Hi friends,  in this video  I'll show you how new windows 10 user can learn the using of windows 10. Thank you.

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question