> i need to create a domain environment on my laptop for presentations.
>
> i have win2000 server on my laptop (tried 2003 also), VPC 2004 (I think I
> installed SP1 version) and 1 XP Pro VM - laptop has a built in nic, as well
> as a wireless nic. I know win 2000 & 2003 server arent supported, but they
> both seem to work so far. I am not sure I like adding the "XP host to a
> virtual DC (guest)" scenario as some other posts suggest, but I suppose I
> could deal with that if I really had to.
>
> the server is 192.168.1.252 but i dont know what to set the gateway to (i
> have a router at 192.168.0.1). I would like to have the host have internet
> access, but guest access is not important right now.
>
> i have dhcp set up on the server/laptop with a scope of 192.168.1.200 -
> 192.168.1.249. I have a loopback adapter also (been trying lots of different
> config): loopback = 192.168.1.254.
>
> I have tried setting the VM network setting to both the built in nic and the
> loopback and setting the IP to 192.168.1.200 and the gateway on the VM
> accordingly (either .252 for built in or .254 for loopback adapter). Neither
> has allowed the guest to see the host and I tried a static address because it
> cannot locate the dhcp server.
>
> I want to be able to unplug my laptop from my LAN and have it run as a
> standalone domain.
>
> How do i set up the gateway for the server (host)?
> Do I need the loopback adapter?
> What would the settings be for the guest (loopback vs built in). The
> software I am demo'ing uses dns aliasing to access the server/host so I am
> pretty sure I need to set up the guest dns server to the host ip address.
> Do I need to set up RAS for routing on the server?
>
> Any help would be appreciated.
>

>i need to create a domain environment on my laptop for presentations.
>
> i have win2000 server on my laptop (tried 2003 also), VPC 2004 (I think I
> installed SP1 version) and 1 XP Pro VM - laptop has a built in nic, as
> well
> as a wireless nic. I know win 2000 & 2003 server arent supported, but
> they
> both seem to work so far. I am not sure I like adding the "XP host to a
> virtual DC (guest)" scenario as some other posts suggest, but I suppose I
> could deal with that if I really had to.
>
> the server is 192.168.1.252 but i dont know what to set the gateway to (i
> have a router at 192.168.0.1). I would like to have the host have internet
> access, but guest access is not important right now.
>
> i have dhcp set up on the server/laptop with a scope of 192.168.1.200 -
> 192.168.1.249. I have a loopback adapter also (been trying lots of
> different
> config): loopback = 192.168.1.254.
>
> I have tried setting the VM network setting to both the built in nic and
> the
> loopback and setting the IP to 192.168.1.200 and the gateway on the VM
> accordingly (either .252 for built in or .254 for loopback adapter).
> Neither
> has allowed the guest to see the host and I tried a static address because
> it
> cannot locate the dhcp server.
>
> I want to be able to unplug my laptop from my LAN and have it run as a
> standalone domain.
>
> How do i set up the gateway for the server (host)?
> Do I need the loopback adapter?
> What would the settings be for the guest (loopback vs built in). The
> software I am demo'ing uses dns aliasing to access the server/host so I am
> pretty sure I need to set up the guest dns server to the host ip address.
> Do I need to set up RAS for routing on the server?
>
> Any help would be appreciated.
>

> Active Directory is not really compatible with NAT. NAT sets up the NAT
> router as a proxy for DNS requests to the public DNS server on the "public"
> network. Active Directory must use the local DNS server, because that is
> where the SRV records for AD are registered.
>
> The domain controller must be configured to use the local DNS service
> (usually running on the same machine). dcpromo will set this up for you if
> it doesn't exist. AD clients must use this local DNS as well to access AD
> resources, such as netlogon. If you want DNS to handle "foreign" names, you
> set up forwarding on the local DNS to refer these requests to a public DNS
> service.
>
> So for the VM guest to be an AD client and have Internet access throughy
> the AD server on the host, it would need to have the server set as its
> default gateway and DNS server. The server would need to be configured as a
> router between the two subnets, and its DNS server would need to be
> configured to forward DNS requests. If it is not configured to do NAT, you
> may also need extra routing on your Internet router at 192.168.0.1 (because
> it will not be aware of the extra 192.168.1.0 subnet) .
>
> On the server, the NIC is in the 192.168.0.x subnet with its default
> gateway set to 192.168.0.1 . This is its connection to the local LAN and to
> the Internet via your router. The loopback adapter is set to a 192.168.1.x
> IP address and its default gateway is blank. This is its link to the virtual
> network.
>
> On the guest, the NIC is set to the loopback adapter option and it has
> an address in the 192.168.1 subnet, with gateway and DNS set to the IP
> address of the loopback adapter on the host. Even if the host is not
> connected to the local network, the guest machine can see the domain
> controller through the loopback address, and can log in to the domain.
>
> "Jimbo" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> >i need to create a domain environment on my laptop for presentations.
> >
> > i have win2000 server on my laptop (tried 2003 also), VPC 2004 (I think I
> > installed SP1 version) and 1 XP Pro VM - laptop has a built in nic, as
> > well
> > as a wireless nic. I know win 2000 & 2003 server arent supported, but
> > they
> > both seem to work so far. I am not sure I like adding the "XP host to a
> > virtual DC (guest)" scenario as some other posts suggest, but I suppose I
> > could deal with that if I really had to.
> >
> > the server is 192.168.1.252 but i dont know what to set the gateway to (i
> > have a router at 192.168.0.1). I would like to have the host have internet
> > access, but guest access is not important right now.
> >
> > i have dhcp set up on the server/laptop with a scope of 192.168.1.200 -
> > 192.168.1.249. I have a loopback adapter also (been trying lots of
> > different
> > config): loopback = 192.168.1.254.
> >
> > I have tried setting the VM network setting to both the built in nic and
> > the
> > loopback and setting the IP to 192.168.1.200 and the gateway on the VM
> > accordingly (either .252 for built in or .254 for loopback adapter).
> > Neither
> > has allowed the guest to see the host and I tried a static address because
> > it
> > cannot locate the dhcp server.
> >
> > I want to be able to unplug my laptop from my LAN and have it run as a
> > standalone domain.
> >
> > How do i set up the gateway for the server (host)?
> > Do I need the loopback adapter?
> > What would the settings be for the guest (loopback vs built in). The
> > software I am demo'ing uses dns aliasing to access the server/host so I am
> > pretty sure I need to set up the guest dns server to the host ip address.
> > Do I need to set up RAS for routing on the server?
> >
> > Any help would be appreciated.
> >
>
>
>

>i got it working pretty good by using the loopback adapter (even tho I made
>1
> mistake by assigning a default gateway to it, which I just removed), and i
> set up 2 dhcp scopes - 1 scope for the 192.168.0 subnet (just in case i
> ever
> attach a <real> computer) and 192.168.1 subnet.
>
> As i was re-reading thru Bill's response for the third time, i decided to
> set up a 2nd VM (copied the first vhd which used dhcp). My first guest VM
> uses the loopback adapter and I could have sworn that the 2nd one did
> also.
>
> Then I was setting up the dns server on both guests. I tried both the
> loopback adapter (192.168.1.253) address as well as the ip address of the
> host (192.168.0.252) and both seemed to work on both VMs - I could ping
> everything I wanted to - but I noticed on my 2nd VM I could ping the
> router -
> then I noticed this 2nd VM got an address from the 1st scope (192.168.0)
> which explained why I could see the router - I found this 2nd VM was set
> up
> using the real built in nic and not the loopback adapter.
>
> I played heck trying to get it to work with the real nic before I set up a
> loopback adapter and now I wonder if I need the loopback adapter at all. I
> have it really close to the way I wanted it: internet access on the guest
> was
> not really needed and everything else works.
>
> Now I would like to have the guests connect to the internet mostly so I
> can
> activate the xp images but I wont be accessing the internet for any
> tests/presentations.
>
> Re: VM at 192.168.1.201: if I can ping 192.168.0.252 (the host), why cant
> it
> ping the router at 192.168.0.1.
> Re: VM at 192.168.0.200: if I can ping the router, why can't I ping
> yahoo.com?
>
> I set up forwarders to 67.21.13.2 , 67.21.13.4 from 192.168.0.252. and
> still no internet access.
>
> "Bill Grant" wrote:
>
>> Active Directory is not really compatible with NAT. NAT sets up the
>> NAT
>> router as a proxy for DNS requests to the public DNS server on the
>> "public"
>> network. Active Directory must use the local DNS server, because that is
>> where the SRV records for AD are registered.
>>
>> The domain controller must be configured to use the local DNS
>> service
>> (usually running on the same machine). dcpromo will set this up for you
>> if
>> it doesn't exist. AD clients must use this local DNS as well to access
>> AD
>> resources, such as netlogon. If you want DNS to handle "foreign" names,
>> you
>> set up forwarding on the local DNS to refer these requests to a public
>> DNS
>> service.
>>
>> So for the VM guest to be an AD client and have Internet access
>> throughy
>> the AD server on the host, it would need to have the server set as its
>> default gateway and DNS server. The server would need to be configured as
>> a
>> router between the two subnets, and its DNS server would need to be
>> configured to forward DNS requests. If it is not configured to do NAT,
>> you
>> may also need extra routing on your Internet router at 192.168.0.1
>> (because
>> it will not be aware of the extra 192.168.1.0 subnet) .
>>
>> On the server, the NIC is in the 192.168.0.x subnet with its default
>> gateway set to 192.168.0.1 . This is its connection to the local LAN and
>> to
>> the Internet via your router. The loopback adapter is set to a
>> 192.168.1.x
>> IP address and its default gateway is blank. This is its link to the
>> virtual
>> network.
>>
>> On the guest, the NIC is set to the loopback adapter option and it
>> has
>> an address in the 192.168.1 subnet, with gateway and DNS set to the IP
>> address of the loopback adapter on the host. Even if the host is not
>> connected to the local network, the guest machine can see the domain
>> controller through the loopback address, and can log in to the domain.
>>
>> "Jimbo" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> >i need to create a domain environment on my laptop for presentations.
>> >
>> > i have win2000 server on my laptop (tried 2003 also), VPC 2004 (I think
>> > I
>> > installed SP1 version) and 1 XP Pro VM - laptop has a built in nic, as
>> > well
>> > as a wireless nic. I know win 2000 & 2003 server arent supported, but
>> > they
>> > both seem to work so far. I am not sure I like adding the "XP host to a
>> > virtual DC (guest)" scenario as some other posts suggest, but I suppose
>> > I
>> > could deal with that if I really had to.
>> >
>> > the server is 192.168.1.252 but i dont know what to set the gateway to
>> > (i
>> > have a router at 192.168.0.1). I would like to have the host have
>> > internet
>> > access, but guest access is not important right now.
>> >
>> > i have dhcp set up on the server/laptop with a scope of 192.168.1.200 -
>> > 192.168.1.249. I have a loopback adapter also (been trying lots of
>> > different
>> > config): loopback = 192.168.1.254.
>> >
>> > I have tried setting the VM network setting to both the built in nic
>> > and
>> > the
>> > loopback and setting the IP to 192.168.1.200 and the gateway on the VM
>> > accordingly (either .252 for built in or .254 for loopback adapter).
>> > Neither
>> > has allowed the guest to see the host and I tried a static address
>> > because
>> > it
>> > cannot locate the dhcp server.
>> >
>> > I want to be able to unplug my laptop from my LAN and have it run as a
>> > standalone domain.
>> >
>> > How do i set up the gateway for the server (host)?
>> > Do I need the loopback adapter?
>> > What would the settings be for the guest (loopback vs built in). The
>> > software I am demo'ing uses dns aliasing to access the server/host so I
>> > am
>> > pretty sure I need to set up the guest dns server to the host ip
>> > address.
>> > Do I need to set up RAS for routing on the server?
>> >
>> > Any help would be appreciated.
>> >
>>
>>
>>

> 1. You can ping the host from the VM with 192.168.1.201 because they
> are in the same IP subnet. (ie they are directly connected through the
> loopback adapter). You cannot ping the router at 192.168.0.1 because it
> is in a different IP subnet. You would need to use NAT on the router or
> add an extra route to the router at 192.168.0.1 (so that it knew where the
> 192.168.1 subnet was).
>
> 2. From a VM in 192.168.0 , you can ping the the router at 192.168.0.1
> because it is in the same subnet. You should also be able to ping a "real"
> IP address on the Internet using NAT on that router. Does the client have
> the router at 192.168.0.1 set as its default gateway? Ping by name
> depends on correct DNS setup. What DNS address is set on this machine?
>
> Whether you need the loopback adapter or not depends on how you want
> everything to run. If you are happy to have the VMs in the same IP subnet
> as the host, you do not need it. If you want them to be in their own
> subnet, you need the loopback adapter on the host as the link between
> virtual network and the real network. And you need routing set up between
> the two subnets.
>
> "Jimbo" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>>i got it working pretty good by using the loopback adapter (even tho I
>>made 1
>> mistake by assigning a default gateway to it, which I just removed), and
>> i
>> set up 2 dhcp scopes - 1 scope for the 192.168.0 subnet (just in case i
>> ever
>> attach a <real> computer) and 192.168.1 subnet.
>>
>> As i was re-reading thru Bill's response for the third time, i decided to
>> set up a 2nd VM (copied the first vhd which used dhcp). My first guest VM
>> uses the loopback adapter and I could have sworn that the 2nd one did
>> also.
>>
>> Then I was setting up the dns server on both guests. I tried both the
>> loopback adapter (192.168.1.253) address as well as the ip address of the
>> host (192.168.0.252) and both seemed to work on both VMs - I could ping
>> everything I wanted to - but I noticed on my 2nd VM I could ping the
>> router -
>> then I noticed this 2nd VM got an address from the 1st scope (192.168.0)
>> which explained why I could see the router - I found this 2nd VM was set
>> up
>> using the real built in nic and not the loopback adapter.
>>
>> I played heck trying to get it to work with the real nic before I set up
>> a
>> loopback adapter and now I wonder if I need the loopback adapter at all.
>> I
>> have it really close to the way I wanted it: internet access on the guest
>> was
>> not really needed and everything else works.
>>
>> Now I would like to have the guests connect to the internet mostly so I
>> can
>> activate the xp images but I wont be accessing the internet for any
>> tests/presentations.
>>
>> Re: VM at 192.168.1.201: if I can ping 192.168.0.252 (the host), why cant
>> it
>> ping the router at 192.168.0.1.
>> Re: VM at 192.168.0.200: if I can ping the router, why can't I ping
>> yahoo.com?
>>
>> I set up forwarders to 67.21.13.2 , 67.21.13.4 from 192.168.0.252. and
>> still no internet access.
>>
>> "Bill Grant" wrote:
>>
>>> Active Directory is not really compatible with NAT. NAT sets up the
>>> NAT
>>> router as a proxy for DNS requests to the public DNS server on the
>>> "public"
>>> network. Active Directory must use the local DNS server, because that is
>>> where the SRV records for AD are registered.
>>>
>>> The domain controller must be configured to use the local DNS
>>> service
>>> (usually running on the same machine). dcpromo will set this up for you
>>> if
>>> it doesn't exist. AD clients must use this local DNS as well to access
>>> AD
>>> resources, such as netlogon. If you want DNS to handle "foreign" names,
>>> you
>>> set up forwarding on the local DNS to refer these requests to a public
>>> DNS
>>> service.
>>>
>>> So for the VM guest to be an AD client and have Internet access
>>> throughy
>>> the AD server on the host, it would need to have the server set as its
>>> default gateway and DNS server. The server would need to be configured
>>> as a
>>> router between the two subnets, and its DNS server would need to be
>>> configured to forward DNS requests. If it is not configured to do NAT,
>>> you
>>> may also need extra routing on your Internet router at 192.168.0.1
>>> (because
>>> it will not be aware of the extra 192.168.1.0 subnet) .
>>>
>>> On the server, the NIC is in the 192.168.0.x subnet with its default
>>> gateway set to 192.168.0.1 . This is its connection to the local LAN and
>>> to
>>> the Internet via your router. The loopback adapter is set to a
>>> 192.168.1.x
>>> IP address and its default gateway is blank. This is its link to the
>>> virtual
>>> network.
>>>
>>> On the guest, the NIC is set to the loopback adapter option and it
>>> has
>>> an address in the 192.168.1 subnet, with gateway and DNS set to the IP
>>> address of the loopback adapter on the host. Even if the host is not
>>> connected to the local network, the guest machine can see the domain
>>> controller through the loopback address, and can log in to the domain.
>>>
>>> "Jimbo" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>> >i need to create a domain environment on my laptop for presentations.
>>> >
>>> > i have win2000 server on my laptop (tried 2003 also), VPC 2004 (I
>>> > think I
>>> > installed SP1 version) and 1 XP Pro VM - laptop has a built in nic, as
>>> > well
>>> > as a wireless nic. I know win 2000 & 2003 server arent supported, but
>>> > they
>>> > both seem to work so far. I am not sure I like adding the "XP host to
>>> > a
>>> > virtual DC (guest)" scenario as some other posts suggest, but I
>>> > suppose I
>>> > could deal with that if I really had to.
>>> >
>>> > the server is 192.168.1.252 but i dont know what to set the gateway to
>>> > (i
>>> > have a router at 192.168.0.1). I would like to have the host have
>>> > internet
>>> > access, but guest access is not important right now.
>>> >
>>> > i have dhcp set up on the server/laptop with a scope of
>>> > 192.168.1.200 -
>>> > 192.168.1.249. I have a loopback adapter also (been trying lots of
>>> > different
>>> > config): loopback = 192.168.1.254.
>>> >
>>> > I have tried setting the VM network setting to both the built in nic
>>> > and
>>> > the
>>> > loopback and setting the IP to 192.168.1.200 and the gateway on the VM
>>> > accordingly (either .252 for built in or .254 for loopback adapter).
>>> > Neither
>>> > has allowed the guest to see the host and I tried a static address
>>> > because
>>> > it
>>> > cannot locate the dhcp server.
>>> >
>>> > I want to be able to unplug my laptop from my LAN and have it run as a
>>> > standalone domain.
>>> >
>>> > How do i set up the gateway for the server (host)?
>>> > Do I need the loopback adapter?
>>> > What would the settings be for the guest (loopback vs built in). The
>>> > software I am demo'ing uses dns aliasing to access the server/host so
>>> > I am
>>> > pretty sure I need to set up the guest dns server to the host ip
>>> > address.
>>> > Do I need to set up RAS for routing on the server?
>>> >
>>> > Any help would be appreciated.
>>> >
>>>
>>>
>>>
>
>