Solved

Server 2008 Hyper-V Network Configuration

Posted on 2014-11-25
6
137 Views
Last Modified: 2014-12-04
I am setting up a 2008 host with 2 physical nics and, at present, 1 guest OS, also 2008. I know, I'm in the dark ages. I want this guest to connect to internet, LAN and potentially another guest, without interfering with the host networking at all. How would I handle IP addressing on the 2nd nic and how it's handled in Hyper-V (External, Internal, Private).
0
Comment
Question by:jconklin-ansinc-net
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 2

Accepted Solution

by:
FinServCo earned 500 total points
ID: 40465364
NIC2 shouldn't have an IP address.  In Hyper-V manager, click on Virtual Network Manager at the right.

Click New Virtual Network, select External.  Name it, select the NIC you want to use, and you could uncheck "allow management operating system to share this network adapter".  That will set up a virtual network adapter that you can assign to one or more guest VMs.

When you do that, it will uncheck most of the settings under the NICs properties in control panel and leave checked the driver and Microsoft Virtual Network Switch Protocol.  

Then any IPs get set in the Guest OS NIC.
0
 
LVL 42

Expert Comment

by:kevinhsieh
ID: 40465937
Ouch, serious dark ages. I highly recommend that you not use Windows 2008 as the host. Any other version of Windows Server or Hyper-V server is acceptable. You can manage the free Hyper-V Server from itself or any version of Windows using the excellent 5nine Manager for Hyper-V. This eliminates the worries of not having a full Windows GUI or having the correct version of the client OS for management. Performance and stability from the later versions of Hyper-V is much better.

http://www.5nine.com/5nine-manager-for-hyper-v-free.aspx
0
 

Author Comment

by:jconklin-ansinc-net
ID: 40473584
FinServCo: It required an IP on the host NIC 2. If I didn't set it static then it picked one up via DHCP.  It also created the virtual switch NIC.
0
Space-Age Communications Transitions to DevOps

ViaSat, a global provider of satellite and wireless communications, securely connects businesses, governments, and organizations to the Internet. Learn how ViaSat’s Network Solutions Engineer, drove the transition from a traditional network support to a DevOps-centric model.

 
LVL 2

Expert Comment

by:FinServCo
ID: 40480639
Yes, but once you created the virtual switch, it should have lost the IP and the only things bound to NIC2 on the HOST machine should be the driver and Microsoft Virtual Network Switch Protocol.

Then you configure the IP settings within the GUEST machines, having set the guests to use the virtual switch associated with NIC2.
0
 

Author Comment

by:jconklin-ansinc-net
ID: 40480745
FinServCo- No, the Host NIC2 still has an IP address. It also has the interface showing the Virtual Network Switch Protocol, and the guest OS has an IP. It seems like a waste of an IP address but maybe it's because it's 2008.
0
 
LVL 2

Expert Comment

by:FinServCo
ID: 40480840
Okay, that's because you have "allow management operating system to share this network adapter" checked.

When you set a NIC as a Hyper-V virtual network, Hyper-V takes it over.  So if you have the "allow management operating system to share this network adapter" checked, you won't see the IP address in the adapter properties, but it will show up at the command line.

This is so that you can have one NIC that's dedicated to management, and another NIC that's part of a virtual network that can be assigned to guest VMs and also used to manage the Hyper-V host server if NIC1 loses connectivity.
0

Featured Post

Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

Question has a verified solution.

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

A safe way to clean winsxs folder from your windows server 2008 R2 editions
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

705 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