Virtual PC Win2k8 domain
mihap...@gmail.com
One Win2k8 RC1 is set up as a DC and has DNS, DHCP on it.
Second Win2k8 RC1 is a member server (will be an Exchange box
afterwards).
At first the network adapter on both was the physical one. That was
before I installed DHCP and everything worked fine. The 2nd server was
able to join the domain without problems. Now I installed DHCP on the
DC and I want to have a "separate" network of some sorts.
DC, DHCP, DNS server IP is 192.168.1.130, default gateway 192.168.1.1
The 2nd server if both NIC's are on the physical adapter gets the IP
from my router, not the DHCP (the IP of the DC is listed under Scope
Option as the router) server I installed on the DC.
If I put both NIC's on local only, then the 2nd server gets the IP
from the DC DHCP...but I'm unable to browse the internet on both
machines.
I just want to get both machines online and I have no idea how to do
that, except by going back one step and configuring both NIC's as
physical ones of the host, but then the 2nd server gets the IP from my
router and not the DHCP on the DC.
I'd appreciate any and all suggestions. Have I done something wrong
when configuring DNS (DNS IP's of my ISP are in the forwarders)?
Please let me know if further details, information is needed for
resolving this.
Bill Grant
non-trivial operation, whether you are using physical or virtual machines.
If you want to use DHCP, you really need your domain machines to be in
their own network, not linked to the host's physical network. And they need
to be in their own IP subnet. With VPC the best idea is to put them in local
only. The AD clients will get their network config from DHCP on the DC and
Active Directory will all work.
Internet access is another matter altogether. To do that you need a
machine which can act as a router between the virtual network and the
physical network. You can use a virtual machine with tw NICs, one linked to
the virtual network and one to the physical network (through the host
machines's NIC). I would not recommend using either a DC or an Exchange
server for this. You could use Win2k/2k3 with RRAS or a Linux vm running as
a NAT router.
There is still the problem of DNS. Since the AD machines all use the
local DNS (so that they can see the SRV records) they cannot resolve foreign
URLs. You need to set up the local DNS to forward to a public DNS (or a DNS
server on your physical LAN which can resolve them). This is not because you
are using virtual machines. You need to do the same with real machines on
real networks.
<mihap...@gmail.com> wrote in message
news:be0de256-7f9f-4c6d...@e6g2000prf.googlegroups.com...
mihap...@gmail.com
> That is pretty much what should happen. Setting up a domain is a
> non-trivial operation, whether you are using physical or virtual machines.
>
> If you want to use DHCP, you really need your domain machines to be in
> their own network, not linked to the host's physical network. And they need
> to be in their own IP subnet. With VPC the best idea is to put them in local
> only. The AD clients will get their network config from DHCP on the DC and
> Active Directory will all work.
>
> Internet access is another matter altogether. To do that you need a
> machine which can act as a router between the virtual network and the
> physical network. You can use a virtual machine with tw NICs, one linked to
> the virtual network and one to the physical network (through the host
> machines's NIC). I would not recommend using either a DC or an Exchange
> server for this. You could use Win2k/2k3 with RRAS or a Linux vm running as
> a NAT router.
>
> There is still the problem of DNS. Since the AD machines all use the
> local DNS (so that they can see the SRV records) they cannot resolve foreign
> URLs. You need to set up the local DNS to forward to a public DNS (or a DNS
> server on your physical LAN which can resolve them). This is not because you
> are using virtual machines. You need to do the same with real machines on
> real networks.
>
Thank you very much for your reply.
As you probably noticed I don't have a wealth of experience in these
matters. I'll consider using a new VM with two NIC's so I can get
internet access. As for DNS isn't it enough to set up the DNS IP's of
my ISP in the forwarders?
Is this process any easier in the Virtual Server. I'd also appreciate
any and all URLs so I can better understand the problems I'm facing.
Bill Grant
<mihap...@gmail.com> wrote in message
news:e682c16a-010e-4369...@s8g2000prg.googlegroups.com...
Yes, setting your DNS on the DC to forward to the DNS server will do the
trick.
No, it would not be any easier using Virtual Server. You would still
need to do the same things, and learning to drive Virtual Server is not
easy.
The network config is not very difficult. You configure the router to
act as a NAT router. You configure your "private" LAN machines to use the
router ad their default gateway but use the DC for DNS. My setup looks like
this. (My physical LAN uses 10.0.0.x addresses with the router at
10.0.0.1 ).
Internet
|
DSL
10.0.0.1-----------host an other LAN machines
|
10.0.0.99 dg 10.0.0.1
RRAS/NAT
192.168.21.254 dg blank
|
192.168.21.1 dg 192.168.21.254
DC,DHCP,DNS server
|
192.168.21.x dg 192.168.21.254
domain members
network config from DHCP
DNS set to 192.168.21.1
mihap...@gmail.com
currently have this network config, much like you pointed it out:
internet
|
ADSL (PPPoE)
192.168.1.1
Linksys router
|
192.168.1.130 dg=192.168.1.1
m0n0wall NAT
10.0.0.1 dg=none
|
10.0.0.10 dg=10.0.0.1
DC, DHCP, DNS
|
10.0.0.100-140 (DHCP range) dg=10.0.0.1
domain members, get their network config from DHCP
DNS=10.0.0.10
Don't know what to do now, it seems to be working just fine. Will
probably mess with Exchange, NAP, Terminal Services, IIS,
virtualization (not on the top of my list),...
This is all quite new to me so any suggestions as to what to test are
welcome.
Thank you for your assistance, it helped immensely.