Re: Domain Controller takes a long time to boot up
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Mon, 21 Apr 2008 18:13:49 -0400
In news:uTasUq9oIHA.4672@xxxxxxxxxxxxxxxxxxxx,
C C <someone@xxxxxxxxxxxxxxx> 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
.
- Follow-Ups:
- References:
- Domain Controller takes a long time to boot up
- From: C C
- Re: Domain Controller takes a long time to boot up
- From: Ace Fekay [MVP]
- Re: Domain Controller takes a long time to boot up
- From: C C
- Domain Controller takes a long time to boot up
- Prev by Date: Re: Internally, Ping Available, But Nothing Else
- Next by Date: Re: Slow browsing within folders
- Previous by thread: Re: Domain Controller takes a long time to boot up
- Next by thread: Re: Domain Controller takes a long time to boot up
- Index(es):
Relevant Pages
|
