network configuration for internet connection

follow that


http://blogs.technet.com/b/letsdothis/archive/2013/11/11/configuring-hyper-v-for-multiple-subnets-with-only-one-nic-server-2012-r2.aspx

first you have to Create Virtual Switch

and then new feature RASS - which will allow routing between two

Hi,

Thank you for getting back to me.
I am using VM clients and not hyper-V, have you got any instructions for that?

Thanks inadvance

HI,

I have got win2008 R2 installed but I don't see "Routing and RAS Admin", is this not installed with the installation?

thanks inadvance

Hi,

I have added the service now, I properly wont get a chance tonight to do this so I will try tomorrow.
I will let you know how I get on.

Thanks in advance

hi all,

I have not got a clue where to start dong this, what I need to do is connect 10.10.10.x which is a vm environment in my lab to my host system which is 192.168.0.x and also be able to connect to the internet.

can anyone please help me with this please.

Thanks inadvance

You will not connect to the internet without a configured gateway.

Hi,

After I had added a network adaptor on my VM, I found that I could then connect to the internet from my host which is on ip 192.168.0.x and also I could ping my VM clients which is on ip 10.10.10.x.

Do I still need to configure RRAS?

Thanks in advance

Routing and Remote Access Services (RRAS) are used for VPN (meaning remote access) and routing over a box (Routing). It is not needed, otherwise.

It is also not recommended to route over a box. Hardware firewalls or routers are best to route over. Routing involves taking packet headers, stripping them off, and recreating them to send the packets on. That is resource intensive, and on a VM machine, you want resources for multiple VMs on the servers. Leave routing and remote access to a hardware firewall/router. Using a box for this has always been a mistake (especially because there is explicit configurations to get any type of RRAS to work right).

You need to configure the NIC in your VM to use NAT, and connect it to the NIC on your PC.

If you can't do that because you need to keep the 10 range on your VMs you need to bridge the NIC in the VM configuration and configure the router to use the 10 range also.

The DC will never get internet access as it doesn't use a gateway.

A gateway is necessary for the DC because of the DNS servers. How else will DNS forwarders and Root hint queries work?

@Chief... if you're replying to my comment I'm agreeing with you.  The DC needs a gateway, but I'm just saying it'll never get internet access as it doesn't currently have a gateway.

:-)

Oh, misinterpreted that Craig.

No probs Chief!

@ciscocharlie... If you want to contain your VMs in their own network but still get internet access you could set up a proxy server on one of your VMs and attach a bridged NIC to it.  That way you could configure the proxy server in the browser on each of your VMs that needs internet access while still keeping them on their 10 range.

Just a thought...