Host vs. Virtual Subnet Issue/Question

Hi,
I am new to VM's and began working with Virtual PC 2007. I have:

Created a Win2003 Server VM (IP=10.1.3.10, Subnet=255.0.0.0, DNS=10.1.3.10)
Created a WinXP Client VM

I setup my server to be a PDC and it runs DHCP
I setup my client to use DHCP

All is well in that my client is configured with the correct IP addressing
specified in my domain DHCP scope and was able to join the domain, but what
is the best way to intergrate my Internet connection with both the client and
server? The host PC is on a different subnet (host=255.255.x.x,
virtual=255.x.x.x)than my virtual machines.

Thanks.

 

Two options.

1. Stop using DHCP and disable it so it won't conflick with the "real world"
LAN. Reset the IP#s on all of them to be the same IP Segment as the real world
LAN.

2. Create another Server (don't use the DC!!) and give it two Nics with one of
them being configured to be on the "real world" LAN. configure the machine with
RRAS to act as a NAT Server (NAT based firewall).

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------

 

Just to clarify, the host machine is a WinXP machine that exists on my "real
network" as a client.

I have created 4 VM's on the "real world" client:

1 PDC
1 All-purpose server
2 WinXP clients

My real world machine (subnet= 255.255.x.x) is serverd by DHCP and gets out
to the my intranet and the Internet.

My intent with the VM's was to create a virtual network with it's own
domain, DNS, and DHCP server. I ran DCpromo and setup DHCP. I used a
255.x.x.x subnet scheme, and everything seemed to work well, except I need to
figure out how to incorporate my "real world" connection to the Internet.
What is the best way to bridge my real world Internet connection and virtual
network together for the sake of an Internet connection? Can I do this with
the virtual network using a virtual subnet that is different than the host
machine? I think I am losing my senses here!

Thanks,
Kelly

 

I understood what you were doing.

It is the same answer,..expect #2 seems the best. You can do it with you
"all-purpose" server of create a special one for the job.

2. Create another Server (don't use the DC!!) and give it two Nics with one of
them being configured to be on the "real world" LAN. configure the machine
with
RRAS to act as a NAT Server (NAT based firewall).


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------

 

How do you give it two nics if the machine in question only has one nic?
Just curious....

 

Well, they are virtual machines, so you just do it in the Virtual PC Console
while the VM in question is shut down. You can give them up to 4 nics.
Whatever you choose in the dropdown list represents the physcal "wire". By
default the choices are Local, Not Connected, Shared NAT, and whatever Phycal
Nic is in the Physical machine.

You can add choices by adding more adapters to the machine such as real nics or
the MS Loopback Adapter. If you use the Loopback Adapter be sure to give them
unique names so that you can tell them apart on the list.

All VM nics that use the same dropdown choice are on the same "wire",....on
different choices means a different "wire". The only way to go from one wire to
another is by having one VM with multiple nics with one on each choice or "wire"
and this VM needs to be configured as a router (I mean a real router, not a
home-user store bought nat box). So you need a LAN Router to go from virtual
wire to virtual wire just like in the real world.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------