<

Hyper-V Network Card not working

Published on
46,067 Points
36,967 Views
11 Endorsements
Last Modified:
Approved
Community Pick
Hyper-v Network Card not working

There are two common mistakes that people make when they setup a Hyper-V VM.

First problem is that they don't install the integration components before they start troubleshooting problems with the Hyper-V VM functionality. One thing the integration components do for the VM is to give the VM a network driver.

Second problem is that they assume that the network driver will be installed during the installation of the VM but that is incorrect you must install the integration components within the VM for the network driver support. If the VM needs to be installed through a PXE boot then you must install a Legacy Driver for this support before you install the OS.

Now I have ran into problems even with the Integration components being installed the Network driver installed by the integration components won't be recognized by the OS. What the fix for this issue is to use the Legacy Network Adapter.

To install the integration components

Before you start make sure you have installed the most current Service Pack and updates for the Guest OS. Make sure you restart the Guest OS after installing the updates.

1. Logon to the Guest VM with Administrative rights.
2. From the Hyper-V menu select the Action Menu and choose the Insert Integration    
    Services Setup Disk option within the menu.

Once you have done the two above steps the installation of the Integration Services should start automatically. After the installation you will need to restart the Guest OS.

Installing a Legacy Network Adapter.

(Legacy Adapters aren't supported in Windows Server 2003 64-bit or Windows XP 64-bit)

1. Make sure your Virtual Machine is shutdown.
2. Right-click the Virtual Machine in Hyper-v select Settings.
3. Select Add Hardware.
4. On the Add Hardware page select Legacy Adapter.
5. Then click Add.

Once you have finished the above steps make sure you see your Legacy Adapter under the installed Hardware within the VM's settings. If you have any other Network Adapters listed make sure you remove those.
11
Comment
2 Comments
 
LVL 1

Expert Comment

by:-Meitzi-
Also, if you did try Install "Integration Services" to Windows Server 2008 or Vista without SP2 installed, you may have same kind of problem.

Follow trick was helpfull for me:
run msconfig
on "boot" page click "Adcanded options" click "Detect HAL" and reboot
0
 
LVL 1

Expert Comment

by:roddines
Make sure that when your using the Legacy Network adapter only use 1 cpu in your Hyper-V CPU settings.  Then once you have the Hyper-V Linux Integration Services installed then the multiple CPU works.  I spent a week trying to work this out.
0

Featured Post

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

Join & Write a Comment

Did you know PowerShell can save you time with SaaS platforms? Simply leverage RESTfulAPIs to build your own PowerShell modules. These will kill repetitive tickets and tabs, using the command Invoke-RestMethod. Tune into this webinar to learn how…
Overview of OneDrive and collaboration.

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month