The way I do this is by having a dedicated router VM as well.  It is dual
homed - one NIC bound to the hardware and therefore on the 'real' LAN (the
'public' NIC), and the other on a VM-only network (the 'private' NIC).  I
have my test VMs route out through the router VM which isn't part of the
test domain.  It truly acts as a router / firewall.

I have often used Server 2003's RRAS for this, but I recently switched to
Vyatta VC5 (http://www.vyatta.org/downloads) so that I can have multiple LAN
ip addresses bound to the router's public NIC and forward the same port on
different ip addresses to different machines on the test network.
 (Currently playing with Exchange 2003 to 2010 migration scenarios where I
keep the 2003 server alive for a period of time.)

HTH,

RS

On Fri, Feb 26, 2010 at 1:04 PM, Glen Johnson <[email protected]> wrote:

>  Hoping someone can point me to a workaround for this.
>
> We have a lab of 8 vista boxes running VPC 2007 sp1.
>
> The teacher is teaching server 2008 and wants to have each student set up a
> domain controller and client workstation.
>
> We set up the server and client as guests, configuring each to use Shared
> NAT networking.
>
> Problem is the two guests can’t talk to each other.
>
> I see in the help that this is expected, but I’m wondering if anyone knows
> how to allow the guests to talk to each other, other than using Private”
> networking.  With private, they don’t have access to the internet, which
> they also need.
>
> Thanks and happy Friday to all.
>
>
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to