Windows 2008 R2 on VMWare: “Unable to contact IP driver. General failure”

I have cloned (Deployed) new image from a template in VMWare of Windows Server 2008 R2 server. And joined to a domain (and domain controller is another VM deployed from same template). Then this frigging error message creped up in Command Prompt whenever I try any network commands (ping, ipconfig, etc.,): “Unable to contact IP driver. General failure”

After spent few minutes on Bing, I found the solution myself. It’s frigging duplicate SID. Usually duplicate SID is not an issue (according to Microsoft). But in my case, the domain controller and standalone server has same SID (deployed from same VM image template).  My solution is to run SysPrep to generate a new SID and it’s resolved the issue for me.

  1. Open Command Prompt in elevated mode (right click and select “Run as Administrator”)
  2. Change your path to C:\Windows\System32\SysPrep
  3. Type SysPrep and select the defaults.
  4. Reboot the VM and re-join to the domain.

There. If that resolved your issue, leave me a comment. Smile

25 thoughts on “Windows 2008 R2 on VMWare: “Unable to contact IP driver. General failure”

  1. Thanks! I always used newsid.exe from sysinternals. It’s still out there which is what I used to fix this problem instead of sysprep. They took it off of sys internals saying that duplicate SIDs were no longer a problem….. I guess that was then. 😀

    1. Crap! I just tried it on a win2k8 R2 Machine and now I’m getting BSOD. Looks like newsid is NOT a viable option if you want to play it safe.

  2. I had the exact same problem with the EXACT same environment and I ran a sysprep, rebooted and then rejoined the domain and everything is good now. Thanks!!!!1

  3. Man this was a lifesaver. Same setup as you described and same errors. Couldn’t do anything on the domain either. I have cloned these before without an issue but this time it was fail. You do need to click the generalize button though. It didn’t work without that.

    Thanks a ton!

    1. Agreed, this was a real lifesaver. As you mentioned you do have to “tick” the “generalization” box for the SId to fully reset.

  4. sometimes the network driver might have been corrupt and win2k8 would have installed system drivers instead of MANUFACTURER assigned driver. Reinstall the driver and it works so well.

  5. Dude if you were in my office I would kiss your frigging feet. I am been messing with SQL for an hour and then started running queries on the DB because I could not add domain users to my instance. That lead me to the MS site which led me to ‘ping’ doh! Then led me here. Thank you very much!

  6. superb, was breaking head to make it done, was running several VMs in my lab setup none of the machines got pinged with the DC, now resolved

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s