dc hangs 15 minutes before showing login screen

[Guest Admin2008]

All of the dc's in our domain hang for about 15 minutes in the process of

preparing network connections and applying the computer settings before they

show the login screen.

-All dc's are Windows 2003

-All are GCs.

-All have DNS installed.

-All Dcdaig and netdaig tests have no errors.

-Each DC is set to 127.0.0.1 as primary DNS server.

 

Any help would be greatly apprieciated!!!

[Guest Lanwench [MVP - Exchange]]

Re: dc hangs 15 minutes before showing login screen

 

Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> All of the dc's in our domain hang for about 15 minutes in the

> process of preparing network connections and applying the computer

> settings before they show the login screen.

> -All dc's are Windows 2003

> -All are GCs.

> -All have DNS installed.

> -All Dcdaig and netdaig tests have no errors.

> -Each DC is set to 127.0.0.1 as primary DNS server.

 

What's in use for secondary?

I'd set each DC to use its actual LAN IP, not the localhost address, for its

primary DNS. You're making it perform an extra step

>

> Any help would be greatly apprieciated!!!

[Guest Admin2008]

Re: dc hangs 15 minutes before showing login screen

 

Changed each dc's to use own ip for primary dns server. No alternate dns

server specified. After the changes still same problem.

 

"Lanwench [MVP - Exchange]" wrote:

> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> > All of the dc's in our domain hang for about 15 minutes in the

> > process of preparing network connections and applying the computer

> > settings before they show the login screen.

> > -All dc's are Windows 2003

> > -All are GCs.

> > -All have DNS installed.

> > -All Dcdaig and netdaig tests have no errors.

> > -Each DC is set to 127.0.0.1 as primary DNS server.

>

> What's in use for secondary?

> I'd set each DC to use its actual LAN IP, not the localhost address, for its

> primary DNS. You're making it perform an extra step

>

> >

> > Any help would be greatly apprieciated!!!

>

>

>

>

[Guest Lanwench [MVP - Exchange]]

Re: dc hangs 15 minutes before showing login screen

 

Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> Changed each dc's to use own ip for primary dns server. No alternate

> dns server specified. After the changes still same problem.

 

OK - and you rebooted after that, one presumes. Check your event logs &

rsop.msc. And make sure your time zone/DST stuff/clocks are all correct.

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

>>> All of the dc's in our domain hang for about 15 minutes in the

>>> process of preparing network connections and applying the computer

>>> settings before they show the login screen.

>>> -All dc's are Windows 2003

>>> -All are GCs.

>>> -All have DNS installed.

>>> -All Dcdaig and netdaig tests have no errors.

>>> -Each DC is set to 127.0.0.1 as primary DNS server.

>>

>> What's in use for secondary?

>> I'd set each DC to use its actual LAN IP, not the localhost address,

>> for its primary DNS. You're making it perform an extra step

>>

>>>

>>> Any help would be greatly apprieciated!!!

[Guest Admin2008]

Re: dc hangs 15 minutes before showing login screen

 

Adding the other dc/dns server to alternate dns server fixed the problem.

Thanks for your help.

 

"Lanwench [MVP - Exchange]" wrote:

> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> > Changed each dc's to use own ip for primary dns server. No alternate

> > dns server specified. After the changes still same problem.

>

> OK - and you rebooted after that, one presumes. Check your event logs &

> rsop.msc. And make sure your time zone/DST stuff/clocks are all correct.

>

> >

> > "Lanwench [MVP - Exchange]" wrote:

> >

> >> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> >>> All of the dc's in our domain hang for about 15 minutes in the

> >>> process of preparing network connections and applying the computer

> >>> settings before they show the login screen.

> >>> -All dc's are Windows 2003

> >>> -All are GCs.

> >>> -All have DNS installed.

> >>> -All Dcdaig and netdaig tests have no errors.

> >>> -Each DC is set to 127.0.0.1 as primary DNS server.

> >>

> >> What's in use for secondary?

> >> I'd set each DC to use its actual LAN IP, not the localhost address,

> >> for its primary DNS. You're making it perform an extra step

> >>

> >>>

> >>> Any help would be greatly apprieciated!!!

>

>

>

>

[Guest Lanwench [MVP - Exchange]]

Re: dc hangs 15 minutes before showing login screen

 

Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> Adding the other dc/dns server to alternate dns server fixed the

> problem. Thanks for your help.

 

Hmm - that shouldn't be necessary. It's fine to have it, but AFAIK it really

shouldn't be necessary...*unless* you're having replication or DNS problems.

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

>>> Changed each dc's to use own ip for primary dns server. No

>>> alternate dns server specified. After the changes still same

>>> problem.

>>

>> OK - and you rebooted after that, one presumes. Check your event

>> logs & rsop.msc. And make sure your time zone/DST stuff/clocks are

>> all correct.

>>

>>>

>>> "Lanwench [MVP - Exchange]" wrote:

>>>

>>>> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

>>>>> All of the dc's in our domain hang for about 15 minutes in the

>>>>> process of preparing network connections and applying the computer

>>>>> settings before they show the login screen.

>>>>> -All dc's are Windows 2003

>>>>> -All are GCs.

>>>>> -All have DNS installed.

>>>>> -All Dcdaig and netdaig tests have no errors.

>>>>> -Each DC is set to 127.0.0.1 as primary DNS server.

>>>>

>>>> What's in use for secondary?

>>>> I'd set each DC to use its actual LAN IP, not the localhost

>>>> address, for its primary DNS. You're making it perform an extra

>>>> step

>>>>

>>>>>

>>>>> Any help would be greatly apprieciated!!!

[Guest Admin2008]

Re: dc hangs 15 minutes before showing login screen

 

The reason that I thought that was the fix was because of this article:

http://support.microsoft.com/kb/945765

 

What steps do you think I should take now? By the way thanks for your help

on this issue.

 

"Lanwench [MVP - Exchange]" wrote:

> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> > Adding the other dc/dns server to alternate dns server fixed the

> > problem. Thanks for your help.

>

> Hmm - that shouldn't be necessary. It's fine to have it, but AFAIK it really

> shouldn't be necessary...*unless* you're having replication or DNS problems.

>

> >

> > "Lanwench [MVP - Exchange]" wrote:

> >

> >> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> >>> Changed each dc's to use own ip for primary dns server. No

> >>> alternate dns server specified. After the changes still same

> >>> problem.

> >>

> >> OK - and you rebooted after that, one presumes. Check your event

> >> logs & rsop.msc. And make sure your time zone/DST stuff/clocks are

> >> all correct.

> >>

> >>>

> >>> "Lanwench [MVP - Exchange]" wrote:

> >>>

> >>>> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> >>>>> All of the dc's in our domain hang for about 15 minutes in the

> >>>>> process of preparing network connections and applying the computer

> >>>>> settings before they show the login screen.

> >>>>> -All dc's are Windows 2003

> >>>>> -All are GCs.

> >>>>> -All have DNS installed.

> >>>>> -All Dcdaig and netdaig tests have no errors.

> >>>>> -Each DC is set to 127.0.0.1 as primary DNS server.

> >>>>

> >>>> What's in use for secondary?

> >>>> I'd set each DC to use its actual LAN IP, not the localhost

> >>>> address, for its primary DNS. You're making it perform an extra

> >>>> step

> >>>>

> >>>>>

> >>>>> Any help would be greatly apprieciated!!!

>

>

>

>

[Guest Lanwench [MVP - Exchange]]

Re: dc hangs 15 minutes before showing login screen

 

Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> The reason that I thought that was the fix was because of this

> article: http://support.microsoft.com/kb/945765

>

> What steps do you think I should take now?

 

I think you should stick with what you did. I suspect I was insufficiently

caffeinated when I wrote - you did the right thing (as per the KB article).

> By the way thanks for your

> help on this issue.

 

You're most welcome - glad it's all working.

 

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

>>> Adding the other dc/dns server to alternate dns server fixed the

>>> problem. Thanks for your help.

>>

>> Hmm - that shouldn't be necessary. It's fine to have it, but AFAIK

>> it really shouldn't be necessary...*unless* you're having

>> replication or DNS problems.

>>

>>>

>>> "Lanwench [MVP - Exchange]" wrote:

>>>

>>>> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

>>>>> Changed each dc's to use own ip for primary dns server. No

>>>>> alternate dns server specified. After the changes still same

>>>>> problem.

>>>>

>>>> OK - and you rebooted after that, one presumes. Check your event

>>>> logs & rsop.msc. And make sure your time zone/DST stuff/clocks are

>>>> all correct.

>>>>

>>>>>

>>>>> "Lanwench [MVP - Exchange]" wrote:

>>>>>

>>>>>> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

>>>>>>> All of the dc's in our domain hang for about 15 minutes in the

>>>>>>> process of preparing network connections and applying the

>>>>>>> computer settings before they show the login screen.

>>>>>>> -All dc's are Windows 2003

>>>>>>> -All are GCs.

>>>>>>> -All have DNS installed.

>>>>>>> -All Dcdaig and netdaig tests have no errors.

>>>>>>> -Each DC is set to 127.0.0.1 as primary DNS server.

>>>>>>

>>>>>> What's in use for secondary?

>>>>>> I'd set each DC to use its actual LAN IP, not the localhost

>>>>>> address, for its primary DNS. You're making it perform an extra

>>>>>> step

>>>>>>

>>>>>>>

>>>>>>> Any help would be greatly apprieciated!!!

[Guest Admin2008]

Re: dc hangs 15 minutes before showing login screen

 

Well hey man thanks for the help!!!

 

"Lanwench [MVP - Exchange]" wrote:

> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> > The reason that I thought that was the fix was because of this

> > article: http://support.microsoft.com/kb/945765

> >

> > What steps do you think I should take now?

>

> I think you should stick with what you did. I suspect I was insufficiently

> caffeinated when I wrote - you did the right thing (as per the KB article).

>

> > By the way thanks for your

> > help on this issue.

>

> You're most welcome - glad it's all working.

>

>

> >

> > "Lanwench [MVP - Exchange]" wrote:

> >

> >> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> >>> Adding the other dc/dns server to alternate dns server fixed the

> >>> problem. Thanks for your help.

> >>

> >> Hmm - that shouldn't be necessary. It's fine to have it, but AFAIK

> >> it really shouldn't be necessary...*unless* you're having

> >> replication or DNS problems.

> >>

> >>>

> >>> "Lanwench [MVP - Exchange]" wrote:

> >>>

> >>>> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> >>>>> Changed each dc's to use own ip for primary dns server. No

> >>>>> alternate dns server specified. After the changes still same

> >>>>> problem.

> >>>>

> >>>> OK - and you rebooted after that, one presumes. Check your event

> >>>> logs & rsop.msc. And make sure your time zone/DST stuff/clocks are

> >>>> all correct.

> >>>>

> >>>>>

> >>>>> "Lanwench [MVP - Exchange]" wrote:

> >>>>>

> >>>>>> Admin2008 <Admin2008@discussions.microsoft.com> wrote:

> >>>>>>> All of the dc's in our domain hang for about 15 minutes in the

> >>>>>>> process of preparing network connections and applying the

> >>>>>>> computer settings before they show the login screen.

> >>>>>>> -All dc's are Windows 2003

> >>>>>>> -All are GCs.

> >>>>>>> -All have DNS installed.

> >>>>>>> -All Dcdaig and netdaig tests have no errors.

> >>>>>>> -Each DC is set to 127.0.0.1 as primary DNS server.

> >>>>>>

> >>>>>> What's in use for secondary?

> >>>>>> I'd set each DC to use its actual LAN IP, not the localhost

> >>>>>> address, for its primary DNS. You're making it perform an extra

> >>>>>> step

> >>>>>>

> >>>>>>>

> >>>>>>> Any help would be greatly apprieciated!!!

>

>

>

>