Vista Forums - View Single Post - Can't join Virtual Vista to a Virtual 2008 Domain Server

07-16-2008

"Steve Jain" <noreply.-@-.essjae.com> wrote in message
news:f53t749edjgljnmlvm06vvqkaes144geka@xxxxxx

Quote:

> On Wed, 16 Jul 2008 16:36:04 -0700, Golden Z
> <GoldenZ@xxxxxx> wrote:
>

Quote:

>>I have done some more testing. The Virtual Vista/XP machines can ping
>>each
>>other and can ping the HOSTNAME but not the IP address.
>>
>>The server is not set up as the DHCP server. DHCP is handled by the
>>router.
>>
>>What do i need to configure in the network settings on the VirtualXP and
>>Vista machines?
>>
>>Firewall settings? Iam unsure what to check? The VirtualXP, the
>>VirtualServer, or the HostPC of the virtual environment.
>>
>>What are you using for the network settings, Shared Networking (NAT)?
>>How can i Tell the difference?
>>
>>These virtualVista and XP are brand new with nothing on them.
>>

>
> The first thing I'd do is give your server a static IP address.
> Generally, it's not a good idea to have your domain controller using a
> dynamic IP.
>
> the default should be the host's NIC, you can check under the Network
> settings of each VM.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
> I do not work for Microsoft.

I would have to agree with Steve. The troubles you are having really
have nothing to do with virtualization, but simply with network design.

If you want to run a domain setup you cannot use DHCP from a router. You
also cannot use the built-in DNS forwarding. You need to set up your domain
in its own network with its own IP subnet, with all client machines using
the local DC for DNS. This applies to both hard metal and virtual machines
and to physical or virtual networks.

The simplest way to do it with VPC is to put all the virtual machines in
Local Only. Give the DC a static IP in a new IP subnet. If you want to run
DHCP, set it up on the DC and enable it in AD. (This will have no affect on
the other machines in the LAN. It only affects the machine in Local Only).
Otherwise configure the client machines manually.

When you have your domain running successfully you can give this network
Internet access by configuring a vm to act as a NAT router between the
virtual network and the physical network. You configure the local DNS to
forward to a public DNS service to resolve foreign URLs as well as the local
domain machines and AD SRV records.

There are really no shortcuts. You need to do it properly if you want
your domain to work.

07-16-2008	#5 (permalink)
Bill Grant n/a posts	Re: Can't join Virtual Vista to a Virtual 2008 Domain Server "Steve Jain" <noreply.-@-.essjae.com> wrote in message news:f53t749edjgljnmlvm06vvqkaes144geka@xxxxxx Quote: > On Wed, 16 Jul 2008 16:36:04 -0700, Golden Z > <GoldenZ@xxxxxx> wrote: > Quote: >>I have done some more testing. The Virtual Vista/XP machines can ping >>each >>other and can ping the HOSTNAME but not the IP address. >> >>The server is not set up as the DHCP server. DHCP is handled by the >>router. >> >>What do i need to configure in the network settings on the VirtualXP and >>Vista machines? >> >>Firewall settings? Iam unsure what to check? The VirtualXP, the >>VirtualServer, or the HostPC of the virtual environment. >> >>What are you using for the network settings, Shared Networking (NAT)? >>How can i Tell the difference? >> >>These virtualVista and XP are brand new with nothing on them. >> > > The first thing I'd do is give your server a static IP address. > Generally, it's not a good idea to have your domain controller using a > dynamic IP. > > the default should be the host's NIC, you can check under the Network > settings of each VM. > > -- > Cheers, > Steve Jain, Virtual Machine MVP > http://vpc.essjae.com/ > I do not work for Microsoft. I would have to agree with Steve. The troubles you are having really have nothing to do with virtualization, but simply with network design. If you want to run a domain setup you cannot use DHCP from a router. You also cannot use the built-in DNS forwarding. You need to set up your domain in its own network with its own IP subnet, with all client machines using the local DC for DNS. This applies to both hard metal and virtual machines and to physical or virtual networks. The simplest way to do it with VPC is to put all the virtual machines in Local Only. Give the DC a static IP in a new IP subnet. If you want to run DHCP, set it up on the DC and enable it in AD. (This will have no affect on the other machines in the LAN. It only affects the machine in Local Only). Otherwise configure the client machines manually. When you have your domain running successfully you can give this network Internet access by configuring a vm to act as a NAT router between the virtual network and the physical network. You configure the local DNS to forward to a public DNS service to resolve foreign URLs as well as the local domain machines and AD SRV records. There are really no shortcuts. You need to do it properly if you want your domain to work.
My System Specs