Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 499
  • Last Modified:

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

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
AfternoonShift
Asked:
AfternoonShift
1 Solution
 
pchindustriesCommented:
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

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

Tackle projects and never again get stuck behind a technical roadblock.
Join Now