Mixed up in Hyper-V network configuration
Hello, let's get straight to the point. This is the infrastructure that I'm trying to obtain (ip adresses fictive):
I have 2 brand new (and powerful) servers running Windows server 2008 Enterprise.
Server 1 acts as main server. Server 2 will act as a backup with failover clustering of Server 1.
On Server 1, a domain is created for the main office, with around 30 users. That server has DNS, DHCP and file sharing roles. Hyper-V role is also added, but no virtual machine is yet created on it. The server itself has 6 network ports, spread over 3 double-port NICS.
(fictive IPs):
Port 1: 10.13.224.9 (active, principal connection)
Port 2: 10.13.224.4 (inactive at the moment, plan to use it in the cluster)
Port 3: 10.13.224.5 (inactive at the moment)
Port 4: 10.13.224.6 (inactive at the moment)
Port 5: 10.13.224.7 (inactive at the moment)
Port 6: 10.13.224.8 (inactive, but renamed as "Hyper-V physical connection", as I intend to use it as the physical link of Hyper-V).
Subnet 255.255.255.0 on all nics.
For the main office, everything works well, users connect, access the shares and all. My problems come from my Hyper-V configuration. Being somewhat a newbie with the product and with virtualization, I'm just stuck with how to configure the networking part. What I want for the VM:
- Will host Server Standard 2003
- Will be the DC of a NEW domain, with 6 users who will use it as their main server for file shares, authentication, printing.
The VM will use the host server's access to the Internet to connect to the Internet itself and share it to the machines connecting to it. While this is possible, the users of the new domain will only interact with the VM, and not the host's domain, users and shares.
Basically, 2 domains, 1 on a VM with computers connecting to it, but Internet shared between both through the host's connection.
What I can't figure out is how to configure the IP addressing both on the host and on the VM so the VM connects to the Internet of the host's machine, and how to configure the users' computer that will only use the VM's domain to only connect to that machine and not the host, basically using only the nic dedicated to the VM.
Am I making any sense?
Please help!
Thank you!
I have 2 brand new (and powerful) servers running Windows server 2008 Enterprise.
Server 1 acts as main server. Server 2 will act as a backup with failover clustering of Server 1.
On Server 1, a domain is created for the main office, with around 30 users. That server has DNS, DHCP and file sharing roles. Hyper-V role is also added, but no virtual machine is yet created on it. The server itself has 6 network ports, spread over 3 double-port NICS.
(fictive IPs):
Port 1: 10.13.224.9 (active, principal connection)
Port 2: 10.13.224.4 (inactive at the moment, plan to use it in the cluster)
Port 3: 10.13.224.5 (inactive at the moment)
Port 4: 10.13.224.6 (inactive at the moment)
Port 5: 10.13.224.7 (inactive at the moment)
Port 6: 10.13.224.8 (inactive, but renamed as "Hyper-V physical connection", as I intend to use it as the physical link of Hyper-V).
Subnet 255.255.255.0 on all nics.
For the main office, everything works well, users connect, access the shares and all. My problems come from my Hyper-V configuration. Being somewhat a newbie with the product and with virtualization, I'm just stuck with how to configure the networking part. What I want for the VM:
- Will host Server Standard 2003
- Will be the DC of a NEW domain, with 6 users who will use it as their main server for file shares, authentication, printing.
The VM will use the host server's access to the Internet to connect to the Internet itself and share it to the machines connecting to it. While this is possible, the users of the new domain will only interact with the VM, and not the host's domain, users and shares.
Basically, 2 domains, 1 on a VM with computers connecting to it, but Internet shared between both through the host's connection.
What I can't figure out is how to configure the IP addressing both on the host and on the VM so the VM connects to the Internet of the host's machine, and how to configure the users' computer that will only use the VM's domain to only connect to that machine and not the host, basically using only the nic dedicated to the VM.
Am I making any sense?
Please help!
Thank you!
ASKER
Hello,
No, there's no proxy. The gateway is on the same ip range, and is a fiber optics to ethernet converter (constantly connected).
As for your second comment, I understand that, but since the vm is really running a minimal configuration, and that clustering will be used anyways, I figured that it would be ok to work the way I am.
I am not done with the configs, so nothing is for sure yet. I can still reinstall with minimal configs and hyper-v role only. It still doesn't tell me how to configure the network though lol.
Thank you.
No, there's no proxy. The gateway is on the same ip range, and is a fiber optics to ethernet converter (constantly connected).
As for your second comment, I understand that, but since the vm is really running a minimal configuration, and that clustering will be used anyways, I figured that it would be ok to work the way I am.
I am not done with the configs, so nothing is for sure yet. I can still reinstall with minimal configs and hyper-v role only. It still doesn't tell me how to configure the network though lol.
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
If I set up manually the Ips of the computer connecting to the VM (around 5 machines), specifying the DNS to be the VM's ip, can I leave the DHCP on for the other machines that are connecting on my host, so that they get the adresses dynamically, with the DNS being the host's?
ASKER
Thank you, everything works well now :)
It's probably a bit late now, but are you aware the host should not have anything running on it other then the HyperV role? I know it's a bit of an overhead, but really in this instance you should have created two VMs, one for each AD domain.