> The situation doesn't really change because you are using virtual
> machines and virtual networks. You do it just the same way as you would to
> isolate a test LAN segment from the rest of the network.
>
> The simplest way to do it is to put the test LAN behind a NAT router.
> The test machines can then contact the machines on the physical LAN and
> thence to the Internet. The machines on the physical LAN are unaware of the
> test machines because NAT is a one-way address translation system.
>
> You can run the NAT router on the host or in a vm. To run it on the host
> you will need to run your vms on a vitual network linked to a loopback
> adapter in the host. If you run the router in a vm, you configure one NIC in
> the virtual network and the other linked to the physical NIC in the host
> machine.
>
> If you want greater control over what does or does not go across the
> link you can run a firewall like ISA server instead of NAT.
>
> "Mr. JYC" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hello,
> >
> > I have a server that I use it to test software. This server is a Windows
> > 2008 server with Virtual Server 2005 R2 on it. It has a dozen virtual
> > servers running on an isolated virtual segment. To connect the virtual
> > servers to the Internet, it uses a physical network interface card. The
> > address space for the virtual servers must not be the same as any others
> > in
> > my company. Other networks within the company should not access the
> > virtual
> > network address space either. Because of a little issue, I need to have
> > the
> > virtual servers connect to the Internet that the regular networks do so
> > that
> > they can access preconfigured vendor update servers. I still have to have
> > all address spaces of all networks separated. What should I do to acheive
> > this?
> >
> > --
> > Thank you for your help!
> > JYC
>
>

> Hello,
>
> I have a server that I use it to test software. This server is a Windows
> 2008 server with Virtual Server 2005 R2 on it. It has a dozen virtual
> servers running on an isolated virtual segment. To connect the virtual
> servers to the Internet, it uses a physical network interface card. The
> address space for the virtual servers must not be the same as any others
> in
> my company. Other networks within the company should not access the
> virtual
> network address space either. Because of a little issue, I need to have
> the
> virtual servers connect to the Internet that the regular networks do so
> that
> they can access preconfigured vendor update servers. I still have to have
> all address spaces of all networks separated. What should I do to acheive
> this?
>
> --
> Thank you for your help!
> JYC