Re: Windows 2003 Server Standard Domain Controller multiple NICs

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

We understand you. At least I think I do.
You DC does not care where your clients are wrt subnets.
If your routing infrastructure is setup correctly, and you have your DNS servers correctly entered into clients, your DC only needs the 1 IP address it has.
What you have right now is Network routing issue. Leave the DC as is with one NIC and one IP address.

Regards,

Austin

"jslutzky" <jslutzky@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6217706D-3043-40F1-807A-F48195AA40DD@xxxxxxxxxxxxxxxx
I'm probably not explaining myself correctly. I currently have 192.168.5.xxx
network that clients reside on with the DC on that network. I am now adding
200 more workstations that will reside on a new network 192.168.8.xxx which
will need to be part of the domain. With that being said they will need to
be able to communicate with the domain controller on the 192.168.5.xxx
network, so the DC should listen for both 192.168.5.xxx / 8.xxx traffic.
Correct?


"Austin Osuide" wrote:

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?
>> >
>>
>>
>>
>>



.

Quantcast