After reading Glenn's comments, it appears that our thoughts are pretty well inline - each of us covering different areas in more depth.
The easiest way for you to get this going based on your comments is to configure the Production network NIC in the VS2005 machine with ICF and then assign a static IP (as you suggested) to the Test network NIC - this implies not messing with RRAS at all. Following this configuration you should be able to point each of the VMs to the IP address of the Test network NIC as their gateway. Optionally they could also use this IP as their Primary DNS resolver; however if you will be using DNS servers on the Test network you may want to point the Test hosts their, and use the DNS servers to forward requests to the production network. Again, there are many ways to do this... Regards, Aric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Your Name Sent: Monday, November 29, 2004 11:15 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Virtual Server 2005 Thanks. >From your descriptions, I think I would want to use NAT only on the NIC connected to the production network. That is, have all of the traffic from the virtual network appearing as a single address on the production network. Since I want everything on the test network (virtual and physical hosts) to appear on the same subnet, I don't think I want NAT on the Test NIC. In assigning it a static address on the virtual subnet, does it become a gateway under RRAS? I'm a little unclear on this, and (I think) it runs counter to Glenn's recommnedation earlier. I will try some configurations later in the day. Greatly appreciate the detailed suggestions. -- nme > The Test Physical NIC should be configured with a private IP address > that is on a subnet unique when compared to your production environment. > You mentioned that you assigned static address to your VMs, therefore > you Test Physical NIC should be on the same subnet as the VMs. > > > > With regards to routing, you do need to set up a device to route between > the two networks. How you do this depends on your planned architecture. > Do you want "true routing" or "NATed routing"? > > > > For true routing, set up the physical host with the Production and Test > NICs with RRAS configured as a router. This will allow all VMs, when > configured with the proper gateway, to "freely" route from their Test > network to the Production network. > > > > Using a NAT instead will limit the ability of the VMs to talk to the > production network. In your general scenario, this is the method most > often used in order to isolate the test network as much as possible. To > do this you have three basic options: > > > > 1. Use RRAS to setup a NAT on the physical host with both NICs. > > 2. Use ISA to setup a NAT on the physical host with both NICs. > > 3. Use Windows Internet Connection Sharing (OS dependent) to set up a > NAT on the physical host with both NICs. > > > > Of course, with any of these options you could substitute the use of the > physical host for that of a VM so long as the VM is configured with two > NICs, one on the Test LAN and one on the Production network, as is the > physical host it resides on. > > > > Your host DNS suffix configuration should not negatively impact > anything... > > > > > > HTH List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
