Solved

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

Posted on 2013-06-25
1
471 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 500 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

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Last article we focus in how to VMware: How to create and use VMs TAGs – Part 1 so before follow this article and perform the next tasks, you should read the first article how to create the TAG before using them in Veeam Backup Jobs.
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
In this video tutorial I show you the main steps to install and configure  a VMware ESXi6.0 server. The video has my comments as text on the screen and you can pause anytime when needed. Hope this will be helpful. Verify that your hardware and BIO…

747 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now