Re: Windows 2003 Server Standard Domain Controller multiple NICs

Why on the DC??
DCs are not routers! They don't join subnets.

Regards,

Austin

"jslutzky" <jslutzky@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:70ADA770-0CF2-4FD3-BF6E-FFD06BEF2CAE@xxxxxxxxxxxxxxxx
All I want to do is add another private subnet which I can do by adding
another address to the existing NIC. There is no reason why the two subnets
can not coexist. Do I not have to make changes to internal DNS regarding the
DC? I'm really not trying to make it any more difficult than it is. Just
want to make sure

"Austin Osuide" wrote:

Why do you want to multihome the DC?
Is it just because it has 2 NICs?
You can remove the other NIC to help resist the temptation. Setting up
another VLAN has nothing to do with your DC.
So long as you configure your routing infrastructure so clients can get to
the DC, you have no problems. Issues arise when you want to segregate the
LANs and if they should not see each other I'm sure there are still ways you
can configure that with the routers without multihoming the DCs and if
that's not acceptable, get 2 DCs for the segregated LANs.
Multi-homed DCs, with both interfaces servicing clients, I can only imagine,
will cause you loads of pain.

Regards,

Austin


"jslutzky" <jslutzky@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1F497B3E-D087-41D6-B536-17929858B152@xxxxxxxxxxxxxxxx
>I configured a Windows Server 2003 Standard Domain Controller at one of >our
> call centers and it working fine. The server has two NIC's with one of
> them
> deactivated. The problem is that I'm going to have to bring on another
> subnet (VLAN) and wanted to know if I could enable the second NIC card
> servicing the new subnet. Can a domain controller service multiple
> subnets?
> Would this affect AD? Do I need to have a seperate DC for the other
> Subnet?
>





.

Loading