Thanks Bill,
It worked like a charm!
"Bill Grant" wrote:
> I agree that if you want to set up a test domain, you really need to
> isolate it from physical LAN. If you do that, Internet access is not easy.
>
> The best method to use is, not surprisingly, the same method that you
> would use on a physical network. You set up your domain on an internal
> virtual network with no links to any interface on the host (emulating a
> switch with no connection to any other network).
>
> To access the Internet you set up a vm which has one interface in this
> network and one linked to a virtual network which can access the outside
> world (such as a NIC in the host machine). You then configure this vm as a
> NAT router. The machines behind NAT can acess the physical LAN, but the
> physical LAN will be unaware of the virtual LAN.
>
> There is the added complication that the standard settings for NAT are
> not compatible with AD. Standard NAT uses the NAT router for DNS, and the
> NAT router forwards the requests to a public DNS server. AD clients must use
> the local DNS, so you need to set your local DNS to forward to a public DNS
> so that public URLs can be resolved.
>
>
> "lunarpc" <(E-Mail Removed)> wrote in message
> news:837B1FD4-293A-4DFA-A983-(E-Mail Removed)...
> > Hi,
> > I have a W2K3 host with a virtual W2K3. I've got them on a virtual
> > network.
> > The host is on a live business network. I do not have access to a seperate
> > switch. This are testing machines for my learning enjoyment. I'm ready to
> > run
> > AD on them but I want to isolate all the domain activity to my virtual
> > network and be able to use remote desktop to the host.
> >
> > bottom line...host needs to connect to the internet but not broadcast
> > domain
> > information except to the virtual network.
> >
> > I'm not sure how to do that.
> >
> > Any help is appreciated,
> > - Mary
>
>
|
Similar Threads
Linear Mode
