PeopleSoft Adoption Made Smooth & Simple!
On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool. Claim Your Free WalkMe Account Now
Course Of The Month
4 days, 16 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Simple Hyper-V networking scenario
Posted on 2013-01-21
I've been doing lots of reading and testing but am still confused with my Hyper-V network configuration.
Here is what I'm trying to achieve:
I want this server to host, via Hyper-V, several Windows XP Professional installs that can access the internet. Also, one of these XP installs will accept RDP connections from a remote jobsite so the user can remote control that XP virtual machine.
Any direction on how to configure the Virtual Network to achieve this? Or point me to articles that explain this scenario?
New install of Server 2008 Standard, without AD.
Only Role installed right now is Hyper-v.
Two NICs, one with an IP 192.168.1.20 and other with external static IP
The server is up and Hyper-V successfully runs new VHDs.
Here is what I'm trying to achieve:
I want this server to host, via Hyper-V, several Windows XP Professional installs that can access the internet. Also, one of these XP installs will accept RDP connections from a remote jobsite so the user can remote control that XP virtual machine.
Any direction on how to configure the Virtual Network to achieve this? Or point me to articles that explain this scenario?
[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
-
4
3
8 Comments
Active today
Attach the virtual network interfaces of the VMs, to your Production Interface (192.168.1.20), allocate the same IP Address to your VMs.
I'm assuming that the Production Network (192.168.1.20) interface (the host) has access to the internet?
then create a NAT forwarding rule on your router, to port forward TCP 3389 to this VM, which needs External RDP Access.
I'm assuming that the Production Network (192.168.1.20) interface (the host) has access to the internet?
then create a NAT forwarding rule on your router, to port forward TCP 3389 to this VM, which needs External RDP Access.
That does work, but isn't what I want. There are two NICs, the 192.168.1.20 is my internal network from the router that uses one static IP. I actually want the Hyper-V to use the other NIC with a different static IP so that the VHDs can get to the internet through that route. It's also an attempt to keep the user on those virtual machines from seeing resources on the 192.168.1.x network.
Active today
create a new network attached to that "external static IP" network interface.
http://www.petri.co.il/configuring-virtual-networks-with-hyper-v.htm
but you VMs, may require a different gateway, IP Addresses, and DNS entries to reach the internet.
http://www.petri.co.il/configuring-virtual-networks-with-hyper-v.htm
but you VMs, may require a different gateway, IP Addresses, and DNS entries to reach the internet.
Thanks. I imagine it would work to assign one virtual machine with a static IP, but I need those virtual machines to have different addresses that I manually enter. Think of it this way...my existing router uses static address 1.2.3.4 and my computer gets an address 192.168.1.6 via that router's DHCP. In a similar fashion, I would like the Hyper-V to use static address 1.2.3.8 and I would assign each virtual machine an address starting with 10.0.1.50. Perhaps I need a physical router in front of the server rather than putting the server straight on the public IP?
Active today
if your VMs are on a public network, you will need to have Public IP Addresses for them.
or you will need to use NAT from a single Public IP Address. This will be find for VMs accessing the internet, and NAT rule for RDP TCP3389
(the IP Address of the NIC in the server is irrelvant here, it just needs connecting to that external network, network traffic will flow from the external network to the VMs connected to that switch).
So do you have X Public IP Address, if you only have a single public IP Address, you will need to use NAT
or you will need to use NAT from a single Public IP Address. This will be find for VMs accessing the internet, and NAT rule for RDP TCP3389
(the IP Address of the NIC in the server is irrelvant here, it just needs connecting to that external network, network traffic will flow from the external network to the VMs connected to that switch).
So do you have X Public IP Address, if you only have a single public IP Address, you will need to use NAT
Well, they're not directly on the public network. From our exchange I gather that a router configured in front of the 2008 Server may do the trick. I will test and report back.
Just putting your requirements together:
New install of Server 2008 Standard, without AD.
Only Role installed right now is Hyper-v.
Two NICs, one with an IP 192.168.1.20 and other with external static IP
The server is up and Hyper-V successfully runs new VHDs.
It's also an attempt to keep the user on those virtual machines from seeing resources on the 192.168.1.x network. (By this I am assuming that you want to put the VMs in a different subnet)
There are a few ways that I can think of achieving this:
Method 1:
Add three NICs on the Windows Server 2008 host machine
NIC 1: 192.168.1.20
NIC 2: External IP
NIC 3: Will have the IP that is same as the VMs
All the VMs would connect to NIC 3
Configure NAT on the Windows Server 2008 host machine
With proper routing/DNS resolution in place, the VMs can use the NAT on the Windows Server 2008 host machine to get to the internet
NAT can be configured to do port forward to allow the RDP connection
Method 2:
Configure a VM with two NICs
NIC 1: Will have the IP that is same as the VMs
NIC 2: External IP
Configure NAT on this VM
The NIC 2 will be connected to the internet via the public NIC on the Windows Server 2008 host machine
Method 3:
Retain current configuration on the Windows Server 2008 host machine
NIC 1: 192.168.1.20
NIC 2: External IP
The VMs will be on a different subnet but could be accessing the network via NIC 1
NIC 1 would be connected to a trunk port and hence would support accessing 2 network via the same switch port.
Reference: http://blogs.msdn.com/b/adamfazio/archive/2008/11/14/understanding-hyper-v-vlans.aspx
Method 4:
Windows Server 2008 host machine with two NICs
NIC 1: 192.168.1.20
NIC 2: Will have the IP that is same as the VMs
All the VMs would connect to NIC 2
NAT configured on a h/w firewall that sits in the path from NIC 2 to the Internet
New install of Server 2008 Standard, without AD.
Only Role installed right now is Hyper-v.
Two NICs, one with an IP 192.168.1.20 and other with external static IP
The server is up and Hyper-V successfully runs new VHDs.
It's also an attempt to keep the user on those virtual machines from seeing resources on the 192.168.1.x network. (By this I am assuming that you want to put the VMs in a different subnet)
There are a few ways that I can think of achieving this:
Method 1:
Add three NICs on the Windows Server 2008 host machine
NIC 1: 192.168.1.20
NIC 2: External IP
NIC 3: Will have the IP that is same as the VMs
All the VMs would connect to NIC 3
Configure NAT on the Windows Server 2008 host machine
With proper routing/DNS resolution in place, the VMs can use the NAT on the Windows Server 2008 host machine to get to the internet
NAT can be configured to do port forward to allow the RDP connection
Method 2:
Configure a VM with two NICs
NIC 1: Will have the IP that is same as the VMs
NIC 2: External IP
Configure NAT on this VM
The NIC 2 will be connected to the internet via the public NIC on the Windows Server 2008 host machine
Method 3:
Retain current configuration on the Windows Server 2008 host machine
NIC 1: 192.168.1.20
NIC 2: External IP
The VMs will be on a different subnet but could be accessing the network via NIC 1
NIC 1 would be connected to a trunk port and hence would support accessing 2 network via the same switch port.
Reference: http://blogs.msdn.com/b/adamfazio/archive/2008/11/14/understanding-hyper-v-vlans.aspx
Method 4:
Windows Server 2008 host machine with two NICs
NIC 1: 192.168.1.20
NIC 2: Will have the IP that is same as the VMs
All the VMs would connect to NIC 2
NAT configured on a h/w firewall that sits in the path from NIC 2 to the Internet
So I have two NICs in the server. It has a NATted firewall/router with a single public IP. I attached another router firewall to the second NIC and the second IP with a different subnet. This worked by allowing RDP traffic to the virtual machines, but both subnets are visible from either direction. I'll have to try VLAN config again.
To mgpremkumar:
I will try again with VLAN tags. I didn't have any success earlier, maybe I had something misconfigured.
To mgpremkumar:
I will try again with VLAN tags. I didn't have any success earlier, maybe I had something misconfigured.
Featured Post
PeopleSoft Adoption Made Smooth & Simple!
On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool. Claim Your Free WalkMe Account Now
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
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…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller.
Log onto the new domain controller with a user account t…
Suggested Courses
Course of the Month4 days, 16 hours left to enroll
688 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.