Server 2003 R2 takes 20 min to boot.

[Guest quantum]

Over the past few days I have added a few more DC's to our domain and one of

them is acting pretty funny. It's windows server 2003 R2; it booted fine

while it was being configured and when it was first promoted to a DC and DNS

(AD intergrated) was installed. Then litteraly over night it will now hang

first on "prepairing network connections" for a few minutes and then on

"Applying computer settings" for at least 10min. When the system finally

boots it acts and works fine, there are no errors in the logs (except for

those pretaining to missing AD replication). I've searched and the only thing

I could find was in reference to Powerchute, but that is not installed on the

server (only AD, DNS, Symantec AV, and Adobe reader). Any thoughts as to what

could be causing the problem? Thanks.

[Guest Mathieu CHATEAU]

Re: Server 2003 R2 takes 20 min to boot.

 

Hello,

 

this is normally a network/dns issue.

 

What about:

netdiag

dcdiag

 

Did you change sysvol from the default path ?

 

Do you have more than one network card ? Is the good one primary ?

Did you install the SP2 ?

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"quantum" <quantum@discussions.microsoft.com> wrote in message

news:ECE63B78-278D-4767-8B8B-23F9445E2A3F@microsoft.com...

> Over the past few days I have added a few more DC's to our domain and one

> of

> them is acting pretty funny. It's windows server 2003 R2; it booted fine

> while it was being configured and when it was first promoted to a DC and

> DNS

> (AD intergrated) was installed. Then litteraly over night it will now hang

> first on "prepairing network connections" for a few minutes and then on

> "Applying computer settings" for at least 10min. When the system finally

> boots it acts and works fine, there are no errors in the logs (except for

> those pretaining to missing AD replication). I've searched and the only

> thing

> I could find was in reference to Powerchute, but that is not installed on

> the

> server (only AD, DNS, Symantec AV, and Adobe reader). Any thoughts as to

> what

> could be causing the problem? Thanks.

[Guest quantum]

Re: Server 2003 R2 takes 20 min to boot.

 

Netdiag /test:dns says everything is ok. I did find a entry missing earlier,

but I replaced it. (I'll check to make sure the entry I fixed stuck, I

rebooted it right after I replaced it, but maybe it needed to replicate first)

 

Dcdiag shows everything ok except for the relpications it misses when

rebooted.

 

sysvol is in it's standard path.

 

There are two broadcom nic's on it teamed to one IP. I guess I could try

unteaming them, but it worked fine yesterday with them teamed up.

 

Yes sp2 is installed and updates are current as of today.

 

Thanks for the help.

 

 

"Mathieu CHATEAU" wrote:

> Hello,

>

> this is normally a network/dns issue.

>

> What about:

> netdiag

> dcdiag

>

> Did you change sysvol from the default path ?

>

> Do you have more than one network card ? Is the good one primary ?

> Did you install the SP2 ?

>

> --

> Cordialement,

> Mathieu CHATEAU

> English blog: http://lordoftheping.blogspot.com

> French blog: http://www.lotp.fr

>

>

> "quantum" <quantum@discussions.microsoft.com> wrote in message

> news:ECE63B78-278D-4767-8B8B-23F9445E2A3F@microsoft.com...

> > Over the past few days I have added a few more DC's to our domain and one

> > of

> > them is acting pretty funny. It's windows server 2003 R2; it booted fine

> > while it was being configured and when it was first promoted to a DC and

> > DNS

> > (AD intergrated) was installed. Then litteraly over night it will now hang

> > first on "prepairing network connections" for a few minutes and then on

> > "Applying computer settings" for at least 10min. When the system finally

> > boots it acts and works fine, there are no errors in the logs (except for

> > those pretaining to missing AD replication). I've searched and the only

> > thing

> > I could find was in reference to Powerchute, but that is not installed on

> > the

> > server (only AD, DNS, Symantec AV, and Adobe reader). Any thoughts as to

> > what

> > could be causing the problem? Thanks.

>

>

[Guest quantum]

Re: Server 2003 R2 takes 20 min to boot.

 

Ok, I was wrong. The missing entry I put in DNS didn't fix it. When I run

netdiag I get 2 errors.

 

The says that the dns entries for the server are not registered correctly. I

removed the DNS server from the server and redirected to the primary DNS

server, but the error still apprears only with the primary servers ip now.

 

The second error is with the trusts and says "[FATAL] Secure channel to

domain '<domain name>' is broken. [ERROR_NO_LOGON_SERVERS].

 

If I run nltest /sc_reset:<domain name> it reconnect correctly, but upon

reboot comes back with the same error. Any thoughts?

 

 

 

"quantum" wrote:

> Netdiag /test:dns says everything is ok. I did find a entry missing earlier,

> but I replaced it. (I'll check to make sure the entry I fixed stuck, I

> rebooted it right after I replaced it, but maybe it needed to replicate first)

>

> Dcdiag shows everything ok except for the relpications it misses when

> rebooted.

>

> sysvol is in it's standard path.

>

> There are two broadcom nic's on it teamed to one IP. I guess I could try

> unteaming them, but it worked fine yesterday with them teamed up.

>

> Yes sp2 is installed and updates are current as of today.

>

> Thanks for the help.

>

>

> "Mathieu CHATEAU" wrote:

>

> > Hello,

> >

> > this is normally a network/dns issue.

> >

> > What about:

> > netdiag

> > dcdiag

> >

> > Did you change sysvol from the default path ?

> >

> > Do you have more than one network card ? Is the good one primary ?

> > Did you install the SP2 ?

> >

> > --

> > Cordialement,

> > Mathieu CHATEAU

> > English blog: http://lordoftheping.blogspot.com

> > French blog: http://www.lotp.fr

> >

> >

> > "quantum" <quantum@discussions.microsoft.com> wrote in message

> > news:ECE63B78-278D-4767-8B8B-23F9445E2A3F@microsoft.com...

> > > Over the past few days I have added a few more DC's to our domain and one

> > > of

> > > them is acting pretty funny. It's windows server 2003 R2; it booted fine

> > > while it was being configured and when it was first promoted to a DC and

> > > DNS

> > > (AD intergrated) was installed. Then litteraly over night it will now hang

> > > first on "prepairing network connections" for a few minutes and then on

> > > "Applying computer settings" for at least 10min. When the system finally

> > > boots it acts and works fine, there are no errors in the logs (except for

> > > those pretaining to missing AD replication). I've searched and the only

> > > thing

> > > I could find was in reference to Powerchute, but that is not installed on

> > > the

> > > server (only AD, DNS, Symantec AV, and Adobe reader). Any thoughts as to

> > > what

> > > could be causing the problem? Thanks.

> >

> >

[Guest Mathieu CHATEAU]

Re: Server 2003 R2 takes 20 min to boot.

 

if you remove the dns entry and then issue ipconfig /registerdns

Does it work ?

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"quantum" <quantum@discussions.microsoft.com> wrote in message

news:3E6E11CF-C244-4435-99C6-149781C23011@microsoft.com...

> Ok, I was wrong. The missing entry I put in DNS didn't fix it. When I run

> netdiag I get 2 errors.

>

> The says that the dns entries for the server are not registered correctly.

> I

> removed the DNS server from the server and redirected to the primary DNS

> server, but the error still apprears only with the primary servers ip now.

>

> The second error is with the trusts and says "[FATAL] Secure channel to

> domain '<domain name>' is broken. [ERROR_NO_LOGON_SERVERS].

>

> If I run nltest /sc_reset:<domain name> it reconnect correctly, but upon

> reboot comes back with the same error. Any thoughts?

>

>

>

> "quantum" wrote:

>

>> Netdiag /test:dns says everything is ok. I did find a entry missing

>> earlier,

>> but I replaced it. (I'll check to make sure the entry I fixed stuck, I

>> rebooted it right after I replaced it, but maybe it needed to replicate

>> first)

>>

>> Dcdiag shows everything ok except for the relpications it misses when

>> rebooted.

>>

>> sysvol is in it's standard path.

>>

>> There are two broadcom nic's on it teamed to one IP. I guess I could try

>> unteaming them, but it worked fine yesterday with them teamed up.

>>

>> Yes sp2 is installed and updates are current as of today.

>>

>> Thanks for the help.

>>

>>

>> "Mathieu CHATEAU" wrote:

>>

>> > Hello,

>> >

>> > this is normally a network/dns issue.

>> >

>> > What about:

>> > netdiag

>> > dcdiag

>> >

>> > Did you change sysvol from the default path ?

>> >

>> > Do you have more than one network card ? Is the good one primary ?

>> > Did you install the SP2 ?

>> >

>> > --

>> > Cordialement,

>> > Mathieu CHATEAU

>> > English blog: http://lordoftheping.blogspot.com

>> > French blog: http://www.lotp.fr

>> >

>> >

>> > "quantum" <quantum@discussions.microsoft.com> wrote in message

>> > news:ECE63B78-278D-4767-8B8B-23F9445E2A3F@microsoft.com...

>> > > Over the past few days I have added a few more DC's to our domain and

>> > > one

>> > > of

>> > > them is acting pretty funny. It's windows server 2003 R2; it booted

>> > > fine

>> > > while it was being configured and when it was first promoted to a DC

>> > > and

>> > > DNS

>> > > (AD intergrated) was installed. Then litteraly over night it will now

>> > > hang

>> > > first on "prepairing network connections" for a few minutes and then

>> > > on

>> > > "Applying computer settings" for at least 10min. When the system

>> > > finally

>> > > boots it acts and works fine, there are no errors in the logs (except

>> > > for

>> > > those pretaining to missing AD replication). I've searched and the

>> > > only

>> > > thing

>> > > I could find was in reference to Powerchute, but that is not

>> > > installed on

>> > > the

>> > > server (only AD, DNS, Symantec AV, and Adobe reader). Any thoughts as

>> > > to

>> > > what

>> > > could be causing the problem? Thanks.

>> >

>> >

[Guest Adrian S]

Re: Server 2003 R2 takes 20 min to boot.

 

Hi,

 

I seem to be having the same issue , have you found a solution , i seem to

think it's something in SP2 try removing it and see if you still have the

same problems. I have removed SP2 and now dont have the problem, although i

still need a solution .

 

Cheers

 

"quantum" wrote:

> Netdiag /test:dns says everything is ok. I did find a entry missing earlier,

> but I replaced it. (I'll check to make sure the entry I fixed stuck, I

> rebooted it right after I replaced it, but maybe it needed to replicate first)

>

> Dcdiag shows everything ok except for the relpications it misses when

> rebooted.

>

> sysvol is in it's standard path.

>

> There are two broadcom nic's on it teamed to one IP. I guess I could try

> unteaming them, but it worked fine yesterday with them teamed up.

>

> Yes sp2 is installed and updates are current as of today.

>

> Thanks for the help.

>

>

> "Mathieu CHATEAU" wrote:

>

> > Hello,

> >

> > this is normally a network/dns issue.

> >

> > What about:

> > netdiag

> > dcdiag

> >

> > Did you change sysvol from the default path ?

> >

> > Do you have more than one network card ? Is the good one primary ?

> > Did you install the SP2 ?

> >

> > --

> > Cordialement,

> > Mathieu CHATEAU

> > English blog: http://lordoftheping.blogspot.com

> > French blog: http://www.lotp.fr

> >

> >

> > "quantum" <quantum@discussions.microsoft.com> wrote in message

> > news:ECE63B78-278D-4767-8B8B-23F9445E2A3F@microsoft.com...

> > > Over the past few days I have added a few more DC's to our domain and one

> > > of

> > > them is acting pretty funny. It's windows server 2003 R2; it booted fine

> > > while it was being configured and when it was first promoted to a DC and

> > > DNS

> > > (AD intergrated) was installed. Then litteraly over night it will now hang

> > > first on "prepairing network connections" for a few minutes and then on

> > > "Applying computer settings" for at least 10min. When the system finally

> > > boots it acts and works fine, there are no errors in the logs (except for

> > > those pretaining to missing AD replication). I've searched and the only

> > > thing

> > > I could find was in reference to Powerchute, but that is not installed on

> > > the

> > > server (only AD, DNS, Symantec AV, and Adobe reader). Any thoughts as to

> > > what

> > > could be causing the problem? Thanks.

> >

> >