Solved

VMWare Virtual Machine Loss of Network on Reboot

Posted on 2016-08-16
5
99 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 121

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 121

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

The Ultimate Checklist to Optimize Your Website

Websites are getting bigger and complicated by the day. Video, images, custom fonts are all great for showcasing your product/service. But the price to pay in terms of reduced page load times and ultimately, decreased sales, can lead to some difficult decisions about what to cut.

Question has a verified solution.

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

An article on effective troubleshooting
Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

690 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