How connect to internet from domain created in Hyper-V

Question

How connect to internet from domain created in Hyper-V
Host =  Win8 Pro
Connection to internet done using WI-FI
Internet seeting
Home router with secury connection -> cable internet
Network name set on router = "Mtl2014"
Host setting
TCP/IPv4 Seeting for WI-FI ,connected to "Mtl2014"
Obtain address automaticly
Obtain DNS server address automaticly
I can connect and browse internet from host
In Hyper-V
 1.created 2 private virtual switches SW1 and SW2
 2.installed 2 VM HA1 and DC with Win2012 server eval edition
 3.assigned stations HA1 and DC  to virtual switch SW1
on Host
WI-FI network connection
 Sharing->Allow other network to connect.. ->Home network connection vEnthernet (SW1)
in Hyper-V
 choose Activate windows on  HA1 and DC
 open browser on HA1 and DC ,
 At this point I am able to see and browse and search in google from HA1 and DC
In Hyper-V
 assined virtual switch SW2 to DC and HA1
 created Domain controler on DC and domain Alex1.com
 TCP/IPv4 Seeting on DC
 IP = 192.165.1.8
 subnet = 255.255.255.0
 default getaway = empty
 Prefered DNS server = 192.165.1.8
 TCP/IPv4 Seeting on HA1
 IP = 192.165.1.11
 subnet = 255.255.255.0
 default getaway = 192.165.1.8
 Prefered DNS server = 192.165.1.8
 added HA1 to domain Alex1.com
Question
 What seeting on SW2, DC, HA1 and  Wi-FI should I change in order to have access to internet from  Alex1\DC and Alex1\HA1?
I was planning to use internet to download/install pacthes/updates for windows and sql servers located on Alex1\
I plan to build 6 more Win 2012 server eval and join then to Alex1\
Thank you
Alex

Answer 1

I see.
1. 192.168.0.0 addresses are not routable across the public Internet. Even if the whole world knows you're using that space, the information is useless. But if you feel better hiding it, OK.
2. Internal doesn't allow communications with a physical network either. Only the external type does.
3/4. Your problem is not really with Hyper-V. It's with IP.
Your machines are all able to communicate with each other because they're on the same switch and the same subnet. No gateway is required. If you have a computer with an IP of 192.168.1.8 and its subnet mask is 255.255.255.0, then it will be able to communicate
with any computer on the same switch with an IP of 192.168.1.anything. It's when they need to talk to computers off of that subnet (anything that doesn't fit the 255.255.255 mask) that they have a problem. For that, you need a gateway somewhere. You can't
use "DC" for the gateway because it's not performing routing services.
You have two choices.
One is to use an external switch so that your guests are directly connected into your physical network. That will take over your WiFi adapter, so you'll probably want to set the share option so your Win8.1 box continues to function. Then just use a common
IP subnet with everything else on your home network.
The second is to set up a software router. If you are using an internal virtual switch, then this has to be in the Win8 environment. I might be mistaken, but I think that
Internet Connection Sharing would even work for this. If you are using an internal virtual switch, then your Win8 system should see two (or more) adapters. One of them is the physical adapter (we'll call it wNetAdapter) and one would be the virtual adapter
(we'll call it vNetAdapter) it uses on the virtual switch. Once you set up ICS, you would have all of your VMs use the IP address that you assigned to vNetAdapter as their gateway.
Eric Siron Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
"Every relationship you have is in worse shape than you think."