Networking Forums

Networking Forums > Computer Networking > Windows Networking > Domain Controller Advice

Reply
Thread Tools Display Modes

Domain Controller Advice

 
 
Marka
Guest
Posts: n/a

 
      02-15-2005, 11:12 AM
We are a single site with a Windows 2000 domain. We have 2 DC's - DC1 & DC2.

DC1 was the first one to be installed and has all the five FSMO roles
running on it.

We also made DC2 into a Global Catalog Server as Exchange 2003 (which we
have running on a 2003 member server) wouldn't run if DC1 went down..

Our MAIN concern is if DC1 fails, we would need DC2 to run on its own.

We tested this situation by shutting down DC1, leaving DC2 running.

When running on DC2, a number of our client machines were very slow and not
usable, but some of our client machines seemed to be running OK ??

What would we need to do to make sure DC2 can run all clients OK if DC1 goes
down.

Thanks

Mark


 
Reply With Quote
 
 
 
 
Miha Pihler [MVP]
Guest
Posts: n/a

 
      02-15-2005, 11:25 AM
Hi Mark,

How is your DNS setup? Are both of your domain controllers also DNS servers
for your active directory domain? Do your clients have both server (DC1 and
DC2) listed as DNS servers (set under TCP/IP properties).

Clients use DNS to located domain controllers, global catalogs etc... If you
only have one DNS server or if your clients has only one DNS server set for
preferred DNS server (under TCP/IP properties) and this DNS server goes down
clients will fail to find other domain controllers.

--
Mike
Microsoft MVP - Windows Security

"Marka" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We are a single site with a Windows 2000 domain. We have 2 DC's - DC1 &
> DC2.
>
> DC1 was the first one to be installed and has all the five FSMO roles
> running on it.
>
> We also made DC2 into a Global Catalog Server as Exchange 2003 (which we
> have running on a 2003 member server) wouldn't run if DC1 went down..
>
> Our MAIN concern is if DC1 fails, we would need DC2 to run on its own.
>
> We tested this situation by shutting down DC1, leaving DC2 running.
>
> When running on DC2, a number of our client machines were very slow and
> not usable, but some of our client machines seemed to be running OK ??
>
> What would we need to do to make sure DC2 can run all clients OK if DC1
> goes down.
>
> Thanks
>
> Mark
>



 
Reply With Quote
 
Marka
Guest
Posts: n/a

 
      02-15-2005, 12:37 PM
Thanks for the reply

Both DC1 & DC2 are Active Directory-Integrated DNS servers.

All PC's on the network are DHCP clients who receive there IP address and
DNS settings from the DHCP server on DC1.

Their DNS server settings are set to "Preferred" DC1 & "Alternate" DC2

Thanks

Mark


> Hi Mark,
>
> How is your DNS setup? Are both of your domain controllers also DNS
> servers for your active directory domain? Do your clients have both server
> (DC1 and DC2) listed as DNS servers (set under TCP/IP properties).
>
> Clients use DNS to located domain controllers, global catalogs etc... If
> you only have one DNS server or if your clients has only one DNS server
> set for preferred DNS server (under TCP/IP properties) and this DNS server
> goes down clients will fail to find other domain controllers.
>
> --
> Mike
> Microsoft MVP - Windows Security



 
Reply With Quote
 
Clayton Sutton
Guest
Posts: n/a

 
      02-15-2005, 01:14 PM
Hey Marka,

First off split your DHCP between the to DCs. If only DC1 is doing DHCP you
are dead in the water if it goes down. You should have enough addresses on
each DHCP server to handle all of your network needs if the other DHCP
server went down.


Clayton



"Marka" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks for the reply
>
> Both DC1 & DC2 are Active Directory-Integrated DNS servers.
>
> All PC's on the network are DHCP clients who receive there IP address and
> DNS settings from the DHCP server on DC1.
>
> Their DNS server settings are set to "Preferred" DC1 & "Alternate" DC2
>
> Thanks
>
> Mark
>
>
> > Hi Mark,
> >
> > How is your DNS setup? Are both of your domain controllers also DNS
> > servers for your active directory domain? Do your clients have both

server
> > (DC1 and DC2) listed as DNS servers (set under TCP/IP properties).
> >
> > Clients use DNS to located domain controllers, global catalogs etc... If
> > you only have one DNS server or if your clients has only one DNS server
> > set for preferred DNS server (under TCP/IP properties) and this DNS

server
> > goes down clients will fail to find other domain controllers.
> >
> > --
> > Mike
> > Microsoft MVP - Windows Security

>
>



 
Reply With Quote
 
Doug Sherman [MVP]
Guest
Posts: n/a

 
      02-15-2005, 04:59 PM
The problem is the FSMO roles. In the case of catrastrophic failure of DC1,
you could seize the roles on DC2 and your domain should survive with
relatively little re-configuration or other dislocation. However, do NOT
seize roles as part of a test - there are major consequences for DC1. See:

http://support.microsoft.com/default...b;en-us;255504

and

http://support.microsoft.com/default...b;en-us;216498

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Marka" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We are a single site with a Windows 2000 domain. We have 2 DC's - DC1 &

DC2.
>
> DC1 was the first one to be installed and has all the five FSMO roles
> running on it.
>
> We also made DC2 into a Global Catalog Server as Exchange 2003 (which we
> have running on a 2003 member server) wouldn't run if DC1 went down..
>
> Our MAIN concern is if DC1 fails, we would need DC2 to run on its own.
>
> We tested this situation by shutting down DC1, leaving DC2 running.
>
> When running on DC2, a number of our client machines were very slow and

not
> usable, but some of our client machines seemed to be running OK ??
>
> What would we need to do to make sure DC2 can run all clients OK if DC1

goes
> down.
>
> Thanks
>
> Mark
>
>



 
Reply With Quote
 
Marka
Guest
Posts: n/a

 
      02-17-2005, 10:52 AM
Our DHCP server has a 8 day lease duration. After we shut DC1 down, we
checked some of the clients with IPCONFIG.
The ip address remained the same.

Mark

"Clayton Sutton" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hey Marka,
>
> First off split your DHCP between the to DCs. If only DC1 is doing DHCP
> you
> are dead in the water if it goes down. You should have enough addresses
> on
> each DHCP server to handle all of your network needs if the other DHCP
> server went down.
>
>
> Clayton
>
>
>
> "Marka" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Thanks for the reply
>>
>> Both DC1 & DC2 are Active Directory-Integrated DNS servers.
>>
>> All PC's on the network are DHCP clients who receive there IP address and
>> DNS settings from the DHCP server on DC1.
>>
>> Their DNS server settings are set to "Preferred" DC1 & "Alternate" DC2
>>
>> Thanks
>>
>> Mark
>>
>>
>> > Hi Mark,
>> >
>> > How is your DNS setup? Are both of your domain controllers also DNS
>> > servers for your active directory domain? Do your clients have both

> server
>> > (DC1 and DC2) listed as DNS servers (set under TCP/IP properties).
>> >
>> > Clients use DNS to located domain controllers, global catalogs etc...
>> > If
>> > you only have one DNS server or if your clients has only one DNS server
>> > set for preferred DNS server (under TCP/IP properties) and this DNS

> server
>> > goes down clients will fail to find other domain controllers.
>> >
>> > --
>> > Mike
>> > Microsoft MVP - Windows Security

>>
>>

>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. Ace Fekay [MVP-DS, MCT] Windows Networking 1 01-10-2010 11:08 PM
Clients can't join domain-new Primary Domain Controller installed blinton25 Windows Networking 7 06-23-2008 09:58 PM
Server 2003 Standard - Cannot browse domain with domain controller! davidw@dwynn.demon.co.uk Windows Networking 2 04-12-2006 04:28 PM
second domain controller idsi Windows Networking 1 08-31-2004 07:40 PM
Moving a domain 2003 domain controller to a different subnet John zhang Windows Networking 1 07-27-2004 01:41 PM



1 2 3 4 5 6 7 8 9 10 11