ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual PC

Recent Virtual PC posts

* Virtual Box
* What is the maximum Virtual Had Disk size for VPC 2007?
* is Guest OS possible access Host OS File system?
* over compensated
* Setup Virtual PC 2007
* VPC 2007 single-threaded?
* Disk performance comparing different options?
* Shrink .vhd when using differencing disks?
* Internet in the Vpc
* Ram
* Can I get info on real, physical hardware ?
* windows image files .wim
* How to play XG midi files on your Vista machine using Virtual PC
* ipv4 address: duplicate, how to fix it
* How to set up 3 NICs on VPC?
* noobie questions on vpc
* No desktop or start menu
* Windows XP virtual pc hard drive fails to commit changes
* Is VPC 2007 use port number?
* This sounds cool

Add Solution

Creating a virtual domain lab for study purpose

Source: microsoft.public.virtualpc
Sent: 12/06/2008
From: Itfitz
Message:

Hello I am studying for the MCSA Cert. and would like to create a virtual
domain lab to complete the projects in the course material. I have tried
creating multiple Server 2003 vhd's and a XP Pro vhd. No problem there. I
made one Server the domain controller. Know the problem is that I can't get
any of the other Virt's to become members of the domain. Do I have to actualy
be a member of a domain for this to work or can I use a fake domain?
Any help in this process would be greatly appreciated.
Thank you.

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Creating a virtual domain lab for study purpose

Sent: 12/07/2008
From: Bo Berglund <(email address - cut out)>
Message:

On Sat, 6 Dec 2008 22:16:00 -0800, Itfitz
<(email address - cut out)> wrote:

Can the virtual machines communicate with each other via the network?

How did you set up the networking for the machines?

A typical scenario for this kind of system is something like this:
------------------------------------------------------------------
All virtual machines in the domain have their NIC:s set to "Local
Only" in the VPC2007 settings for each machine. This isolates the test
domain from your host system network.

One virtual machine will act as the Internet router for the domain and
will have an extra NIC in the VPC2007 settings. This will be set to
the NIC of the host system. Not needed if you are not going to let the
virtual domain access the Internet.

All virtual machines except the domain controller and the router will
have their networking set to "automatic" (inside the respective
operating systems).

The domain controller and the router will have fixed IP addresses in
the same subnet.

The router's extra NIC will have DHCP set so it will also get a
physical IP from your outside network on this NIC and can then be used
to connect to the Internet.

All virtual machines except the router will have their default
gateways set to point to the router.

You need to install DHCP and DNC server roles on the domain controller
and configure them to use the router for Internet access and DNC and
to serve out local IP addresses in the local subnet.

Now the domain controller will handle the other domain members
concerning networking.

--

Bo Berglund (Sweden)

Show quoted text

>Hello I am studying for the MCSA Cert. and would like to create a virtual
>domain lab to complete the projects in the course material. I have tried
>creating multiple Server 2003 vhd's and a XP Pro vhd. No problem there. I
>made one Server the domain controller. Know the problem is that I can't get
>any of the other Virt's to become members of the domain. Do I have to actualy
>be a member of a domain for this to work or can I use a fake domain?
>Any help in this process would be greatly appreciated.
>Thank you.

Re: Creating a virtual domain lab for study purpose

Sent: 12/07/2008
From: Itfitz
Message:

Thank you for the reponse.
I set them all to Local Only.

I have a few questions though. If I set all of the comps to automatic, how
do I set there default gateway towards the router? Also does the router and
the Domain Controller have to be seperate machines?
Thanks again

"Bo Berglund" wrote:

Show quoted text

> On Sat, 6 Dec 2008 22:16:00 -0800, Itfitz
> <(email address - cut out)> wrote:
>
> >Hello I am studying for the MCSA Cert. and would like to create a virtual
> >domain lab to complete the projects in the course material. I have tried
> >creating multiple Server 2003 vhd's and a XP Pro vhd. No problem there. I
> >made one Server the domain controller. Know the problem is that I can't get
> >any of the other Virt's to become members of the domain. Do I have to actualy
> >be a member of a domain for this to work or can I use a fake domain?
> >Any help in this process would be greatly appreciated.
> >Thank you.
>
> Can the virtual machines communicate with each other via the network?
>
> How did you set up the networking for the machines?
>
>
> A typical scenario for this kind of system is something like this:
> ------------------------------------------------------------------
> All virtual machines in the domain have their NIC:s set to "Local
> Only" in the VPC2007 settings for each machine. This isolates the test
> domain from your host system network.
>
> One virtual machine will act as the Internet router for the domain and
> will have an extra NIC in the VPC2007 settings. This will be set to
> the NIC of the host system. Not needed if you are not going to let the
> virtual domain access the Internet.
>
> All virtual machines except the domain controller and the router will
> have their networking set to "automatic" (inside the respective
> operating systems).
>
> The domain controller and the router will have fixed IP addresses in
> the same subnet.
>
> The router's extra NIC will have DHCP set so it will also get a
> physical IP from your outside network on this NIC and can then be used
> to connect to the Internet.
>
> All virtual machines except the router will have their default
> gateways set to point to the router.
>
> You need to install DHCP and DNC server roles on the domain controller
> and configure them to use the router for Internet access and DNC and
> to serve out local IP addresses in the local subnet.
>
> Now the domain controller will handle the other domain members
> concerning networking.
>
> --
>
> Bo Berglund (Sweden)
>

Re: Creating a virtual domain lab for study purpose

Sent: 12/07/2008
From: "Steve Jain [MVP]" <(email address - cut out)>
Message:

On Sun, 7 Dec 2008 14:32:03 -0800, Itfitz
<(email address - cut out)> wrote:

Local only is just that, there is no connection to the outside
network. All the VMs are completely isolated.

You may be able to get around this by adding a 2nd virtual NIC to the
VM acting as the router and have 1 interface local only and the other
set to host's NIC.

If your VMs are getting their tcp.ip info from a DHCP server, it will
be able to provide the gateway information also. In this case the
gateway would be the VM acting as the router (i.e. the one that has
the 2 NICs)

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/

Show quoted text

>Thank you for the reponse.
>I set them all to Local Only.
>
>I have a few questions though. If I set all of the comps to automatic, how
>do I set there default gateway towards the router? Also does the router and
>the Domain Controller have to be seperate machines?
>Thanks again
>

Re: Creating a virtual domain lab for study purpose

Sent: 12/07/2008
From: Itfitz
Message:

I must have something set wrong.
I have all three machines set to local only.
I can ping each machine every which way.
I still cannot get the other two machines to join the domain

"Steve Jain [MVP]" wrote:

Show quoted text

> On Sun, 7 Dec 2008 14:32:03 -0800, Itfitz
> <(email address - cut out)> wrote:
>
> >Thank you for the reponse.
> >I set them all to Local Only.
> >
> >I have a few questions though. If I set all of the comps to automatic, how
> >do I set there default gateway towards the router? Also does the router and
> >the Domain Controller have to be seperate machines?
> >Thanks again
> >
>
> Local only is just that, there is no connection to the outside
> network. All the VMs are completely isolated.
>
> You may be able to get around this by adding a 2nd virtual NIC to the
> VM acting as the router and have 1 interface local only and the other
> set to host's NIC.
>
> If your VMs are getting their tcp.ip info from a DHCP server, it will
> be able to provide the gateway information also. In this case the
> gateway would be the VM acting as the router (i.e. the one that has
> the 2 NICs)
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
>

Re: Creating a virtual domain lab for study purpose

Sent: 12/08/2008
From: Itfitz
Message:

I found the problem I didn't give the users admin rights
Now the next step is to get the router configured to let internet access in
to all on the network.
If you have hints for this please feel free to respond.
Thanks for everyones help so far.

"Bill Grant" wrote:

Show quoted text

>
>
> "Itfitz" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > I must have something set wrong.
> > I have all three machines set to local only.
> > I can ping each machine every which way.
> > I still cannot get the other two machines to join the domain
> >
> >>
>
> This really has very little to do with virtualization. It is about how
> Active Directory works.
>
> First up, forget about default gateways and Internet access. That has
> nothing to do with joining a domain. What matters is DNS. Set the client
> machines to use the LAN IP of the DC for DNS.
>
> Check that this is working by doing an nslookup from a client for the
> domain name. (eg nslookup mydomain.com). If that works, join the client to
> the domain.
>
> After you have your domain working you can think about giving it Internet
> access. The easiest way to do it is to configure a vm as a NAT router
> between the Local Only network and the physical network. The domain machines
> would then use the NAT router's local IP as default gateway but must still
> use the local DNS. You modify the local DNS to forward to a public DNS
> server to resolve "foreign" URLs (just as you would for a local LAN running
> AD behind a NAT router on a physical network).
>
>
>
>

Re: Creating a virtual domain lab for study purpose

Sent: 12/08/2008
From: "Bill Grant" <not.available@online>
Message:

"Itfitz" <(email address - cut out)> wrote in message
news:(email address - cut out)...

This really has very little to do with virtualization. It is about how
Active Directory works.

First up, forget about default gateways and Internet access. That has
nothing to do with joining a domain. What matters is DNS. Set the client
machines to use the LAN IP of the DC for DNS.

Check that this is working by doing an nslookup from a client for the
domain name. (eg nslookup mydomain.com). If that works, join the client to
the domain.

After you have your domain working you can think about giving it Internet
access. The easiest way to do it is to configure a vm as a NAT router
between the Local Only network and the physical network. The domain machines
would then use the NAT router's local IP as default gateway but must still
use the local DNS. You modify the local DNS to forward to a public DNS
server to resolve "foreign" URLs (just as you would for a local LAN running
AD behind a NAT router on a physical network).

Show quoted text

> I must have something set wrong.
> I have all three machines set to local only.
> I can ping each machine every which way.
> I still cannot get the other two machines to join the domain
>
>>

Re: Creating a virtual domain lab for study purpose

Sent: 12/08/2008
From: Itfitz
Message:

When joining the other computers to the domain I had to use an admin to sign
in. once I used admin credentials it let me join the domain right away.
The problem I am facing now is using the 2nd server as the router. I have a
Netgear storage unit and I keep losing it when I try to link the wireless nic
with the outside network.
I use the wireless nic to connect to the router and the 10/100 to connect to
the storage unit.
This realy isn't a problem though because to do my training I don't realy
need internet access with the lab. From here i should be able to complete my
courses.
Thank you for all your help in these matters.
feel free to give me any more advice you feel may help me better prapair for
the MCSA exam

"Bill Grant" wrote:

Show quoted text

> What admin rights did you give the users? Why?
>
>
> "Itfitz" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > I found the problem I didn't give the users admin rights
> > Now the next step is to get the router configured to let internet access
> > in
> > to all on the network.
> > If you have hints for this please feel free to respond.
> > Thanks for everyones help so far.
> >
> > "Bill Grant" wrote:
> >
> >>
> >>
> >> "Itfitz" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> > I must have something set wrong.
> >> > I have all three machines set to local only.
> >> > I can ping each machine every which way.
> >> > I still cannot get the other two machines to join the domain
> >> >
> >> >>
> >>
> >> This really has very little to do with virtualization. It is about how
> >> Active Directory works.
> >>
> >> First up, forget about default gateways and Internet access. That has
> >> nothing to do with joining a domain. What matters is DNS. Set the client
> >> machines to use the LAN IP of the DC for DNS.
> >>
> >> Check that this is working by doing an nslookup from a client for the
> >> domain name. (eg nslookup mydomain.com). If that works, join the client
> >> to
> >> the domain.
> >>
> >> After you have your domain working you can think about giving it
> >> Internet
> >> access. The easiest way to do it is to configure a vm as a NAT router
> >> between the Local Only network and the physical network. The domain
> >> machines
> >> would then use the NAT router's local IP as default gateway but must
> >> still
> >> use the local DNS. You modify the local DNS to forward to a public DNS
> >> server to resolve "foreign" URLs (just as you would for a local LAN
> >> running
> >> AD behind a NAT router on a physical network).
> >>
> >>
> >>
> >>
>

Re: Creating a virtual domain lab for study purpose

Sent: 12/09/2008
From: "Bill Grant" <not.available@online>
Message:

What admin rights did you give the users? Why?

"Itfitz" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> I found the problem I didn't give the users admin rights
> Now the next step is to get the router configured to let internet access
> in
> to all on the network.
> If you have hints for this please feel free to respond.
> Thanks for everyones help so far.
>
> "Bill Grant" wrote:
>
>>
>>
>> "Itfitz" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > I must have something set wrong.
>> > I have all three machines set to local only.
>> > I can ping each machine every which way.
>> > I still cannot get the other two machines to join the domain
>> >
>> >>
>>
>> This really has very little to do with virtualization. It is about how
>> Active Directory works.
>>
>> First up, forget about default gateways and Internet access. That has
>> nothing to do with joining a domain. What matters is DNS. Set the client
>> machines to use the LAN IP of the DC for DNS.
>>
>> Check that this is working by doing an nslookup from a client for the
>> domain name. (eg nslookup mydomain.com). If that works, join the client
>> to
>> the domain.
>>
>> After you have your domain working you can think about giving it
>> Internet
>> access. The easiest way to do it is to configure a vm as a NAT router
>> between the Local Only network and the physical network. The domain
>> machines
>> would then use the NAT router's local IP as default gateway but must
>> still
>> use the local DNS. You modify the local DNS to forward to a public DNS
>> server to resolve "foreign" URLs (just as you would for a local LAN
>> running
>> AD behind a NAT router on a physical network).
>>
>>
>>
>>

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: