SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems (http://www.crwatersolutions.com) - Contact me direct: david_sterling@sterling-consulting.com or call 704-873-8846 x704.

Search This Blog

Sunday, December 15, 2013

Windows 2012 to Windows 2012 R2 - VMWare Workstation VMNet0 error

Discovered a problem while upgrading our VMWare Server from Windows 2012 to 2012 R2. On successfully updating, when starting up a Virtual Machine, got the error message that VMNet0 was missing. Once the VM booted, attempting to click 'Connect' on the network adapter in settings generated an error saying that the VMNet0 was not started.

Checking the VMWare settings (Edit > Virtual Network Editor...) I found that VMNet0 was indeed missing. Adding it proved a problem since it would not allow me to set it as Bridged (error that there were no non-bridged adapters available); in short, it was there, just not visible.

Did a bit of research and found some others had similar problems with Windows 8 to 8.1 - some recommended messing with the network adapter protocols (of which I do not recommend) but the best suggestion that worked overall was to simply re-load the installation media (or use the .exe if that's what you have) and run the VMWare Install Repair (you do not have to uninstall/reinstall). After the repair is complete, do a reboot of the server.

When the server has started up completely, open the VMWare console and check the network (Edit > Virtual Network Editor...) and VMNet0 (set as auto-bridged) should be displayed. Power up the VM and the network should appear as normal.

No comments: