Search the VMware Knowledge Base (KB)
View by Article ID

A virtual machine deployed from template or cloned fails to ping outside network with the error: Unable to contact IP driver (2016747)

  • 4 Ratings


A Windows 2008 or Windows 2012 virtual machine, either deployed from a template or a cloned virtual machine, experiences these symptoms:
  • The virtual machine cannot reach outside the network via ping
  • You see the error:

    Unable to contact IP driver. General Failure

  • nslookup fails with the same error


The issue is caused by a duplicate Security Identifier (SID). The guest customization option is not selected while deploying the virtual machine.


To resolve the issue, you need to run the sysprep tool to generate a new security identifier for the virtual machine.

To run the sysprep tool to generate a new SID.
  1. Open a console to the affected Windows virtual machine.
  2. Open a command prompt in elevated mode. Right-click a shortcut to the Windows Command Processor and select the Run as administrator option.
  3. Change the path to C:\Windows\System32\sysprep.
  4. Run the sysprep command.
  5. When the sysprep wizard appears, check the generalize check box, leave all other setting at the default values.
  6. Reboot the virtual machine to apply the changes.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 4 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 4 Ratings