Domain Controller takes a long time to boot up

Hello.

We had to shutdown servers in our computer room last
night due to high temp. The AC condenser froze.

After the AC was back to normal, I started the DC's first.
DC1 took a long time to boot up. It stayed long on the
"Preparing network connections" then on the next one
I couldn't remember. So I started up the DC2. That
took a long time to boot up too.

What do I need to know to speed up the bootup of
Domain Controllers with Active Directory?

Thanks in advance.

Hello C,

The problem is that the DC only can full boot if the DNS service is started
or they can reach a DNS server. This will cause the long boot time. During
the startup it will first check for the preferred DNS server, i assume that's
itself, so it realized the machine is up and wait for DNS.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hello.
>
> We had to shutdown servers in our computer room last night due to high
> temp. The AC condenser froze.
>
> After the AC was back to normal, I started the DC's first.
> DC1 took a long time to boot up. It stayed long on the
> "Preparing network connections" then on the next one
> I couldn't remember. So I started up the DC2. That
> took a long time to boot up too.
> What do I need to know to speed up the bootup of
> Domain Controllers with Active Directory?
> Thanks in advance.
>

That isn't all that abnormal. But you can aggravate it if the DNS listed in
the TCP/IP Specs it not the DC itself listed first.

Beyond that,...if there is anything serously wrong it will have something in
the Event log.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"C C" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hello.
>
> We had to shutdown servers in our computer room last
> night due to high temp. The AC condenser froze.
>
> After the AC was back to normal, I started the DC's first.
> DC1 took a long time to boot up. It stayed long on the
> "Preparing network connections" then on the next one
> I couldn't remember. So I started up the DC2. That
> took a long time to boot up too.
>
> What do I need to know to speed up the bootup of
> Domain Controllers with Active Directory?
>
> Thanks in advance.
>

In news:%(E-Mail Removed),
C C <(E-Mail Removed)> typed:
> Hello.
>
> We had to shutdown servers in our computer room last
> night due to high temp. The AC condenser froze.
>
> After the AC was back to normal, I started the DC's first.
> DC1 took a long time to boot up. It stayed long on the
> "Preparing network connections" then on the next one
> I couldn't remember. So I started up the DC2. That
> took a long time to boot up too.
>
> What do I need to know to speed up the bootup of
> Domain Controllers with Active Directory?
>
> Thanks in advance.

DNS can have alot to do with it, but can't say for sure without knowing your
config. What DNS servers are configureed in the DC's IP properties?

If you have one of the replica DCs in the Site as the first entry and itself
as the second entry, I can see why when booting both DCs up at the same time
they can't find their DNS server, even if it is itself, because it goes
through the DNS resolver resolution process time-out before it goes to the
second one to find the DC, which even if itself.

If you have itself listed first, then a replica DC in the same subnet as
it's second one it will boot quicker.

If you have your ISP's listed in the config, it will be problematic because
the cardinal rule is to not use your ISP anywhere other than a forwarder.

If you can post an unedited ipconfig /all of both DCs, it will be extremely
helpful towards a diagnosis.

Thanks,

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations

Have a look at "Domain Controller boots up slowly when pointing to itself as
the only DNS server" (http://support.microsoft.com/kb/945765/en-us) and
"Best practices for DNS client settings in Windows 2000 Server and in
Windows Server 2003" (http://support.microsoft.com/kb/825036/en-us)

ThePro

"C C" <(E-Mail Removed)> wrote:
> Hello.
>
> What do I need to know to speed up the bootup of
> Domain Controllers with Active Directory?

Thanks for your reply. I have attached the ipconfig of both DC's below.

Please note that the computer room was totally shutdown, which means
that at powerup, no other DC/DNS is available. Both were booting up!

Another user posted his reply with the following links:
http://support.microsoft.com/kb/945765/en-us
http://support.microsoft.com/kb/825036/en-us

IPCONFIG output: Note that the default gateway is our ISA Server
which is still down at the time the DC's are booting up.

=========== DC1 IPCONFIG ============

Windows IP Configuration
Host Name . . . . . . . . . . . . : MCDC1
Primary Dns Suffix . . . . . . . : mc.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mc.local
ecommc.local

Ethernet adapter LAN:

Connection-specific DNS Suffix . : mc.local
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.14
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.3
DNS Servers . . . . . . . . . . . : 192.168.0.14
192.168.0.12
Primary WINS Server . . . . . . . : 192.168.0.14
Secondary WINS Server . . . . . . : 192.168.0.12

==========DC2 IPCONFIG: =============

Windows IP Configuration

Host Name . . . . . . . . . . . . : MCDC2
Primary Dns Suffix . . . . . . . : mc.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mc.local

Ethernet adapter Private Lan:

Connection-specific DNS Suffix . : mc.local
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.3
DNS Servers . . . . . . . . . . . : 192.168.0.12
192.168.0.14
Primary WINS Server . . . . . . . : 192.168.0.12
Secondary WINS Server . . . . . . : 192.168.0.14


"Ace Fekay [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In news:%(E-Mail Removed),
> C C <(E-Mail Removed)> typed:
>> Hello.
>>
>> We had to shutdown servers in our computer room last
>> night due to high temp. The AC condenser froze.
>>
>> After the AC was back to normal, I started the DC's first.
>> DC1 took a long time to boot up. It stayed long on the
>> "Preparing network connections" then on the next one
>> I couldn't remember. So I started up the DC2. That
>> took a long time to boot up too.
>>
>> What do I need to know to speed up the bootup of
>> Domain Controllers with Active Directory?
>>
>> Thanks in advance.
>
> DNS can have alot to do with it, but can't say for sure without knowing
> your config. What DNS servers are configureed in the DC's IP properties?
>
> If you have one of the replica DCs in the Site as the first entry and
> itself as the second entry, I can see why when booting both DCs up at the
> same time they can't find their DNS server, even if it is itself, because
> it goes through the DNS resolver resolution process time-out before it
> goes to the second one to find the DC, which even if itself.
>
> If you have itself listed first, then a replica DC in the same subnet as
> it's second one it will boot quicker.
>
> If you have your ISP's listed in the config, it will be problematic
> because the cardinal rule is to not use your ISP anywhere other than a
> forwarder.
>
> If you can post an unedited ipconfig /all of both DCs, it will be
> extremely helpful towards a diagnosis.
>
> Thanks,
>
> --
> Regards,
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
> MVP Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Infinite Diversities in Infinite Combinations
>
>

In news:(E-Mail Removed),
C C <(E-Mail Removed)> typed:
> Thanks for your reply. I have attached the ipconfig of both DC's
> below.
> Please note that the computer room was totally shutdown, which means
> that at powerup, no other DC/DNS is available. Both were booting up!
>
> Another user posted his reply with the following links:
> http://support.microsoft.com/kb/945765/en-us
> http://support.microsoft.com/kb/825036/en-us
>
> IPCONFIG output: Note that the default gateway is our ISA Server
> which is still down at the time the DC's are booting up.
>
> =========== DC1 IPCONFIG ============
>
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : MCDC1
> Primary Dns Suffix . . . . . . . : mc.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : mc.local
> ecommc.local
>
> Ethernet adapter LAN:
>
> Connection-specific DNS Suffix . : mc.local
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection
> Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.14
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.3
> DNS Servers . . . . . . . . . . . : 192.168.0.14
> 192.168.0.12
> Primary WINS Server . . . . . . . : 192.168.0.14
> Secondary WINS Server . . . . . . : 192.168.0.12
>
> ==========DC2 IPCONFIG: =============
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : MCDC2
> Primary Dns Suffix . . . . . . . : mc.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : mc.local
>
> Ethernet adapter Private Lan:
>
> Connection-specific DNS Suffix . : mc.local
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> Ethernet Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.12
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.0.3
> DNS Servers . . . . . . . . . . . : 192.168.0.12
> 192.168.0.14
> Primary WINS Server . . . . . . . : 192.168.0.12
> Secondary WINS Server . . . . . . : 192.168.0.14

Thanks for posting the info. Yes, I did see the other poster's post and well
aware of those articles, for I usually reference them for other posters.
However, I wanted to see your configuration first before making any
comments, recommendations or diagnosis.

The configs actually look great and is the way I would configure DNS
settings. But the problem is when both DCs are down simultaneously and you
try to boot them up simultenously, you would experience the long delays
because they simply can't find domain resources and service locations (SRVs)
because the DNS server they are querying is not up yet. This would explain
the whole issue.

Does the AC problem happen often where it shuts down both DCs? If so, to
alleviate this problem in YOUR scenario where both are down more often than
one would like to see, I would probably point to itself first, then the
partner. Another solution is place a member server with a secondary copy of
the zone, and point both DC's first entry to it, then itself as the second.

But honestly, if this is only an isolated and rare incident/occurence, I
wouldn't worry about your configs or change anything and just get the AC
fixed or have some kind of AC backup. This way you won't see this again.

Ace

"Ace Fekay [MVP]" <(E-Mail Removed)> wrote in message
news:%23rXWH0$(E-Mail Removed)...
> In news:(E-Mail Removed),
> C C <(E-Mail Removed)> typed:
>> Thanks for your reply. I have attached the ipconfig of both DC's
>> below.
>> Please note that the computer room was totally shutdown, which means
>> that at powerup, no other DC/DNS is available. Both were booting up!
>>
>> Another user posted his reply with the following links:
>> http://support.microsoft.com/kb/945765/en-us
>> http://support.microsoft.com/kb/825036/en-us
>>
>> IPCONFIG output: Note that the default gateway is our ISA Server
>> which is still down at the time the DC's are booting up.
>>
>> =========== DC1 IPCONFIG ============
>>
>> Windows IP Configuration
>> Host Name . . . . . . . . . . . . : MCDC1
>> Primary Dns Suffix . . . . . . . : mc.local
>> Node Type . . . . . . . . . . . . : Hybrid
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : mc.local
>> ecommc.local
>>
>> Ethernet adapter LAN:
>>
>> Connection-specific DNS Suffix . : mc.local
>> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
>> Connection
>> Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.0.14
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.0.3
>> DNS Servers . . . . . . . . . . . : 192.168.0.14
>> 192.168.0.12
>> Primary WINS Server . . . . . . . : 192.168.0.14
>> Secondary WINS Server . . . . . . : 192.168.0.12
>>
>> ==========DC2 IPCONFIG: =============
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : MCDC2
>> Primary Dns Suffix . . . . . . . : mc.local
>> Node Type . . . . . . . . . . . . : Hybrid
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : mc.local
>>
>> Ethernet adapter Private Lan:
>>
>> Connection-specific DNS Suffix . : mc.local
>> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>> Ethernet Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.0.12
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.0.3
>> DNS Servers . . . . . . . . . . . : 192.168.0.12
>> 192.168.0.14
>> Primary WINS Server . . . . . . . : 192.168.0.12
>> Secondary WINS Server . . . . . . : 192.168.0.14
>
> Thanks for posting the info. Yes, I did see the other poster's post and
> well aware of those articles, for I usually reference them for other
> posters. However, I wanted to see your configuration first before making
> any comments, recommendations or diagnosis.
>
> The configs actually look great and is the way I would configure DNS
> settings. But the problem is when both DCs are down simultaneously and you
> try to boot them up simultenously, you would experience the long delays
> because they simply can't find domain resources and service locations
> (SRVs) because the DNS server they are querying is not up yet. This would
> explain the whole issue.
>
> Does the AC problem happen often where it shuts down both DCs? If so, to
> alleviate this problem in YOUR scenario where both are down more often
> than one would like to see, I would probably point to itself first, then
> the partner. Another solution is place a member server with a secondary
> copy of the zone, and point both DC's first entry to it, then itself as
> the second.
>
> But honestly, if this is only an isolated and rare incident/occurence, I
> wouldn't worry about your configs or change anything and just get the AC
> fixed or have some kind of AC backup. This way you won't see this again.
>
> Ace
>

Ace, thanks. This is our first AC problem which
caused the total shutdown. This is the first time
both DC's were down therefore this is our first
experience with the slow boot up of the DC's.

Thanks for your suggestion. I will consider setting
up a member server to store the second copy of
the zone.

In news:(E-Mail Removed),
C R C <(E-Mail Removed)> typed:
>
> Ace, thanks. This is our first AC problem which
> caused the total shutdown. This is the first time
> both DC's were down therefore this is our first
> experience with the slow boot up of the DC's.
>
> Thanks for your suggestion. I will consider setting
> up a member server to store the second copy of
> the zone.

No problem, CRC.

Or you can also leave it alone as it is. :-)

Cheers!