Domain Controller Slow to boot (Applying Computer Settings)
bg_27
Hi,
I have 2 Domain Controllers (Windows Server 2008 Enterprise) both are
also running DNS (AD integrated).
When I boot both servers up at the same time (or boot a single server),
they stay at "Applying Computer Settings" for about 5 mins. I have read
various things mentioning DNS client settings. If I boot 1 AD server, it
will hang at this point as well, then I boot the second AD server it
boots normally.
My DNS client settings on each server are:
AD01
Preferred DNS: 127.0.0.1
Alternate DNS: 192.168.99.32 (AD02)
AD02
Preferred DNS: 127.0.0.1
Alternate DNS: 192.168.99.31 (AD01)
Is there anything I am missing? Is this normal behavior for 2 domain
controllers? This is causing a problem with my 2008 cluster, which the
cluster name will not come online, I think this problem is related to
the slow booting of DNS/AD.
--
bg_27
------------------------------------------------------------------------
bg_27's Profile: http://forums.techarena.in/members/bg_27.htm
View this thread: http://forums.techarena.in/active-directory/1019600.htm
Hikmat Kanaan
1. Use the Server IP as a preferred DNS server don’t use 127.0.0.1
2. Check your running services to disable unneeded services
3. Check the task schedule , there is a few tasks that you can disable there
that might speed your login
"bg_27" <bg_27....@DoNotSpam.com> wrote in message
news:bg_27....@DoNotSpam.com...
Meinolf Weber
This belongs to the reason that none of tthe servers can reach a DNS server
during startup. They wait until one of them has started the DNS server service
and then is aible to use it. The easiest way will be to have allways a DNS
server up and running.
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
> Hi,
>
> I have 2 Domain Controllers (Windows Server 2008 Enterprise) both are
> also running DNS (AD integrated).
>
> When I boot both servers up at the same time (or boot a single
> server), they stay at "Applying Computer Settings" for about 5 mins. I
> have read various things mentioning DNS client settings. If I boot 1
> AD server, it will hang at this point as well, then I boot the second
> AD server it boots normally.
>
> My DNS client settings on each server are:
>
> AD01
> Preferred DNS: 127.0.0.1
> Alternate DNS: 192.168.99.32 (AD02)
> AD02
> Preferred DNS: 127.0.0.1
> Alternate DNS: 192.168.99.31 (AD01)
> Is there anything I am missing? Is this normal behavior for 2 domain
> controllers? This is causing a problem with my 2008 cluster, which the
> cluster name will not come online, I think this problem is related to
> the slow booting of DNS/AD.
>
Meinolf Weber
Also change the preferred DNS server to the real ip address instaed of the
loopback ip 127.0.0.1
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
> Hi,
>
> I have 2 Domain Controllers (Windows Server 2008 Enterprise) both are
> also running DNS (AD integrated).
>
> When I boot both servers up at the same time (or boot a single
> server), they stay at "Applying Computer Settings" for about 5 mins. I
> have read various things mentioning DNS client settings. If I boot 1
> AD server, it will hang at this point as well, then I boot the second
> AD server it boots normally.
>
> My DNS client settings on each server are:
>
> AD01
> Preferred DNS: 127.0.0.1
> Alternate DNS: 192.168.99.32 (AD02)
> AD02
> Preferred DNS: 127.0.0.1
> Alternate DNS: 192.168.99.31 (AD01)
> Is there anything I am missing? Is this normal behavior for 2 domain
> controllers? This is causing a problem with my 2008 cluster, which the
> cluster name will not come online, I think this problem is related to
> the slow booting of DNS/AD.
>
anthonymaw
Domain Controllers tend to be slow to boot up in the first place
compared to standalone or member servers and 5 minutes is NOT uncommon.
During the Domain Controller boot process there are two stages indicated
by "Applying Network Settings", "Applying Computer Settings", and
"Applying User Settings" after a user logs in. If it chokes at the
"Applying Network Setttings" stage then it's a DNS problem. Applying
Computer or User Settings is when Group Policies get loaded onto the
computer and user registry settings respectively. If there are problems
reading and applying Group Policies then it may appear to hang for a
long time. Both can be related to errors in the server's network
settings or it could be missing or incorrect records in the DNS zone
itself. Domain Controllers have a special set of Group Policies that
are applied by default.
--
anthonymaw
------------------------------------------------------------------------
anthonymaw's Profile: http://forums.techarena.in/members/93470.htm