Link to home
Start Free TrialLog in
Avatar of J.R. Sitman
J.R. SitmanFlag for United States of America

asked on

New VM not recognizing NIC

I just added a new VM to my existing Hyper-V server.  The new VM is a Windows 2003 R2.  In the Hyper-V settings for this server I assigned a NIC card.  However, when I'm logged on to the new VM it is not seing a NIC.  How do I add it.
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Have you installed the Integeration Tools from the cdrom yet?
Avatar of J.R. Sitman

ASKER

No, how?
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Just to add some info to the post above. Without the integration services some virtual devices do not work/are not recognized. These "Integration Services" are needed for non Hyper-V aware Operating Systems (such as Server 2003). Server 2008 on the other hand knows when it is running on Hyper-V (when using as a guest OS). The latter is also called an "enlightened" VM.

Thus, to solve your issue you should install the integration services as hanccocka said, or you could opt to use a legacy network adapter (recognized natively by Server 2003).

Hope this explained a bit.

Michael
Thanks, it worked.