> Hello jcwi65,
>
> I have been playing around with various virtual network setups using
> Virtual PC 2004, 2007 and Hyper-V. With 2007, you are correct in assuming
> to use NAT for the gateway and static addresses for the servers. Let us
> assume that your live network si using the 192.168.10.0/24 addressing
> scheme. We will assign the 10.10.1.0/20 for the virtual network.
>
> The gateway should have two adapters, one bound to your physical adapter
> (and you can use DHCP for this address if you wish, although we will give
> it a static one for this demonstration), and one adapter bound to the
> "Local Only" option in VPC2007. All other VMs in the environment will use
> the "Local Only" option. I have attached a diagram of a potential layout
> of your network.
>
> Static IPs are the way to go for your servers (gateway and DC). If you
> really want to run DHCP from your gateway, be sure it is configured to
> only service clients on its virtual side, and that all pertinent
> information is correct (gateway information for the scope options should
> point to its internal IP, DNS should point to the DC). Keep in mind that
> DHCP could also run from your DC. This will guarantee that the DHCP
> broadcasts will stay in the virtual environment. Just a thought.
>
> As far as DNS, the DC should point to itself. As far as the gateway, the
> internal IP needs no DNS configuration. The external one will need to be
> configured in a way to get to the Internet (probably your ADSL/Cable
> modem, or other Internet connection). When you configure DNS on the DC,
> put the address of your Internet connection device (router or modem) in
> the DNS forwarders section. That way when any client sends a DNS request
> to your DNS server, and it doesn't have a record for it, it can query the
> router (which will in turn send the request to your ISP, and so on).
>
> No special configs for the clients, other than their network adapters
> being bound to the "Local Only" option.
>
> Check ou the attached diagram for somewhat of a visual.
>
>
> Hope this helps.
>
>
> Paul Yhonquea
>
>
>
> "jcwi65" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>>
>> Currently I am running the latest version of VPC 2007 sp1, I have XP Pro
>> in one VM 2000 in one, and Server 2003 in two others. What I want to do
>> is set one server up with DNS, Active Directory, and eventually RIS and
>> WSUS. The other server I would like to be my gateway to the internet and
>> be a DHCP server for VM clients XP and 2000. the servers should have
>> static IPs. Would I use a NAT for the gateway server and assign my
>> static IPs to both servers? Use the the local network as the 2nd adapter
>> on the gateway and then on each of the VMs? Also on the static servers
>> the DNS address would point back to the DNS server in the virtual
>> network correct? I have tried to get this virtual network setup and
>> cannot get the local network to see the Internet through the one sever.
>> :cry:
>>
>> Any help would be appreciated. Thanks in advance.
>>
>> jcwi65
>>
>>
>> --
>> jcwi65
>>
>
>
>

>
> The diagram did not come through, can you repost it? Your information
> has been very helpful. I have not been able to test it and will be
> doing so momentarily.
>
>
> --
> jcwi65

>
>
> "jcwi65" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>>
>> (email address - cut out)
>>
>>
>> --
>> jcwi65
>
> You need to be careful using NAT with Active Directory. This has nothing
> to do with VPC. It applies as well on "real" machines on "real" networks.
> The way that NAT handles DNS (ie the NAT server acting as a DNS proxy) is
> not compatible with AD.
>
> Put your server in Local Only and give it a static IP in its own IP
> subnet. Use dcpromo to create a domain and let dcpromo set up DNS for you.
> I would also configure DHCP on the DC and authorize it in AD.
>
> Use RRAS in one of your servers (not the DC) as a NAT router to the
> physical network. One NIC connects to the physical network through the
> NIC in the host machine. The other NIC is in Local Only and is the default
> gateway for your private LAN. Do not configure RRAS to do DHCP or DNS
> proxy.
>
> Configure the DHCP scope to give your AD clients the NAT router's
> private IP as their default gateway but the DC as their DNS server.
> Configure your local DNS to forward to a public DNS server (so that it can
> resolve foreign URLs as well as local SRV records).
>
> Here is how my network looked when I ran a domain using VPC.
>
> Internet
> |
> Netgear
> 192.168.0.1
> |
> Local Network (workgroup)
> 192.168.0.x dg 192.168.0.1
> |
> 192.168.0.254 dg 192.168.0.1
> RRAS/NAT
> 192.168.31.254 dg blank
> |
> DC
> 192.168.31.11 dg 192.168.31.254
> |
> AD members
> 192.168.31.x dg 192.168.31.254 dns 192.168.31.11

>
> (email address - cut out)
>
>
> --
> jcwi65

> Bill,
>
> This is pretty much what I was suggesting to jcwi65, but you did lay
> out the
> technical details a bit better. Forgot about the piece dealing with
> authorizing the DHCP server.
>
> Paul Yhonquea
>
>
> "Bill Grant" <not.available@xxxxxx> wrote in message
> news:ezluDggHKHA.3708@xxxxxx> > >
> > >
> > >
> > > "jcwi65" <(email address - cut out)> wrote in message
> > > news:(email address - cut out)...> > > > >
> > > >>
> > > >> jcthompson@xxxxxx
> > > >>
> > > >>
> > > >> --
> > > >> jcwi65> > > >
> > >
> > > You need to be careful using NAT with Active Directory. This has
> > nothing
> > > to do with VPC. It applies as well on "real" machines on "real"
> > networks.
> > > The way that NAT handles DNS (ie the NAT server acting as a DNS
> > proxy) is
> > > not compatible with AD.
> > >
> > > Put your server in Local Only and give it a static IP in its own
> > IP
> > > subnet. Use dcpromo to create a domain and let dcpromo set up DNS
> > for you.
> > > I would also configure DHCP on the DC and authorize it in AD.
> > >
> > > Use RRAS in one of your servers (not the DC) as a NAT router to
> > the
> > > physical network. One NIC connects to the physical network
> > through the
> > > NIC in the host machine. The other NIC is in Local Only and is
> > the default
> > > gateway for your private LAN. Do not configure RRAS to do DHCP or
> > DNS
> > > proxy.
> > >
> > > Configure the DHCP scope to give your AD clients the NAT router's
> > > private IP as their default gateway but the DC as their DNS
> > server.
> > > Configure your local DNS to forward to a public DNS server (so
> > that it can
> > > resolve foreign URLs as well as local SRV records).
> > >
> > > Here is how my network looked when I ran a domain using VPC.
> > >
> > > Internet
> > > |
> > > Netgear
> > > 192.168.0.1
> > > |
> > > Local Network (workgroup)
> > > 192.168.0.x dg 192.168.0.1
> > > |
> > > 192.168.0.254 dg 192.168.0.1
> > > RRAS/NAT
> > > 192.168.31.254 dg blank
> > > |
> > > DC
> > > 192.168.31.11 dg 192.168.31.254
> > > |
> > > AD members
> > > 192.168.31.x dg 192.168.31.254 dns 192.168.31.11 > >

> > Paul Yhonquea;1113555 Wrote:
> > Bill,
> >
> > This is pretty much what I was suggesting to jcwi65, but you did lay
> > out the
> > technical details a bit better. Forgot about the piece dealing with
> > authorizing the DHCP server.
> >
> > Paul Yhonquea
> >
> >
> > "Bill Grant" <not.available@xxxxxx> wrote in message
> > news:ezluDggHKHA.3708@xxxxxx> > > > >
> > > >
> > > >
> > > > "jcwi65" <(email address - cut out)> wrote in message
> > > > news:(email address - cut out)...
> > > >
> > > > You need to be careful using NAT with Active Directory. This has
> > > nothing
> > > > to do with VPC. It applies as well on "real" machines on "real"
> > > networks.
> > > > The way that NAT handles DNS (ie the NAT server acting as a DNS
> > > proxy) is
> > > > not compatible with AD.
> > > >
> > > > Put your server in Local Only and give it a static IP in its own IP
> > > > subnet. Use dcpromo to create a domain and let dcpromo set up DNS for
> > > you.
> > > > I would also configure DHCP on the DC and authorize it in AD.
> > > >
> > > > Use RRAS in one of your servers (not the DC) as a NAT router to the
> > > > physical network. One NIC connects to the physical network through
> > > the
> > > > NIC in the host machine. The other NIC is in Local Only and is the
> > > default
> > > > gateway for your private LAN. Do not configure RRAS to do DHCP or DNS
> > > > proxy.
> > > >
> > > > Configure the DHCP scope to give your AD clients the NAT router's
> > > > private IP as their default gateway but the DC as their DNS server.
> > > > Configure your local DNS to forward to a public DNS server (so that
> > > it can
> > > > resolve foreign URLs as well as local SRV records).
> > > >
> > > > Here is how my network looked when I ran a domain using VPC.
> > > >
> > > > Internet
> > > > |
> > > > Netgear
> > > > 192.168.0.1
> > > > |
> > > > Local Network (workgroup)
> > > > 192.168.0.x dg 192.168.0.1
> > > > |
> > > > 192.168.0.254 dg 192.168.0.1
> > > > RRAS/NAT
> > > > 192.168.31.254 dg blank
> > > > |
> > > > DC
> > > > 192.168.31.11 dg 192.168.31.254
> > > > |
> > > > AD members
> > > > 192.168.31.x dg 192.168.31.254 dns 192.168.31.11 > > > > > >
>
> In what I have gathered from this information, the RRAS should be
> setup to connect two networks and not use any of the NAT options?

> > jcwi65;1113831 Wrote:
> > > > Paul Yhonquea;1113555 Wrote:
> > > Bill,
> > >
> > > This is pretty much what I was suggesting to jcwi65, but you did lay
> > > out the
> > > technical details a bit better. Forgot about the piece dealing with
> > > authorizing the DHCP server.
> > >
> > > Paul Yhonquea
> > >
> > >
> > > "Bill Grant" <not.available@xxxxxx> wrote in message
> > > news:ezluDggHKHA.3708@xxxxxx> > > >
> >
> > In what I have gathered from this information, the RRAS should be
> > setup to connect two networks and not use any of the NAT options?> >
>
> Also do I set up the forwarder using my DSL router/modem's default
> DNS #s or the default gateway #?

>> DNS #s or the default gateway #?
> I ran into a problem, when setting up the router server I used Paul's
> scheme from his diagram. I wasn't sure what to use as the DNS on
> connection #2 and I couldn't get it to connect. When I set it back to
> aquire a IP and DNS automatically I could connect at least to the
> Internet.
> I have not tried yet in the rest of the domain as I am
> unclear to the settings in RRAS since I shouldn't use NAT, that only
> leaves connecting two private networks.

> >> Also do I set up the forwarder using my DSL router/modem's default> > > > > > > >
> > > >> DNS #s or the default gateway #? > > > > > >
>
> The Forwarder can actually be configured with the IP of your DS
> modem, o
> the DNS server your ISP gives you
> > > >
> > > I ran into a problem, when setting up the router server I used Paul'
> > > scheme from his diagram. I wasn't sure what to use as the DNS o
> > > connection #2 and I couldn't get it to connect. When I set it back t
> > > aquire a IP and DNS automatically I could connect at least to th
> > > Internet. > >
>
> Use the DSL modem as your gateway and DNS if you decide to go stati
> on th
> external interface of your RRAS, although DHCP from your DS
> modem/route
> will give you all of the info you need
> > > >
> > > I have not tried yet in the rest of the domain as I a
> > > unclear to the settings in RRAS since I shouldn't use NAT, that onl
> > > leaves connecting two private networks. > >
>
> Did you use the "Local Only" option for the internal interface of th
> RRAS
> If so, the IP you assign to it (it should be static) will be th
> gateway fo
> your clients, and any servers in your test environment. IP and subne
> mas
> need to be configured, but leave the default gateway blank for thi
> interface. No need for configuring DNS for this interface either
> Just th
> IP and mask
>
>
>
> Hope this helps
>
>
>
> Paul Yhonquea, MC

>
> When I set up the RRAS on the gateway server, which is the best option
> when setting it up?
>
> 1. NAT
> 2. VPN & NAT
> 3. Secure between two networks
>
>
> --
> jcwi65

> jcwi65
>
> First, my apologies for getting back to you so late
>
> NAT should work. Based on my experiences, though, I normally set u
> RRA
> with the custom configuration, and I just pick network router (LA
> routing)
> After that, once the router starts, you can open the Routing and Remot
> Access MMC snap-in, expand your router, expand IP routing, right-clic
> o
> 'General', and select new routing protocol. You can choose any protoco
> yo
> like; I normally use OSPF, and once that is created, right-click th
> ne
> protocol and select 'New Interface...' (each interface will need to b
> adde
> separately). When adding, just select OK to accept default configs o
> th
> (protocol name here) Properties page
>
>
> Hope this helps
>
>
> Paul Yhonquea, MC
>
>
>
> > > >
> >
> > > When I set up the RRAS on the gateway server, which is the bes
> > optio
> > > when setting it up
> >
> > > 1. NA
> > > 2. VPN & NA
> > > 3. Secure between two network
> >
> >
> > > -
> > > jcwi65 > >

>
> Paul, thank-you for all your help. the configuration is up and running
> perfectly. My only frustration is VPC 2007 SP1x64. I set up the
> virtual domain in VPC and no matter what I tried it wouldn't work. I
> then decided that something I was doing must be wrong. So I decided to
> try the exact same configuration in Virtualbox. After running through
> the setup again, everything worked flawlessly. I suspect that the 64
> bit driver in VPC 2007 has some bugs in it. Thanks again!
>
> jcwi65
>
>
> --
> jcwi65