please help me fix the NIC in my hyper-v virtualized instance of SBS 2011

Posted on 2013-01-03
Medium Priority
Last Modified: 2014-11-12
First off, Im an idiot. Im in the midst of a job change, and in the flurry to wrap things up Ive done just about everything wrong that I could have. Heres where I am

I have 4 vhds that represent four hard drives in a virtualized 2011 SBS server. The host is 2008 R2 Std. One NIC on the host is for the host ( and one NIC on the host is suppose to be an exclusive NIC for the guest (

Theres a long drawn out story about how we got here, but Im not sure it matters. Heres what I want to accomplish

1) clean out all references to old NICs from my bazillion "quick attempts" to fix this problem over the last 24 hours

2) create a virtual NIC and assign the original IP address to it

Theres lots of links on the web about how to make hidden NICs appear and uninstall them, but that alone isnt getting the job done. Who can help out?
Question by:Eric_Price
  • 7
  • 2

Author Comment

ID: 38742876
This link here is very much like the issue I am having.

LVL 13

Expert Comment

ID: 38742902
please check with legacy network adapter.

Author Comment

ID: 38742944
I was just considering that Sandeep, mostly because im getting pretty desperate. Just hated to, knowing that once upon a time it worked with the normal driver.

Ill go ahead and throw out that Ive pretty well done these steps

•      Shut down the VM
•      removed the virtual NICs using the Hyper-V management console
•      started the VM
•      cleaned up some old phantom adapters
•      shut down the VM
•      re-added the virtual NICs in the management console
•      Started teh VM and configured its networking.

Also, for getting rid of the old adapters

1.      Open a command prompt with administrative privlidges (right-click, Run as administrator)
2.      In the command prompt enter the following two commands in order:
3.      The second command is very important, because if you don't start the Device Manager session from inside the elevated command prompt you just opened, you won't have the proper settings.
4.      Once Device Manager is open, go to "View" and select "Show hidden devices"
5.      Expand "Network Adapters" and you should see any VM NICs that have been removed (they will be greyed out).  Select them, right-click and choose "Uninstall"

Original Article

This last time (which I just finished) I tried using a new IP (same subnet obviously) and I only added the vmware nic back in after a) reinstalling the integration software and b) removing any registry references to "Local Area Connection" in the HKLM\SYSTEM\ControlSet001\Control\Network section of the registry. I didnt find any articles telling me to do it per se, but Ive had trouble with server remembering my IP, and it seemed reasonable with the name (LAC) that they were left overs.

With that, I find that my IP address now "sticks" to the adapter in a way that it didnt before, and yet I still cant ping anything else on the network (which I can from the host). The error is either Destination host unreachable from the IP of the virtual guest or Request Timed Out. I can ping my own IP (now

When I boot to safe mode with networking the result is the same - can ping self, but not network.

The firewall on both the host and guest are off at the present time.
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 38742968
Sandeep - It would not let me install a legacy driver. It knew it was the intel card, but said the device was configured incorrectly.
LVL 13

Assisted Solution

Sandy earned 1400 total points
ID: 38742979
Eric, Please try following

1. Let the host machine as it is now just remove the virtual adapter from VM and under add new hardware please use legacy network adapter.

2. Ensure VLAN ID or trunk is configured (If applicable).

3. Configure VM Legacy network adapter with network configuration.

4. Also check any IPSEC policy is not in enforced condition.

Meanwhile i am also searching as how can i help out (if i can)

Author Comment

ID: 38743025
That pretty well describes what I did, unless its late enough here that Im misinterpreting. I took the virtual down, removed the regular driver, booted up, went through the manual uninstall process, took the virtual back down, added the legacy, booted up. It intiially didnt have a driver for the legacy device (but did show it). When I asked it to scan for a suitable driver it indicated it knew it was the Intel card, but said it wasnt configured properly. Moreover, several of the things Ive read this evening suggest a) that the legacy card performs worse and b) more importantly, didnt support 64 bit versions of 2003 / xp. dont know if that changed moving forward or not.

I have since taken that card out and put the regular driver back in and once again have something that looks ok, until I actually need to ping something beyond my own virtual self.

Author Comment

ID: 38743086
So, if I do a

netsh interface ip show neighbors I get several entries. Here are some relevant ones

Internet Address                                 Physical Address                 Type                                         00-21-55-75-c3-16               Incomplete                                         Unreachable                        Unreachable                                     40-61-86-85-16-ee              Stale                                           01-00-5e-00-00-16               Permanent

Now is saying its type is Probe
LVL 24

Assisted Solution

by:Mohammed Hamada
Mohammed Hamada earned 600 total points
ID: 38743089
Maybe you should consider something like Treexy Driver cleaner to clean up drivers and their registry remnants as well.

Accepted Solution

Eric_Price earned 0 total points
ID: 38746824
So... thanks for the ideas guys. In the end, I ended up using a tool to programmatically clean out the registry and settings of all my old network information.


It allowed me to do what I apparently could do manually. Or maybe I just got lucky. I linked to the tool though in case someone else comes along with the same problem.

Almost makes me pine for the old days of real network cards.


Thanks again!

Author Closing Comment

ID: 38762296
The link I provided was the thing that ultimately fixed my phantom NIC issue and allowed me to start from scratch on rebuilding NICs and getting IPs assigned.

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

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

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 …
In this article will go through how to backup a vPostgres DB from a broken vCenter Appliance and restore to a new vCenter Appliance.
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
Suggested Courses
Course of the Month14 days, 23 hours left to enroll

840 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