Hyper V Nic Cards advice/ steps

Ok, I just set up a brand new hyper v core server 2012.  The physical box has 2 onboard nic cards. I am going to set up 2 virtual machines, one will be a domain controller and one will be a file and print server.  What would be (and please include detailed steps) the best way to set up the nic cards and assign ip addresses to the virtual machines to match my network?
schmad01Asked:
Who is Participating?
 
schmad01Connect With a Mentor Author Commented:
I just solved my own problem. I unchecked the option to use a vlan id.  But just to clarify, if I wanted to use that option, I'm assuming I would have to have a matching id on a managed switch, is that correct or am I way off on that?
0
 
Cliff GaliherCommented:
Detailed steps? That'd require much more knowledge of your network. VLANs, types of NICs, whether you want to segregate management traffic.

Put simply, there is no way to answer this question. Configuring and managing hyper-v requires SOME knowledge already. If you have specific questions, there are plenty of experts on EE who can help. But if you just want a full tutorial, you should buy a book or hire a paid consultant. There is just too large of a knowledge gap and too may variables to accurately address the questiom as posed.
0
 
schmad01Author Commented:
It's just a simple network, no managed switches or vlans. 1st nic on the host a has static ip address for management and the 2nd nic is dynamic.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
schmad01Author Commented:
Ok, I've done my reading. I created a virtual switch in Hyper V virtual switch Manager.
I used all the defaults but chose not to allow management to share. I named it Vswitch1.  I assigned it to NiC2. I then went to my virtual machine and created the network adapter and assigned it to Vswitch1.  The problem I'm having now is the network adapter in my virtual machine can't identify the network.  I have it an ip address to match my physical network including the default gateway and dns server. Any suggestions?
0
 
Cliff GaliherCommented:
Basic troubleshooting. Ping. Nslookup. Netmon/wireshark.. find out if packets are flowing in or out of the VM at all. Like a physical OS, other factors can play a part. Chances are hyper-v is not the issue, given your description so far.
0
 
schmad01Author Commented:
Before I even created the virtual switch or adapter nic#2 was working fine, obtained ip address, connected to the network, internet, etc. Soon as I created switch and adapter, of course the nic then is stripped of all protocols except hyper v extensible switch. So, with that said, yes, I believe something is missing either in hyper v or with the created virtual switch or adapter.
0
 
schmad01Author Commented:
I just solved my own problem. I unchecked the option to use a vlan id.
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.