Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Connecting two physical Hyper-V servers together without seeing production network.

Posted on 2013-06-25
1
Medium Priority
?
494 Views
Last Modified: 2014-11-12
I'm looking to run a test domain on a separate subnet, so only the VM servers can see each other, and not see any other network.

I currently have 2 servers. Both running Windows Server 2012 DataCenter and both have Hyper-V Manager installed.  

I have images of my DC and exchange server. I also created a fresh VM w/ Windows Server 2012(will use for exchange 2010 test migration)
 
Each Server has 1 NIC plugged into the production lan. I have the Hyper-V Virtual switch as external. Once I boot a server up in VM, I can set each one static and they see each other. but if I let dhcp takeover, the server try and move over to the production LAN. I currently don't have any VLANs configured on my physical switches, so I haven't enabled anything on the VM servers.  how do i get the VM servers to default to the test domain? It seems if I use internal/private virtual switches, the VM on each physical server end up losing connectivity between each other.

Each server has 4 physical NICS, so i did try and setup a 2nd physical NIC w/ a static ip of the VM network, but i still couldn't get the VM serves to stay on the VM network.

What's the best way to set this up?

production network:
192.168.0.1
255.255.248.0

VM network:
192.168.100.1
255.255.255.0
0
Comment
Question by:AfternoonShift
1 Comment
 

Accepted Solution

by:
pchindustries earned 1500 total points
ID: 39277247
You have a couple of options.

The simplest option is to create a VLAN on your production switch to segment traffic from your production LAN. If this is not possible then you must create a new virtual switch (leave the current production virtual switch unchanged) on each Hyper-V host and connect that virtual switch to one of your physical nics that is not in use by the production LAN. You then must connect the the NICs for your new virtual switch together by using a crossover cable or a switch that is totally separate from your production switches. Once you do this, connect your VMs to the new virtual switch and they will all be able to see each other.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

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

Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
Optimized for private cloud infrastructures and datacenters, Nano Server is minimalistic, yet super-efficient, OS for services such as Hyper-V and Hyper-V cluster. Learn how you can easily deploy Nano Server and unlock its power!
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…
Suggested Courses

916 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