"Mike Porcellana" <MikePorcellana@xxxxxx> wrote in
message news:5696A184-51CB-4A34-A6C9-056626270547@xxxxxx
Quote:
> Will give it a try later today...THANK YOU very much!!
>
I would just add one proviso to what Bo has said. If you are running a
domain, it is not a good idea to use the dc as a router. (This is a general
rule, not restricted to virtual machines. The only exception is sbs server
which is designed to run like that).
Since you have ample memory I would run a separate machine as a RRAS
router between the virtual network and the physical network.
I would go ahead and set up the domain in local only on its own private
subnet. After this is running successfully you can look at connecting this
network to the physical network for Internet access. I use Server 2003
running in a vm as a NAT router for this.
Here is how I had this set up under VPC.
Internet
|
Netgear
192.168.0.1
|
LAN machines including VPC host (workgroup)
192.168.0.x dg 192.168.0.1
|
192.168.0.200 dg 192.168.0.1
RRAS vm
192.168.21.254 dg blank
|
DC
192.168.21.1 dg 192.168.21.254
|
AD clients
192.168.21.x dg 192.168.21.254
You can even run DHCP on the virtual network for you private LAN if you
like, because it is isolated from the physical network.
Because all AD machines must use the local DNS, you need to set the
local DNS server to forward to a public DNS (such as your ISP) so that AD
machines can resolve "foreign" URLs (such as Microsoft Update).