Solved

VMWare Virtual Machine Loss of Network on Reboot

Posted on 2016-08-16
5
86 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

Create the perfect environment for any meeting

You might have a modern environment with all sorts of high-tech equipment, but what makes it worthwhile is how you seamlessly bring together the presentation with audio, video and lighting. The ATEN Control System provides integrated control and system automation.

Question has a verified solution.

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

Suggested Solutions

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…

820 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