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

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 (192.168.0.253) and one NIC on the host is suppose to be an exclusive NIC for the guest (192.168.0.7)

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?
LVL 1
Eric_PriceAsked:
Who is Participating?
 
Eric_PriceConnect With a Mentor Author Commented:
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.

nvspscrub

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.

Almost.

Thanks again!
0
 
Eric_PriceAuthor Commented:
This link here is very much like the issue I am having.

http://www.mail-archive.com/ntsysadmin@lyris.sunbelt-software.com/msg113402.html
0
 
SandyCommented:
please check with legacy network adapter.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Eric_PriceAuthor Commented:
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:
•      SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
•      START DEVMGMT.MSC
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 192.168.0.251)

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.
0
 
Eric_PriceAuthor Commented:
Sandeep - It would not let me install a legacy driver. It knew it was the intel card, but said the device was configured incorrectly.
0
 
SandyConnect With a Mentor Commented:
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)
0
 
Eric_PriceAuthor Commented:
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.
0
 
Eric_PriceAuthor Commented:
So, if I do a

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

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

Now 192.168.0.1 is saying its type is Probe
0
 
Mohammed HamadaConnect With a Mentor Senior IT ConsultantCommented:
Maybe you should consider something like Treexy Driver cleaner to clean up drivers and their registry remnants as well.
0
 
Eric_PriceAuthor Commented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.