> That is pretty much what should happen. Setting up a domain is a
> non-trivial operation, whether you are using physical or virtual machines.
>
> If you want to use DHCP, you really need your domain machines to be in
> their own network, not linked to the host's physical network. And they need
> to be in their own IP subnet. With VPC the best idea is to put them in local
> only. The AD clients will get their network config from DHCP on the DC and
> Active Directory will all work.
>
> Internet access is another matter altogether. To do that you need a
> machine which can act as a router between the virtual network and the
> physical network. You can use a virtual machine with tw NICs, one linked to
> the virtual network and one to the physical network (through the host
> machines's NIC). I would not recommend using either a DC or an Exchange
> server for this. You could use Win2k/2k3 with RRAS or a Linux vm running as
> a NAT router.
>
> There is still the problem of DNS. Since the AD machines all use the
> local DNS (so that they can see the SRV records) they cannot resolve foreign
> URLs. You need to set up the local DNS to forward to a public DNS (or a DNS
> server on your physical LAN which can resolve them). This is not because you
> are using virtual machines. You need to do the same with real machines on
> real networks.
>

> I'm trying to set up a domain for testing purposes and am failing.
>
> One Win2k8 RC1 is set up as a DC and has DNS, DHCP on it.
> Second Win2k8 RC1 is a member server (will be an Exchange box
> afterwards).
>
> At first the network adapter on both was the physical one. That was
> before I installed DHCP and everything worked fine. The 2nd server was
> able to join the domain without problems. Now I installed DHCP on the
> DC and I want to have a "separate" network of some sorts.
>
> DC, DHCP, DNS server IP is 192.168.1.130, default gateway 192.168.1.1
> The 2nd server if both NIC's are on the physical adapter gets the IP
> from my router, not the DHCP (the IP of the DC is listed under Scope
> Option as the router) server I installed on the DC.
>
> If I put both NIC's on local only, then the 2nd server gets the IP
> from the DC DHCP...but I'm unable to browse the internet on both
> machines.
>
> I just want to get both machines online and I have no idea how to do
> that, except by going back one step and configuring both NIC's as
> physical ones of the host, but then the 2nd server gets the IP from my
> router and not the DHCP on the DC.
>
> I'd appreciate any and all suggestions. Have I done something wrong
> when configuring DNS (DNS IP's of my ISP are in the forwarders)?
>
> Please let me know if further details, information is needed for
> resolving this.

> On Dec 8, 11:22 pm, "Bill Grant" <not.available@online> wrote:
>> That is pretty much what should happen. Setting up a domain is a
>> non-trivial operation, whether you are using physical or virtual
>> machines.
>>
>> If you want to use DHCP, you really need your domain machines to be
>> in
>> their own network, not linked to the host's physical network. And they
>> need
>> to be in their own IP subnet. With VPC the best idea is to put them in
>> local
>> only. The AD clients will get their network config from DHCP on the DC
>> and
>> Active Directory will all work.
>>
>> Internet access is another matter altogether. To do that you need a
>> machine which can act as a router between the virtual network and the
>> physical network. You can use a virtual machine with tw NICs, one linked
>> to
>> the virtual network and one to the physical network (through the host
>> machines's NIC). I would not recommend using either a DC or an Exchange
>> server for this. You could use Win2k/2k3 with RRAS or a Linux vm running
>> as
>> a NAT router.
>>
>> There is still the problem of DNS. Since the AD machines all use the
>> local DNS (so that they can see the SRV records) they cannot resolve
>> foreign
>> URLs. You need to set up the local DNS to forward to a public DNS (or a
>> DNS
>> server on your physical LAN which can resolve them). This is not because
>> you
>> are using virtual machines. You need to do the same with real machines on
>> real networks.
>>
>
> Thank you very much for your reply.
>
> As you probably noticed I don't have a wealth of experience in these
> matters. I'll consider using a new VM with two NIC's so I can get
> internet access. As for DNS isn't it enough to set up the DNS IP's of
> my ISP in the forwarders?
> Is this process any easier in the Virtual Server. I'd also appreciate
> any and all URLs so I can better understand the problems I'm facing.