Long reboot

  • Thread starter Thread starter r. wales
  • Start date Start date
R

r. wales

Guest
I have a win 2k3 server that takes a long time to reboot. It is fully
patched. This is not new or recent behavior and as far as I can tell has
always been like this. As the server boots up, it spends around 11 minutes
'Preparing Network Connections'. This is a lot more time than our other
servers spend during this same phase. Any thoughts or ideas? It's more of a
nuisance than a problem, I just want to see if anyone has any ideas on how to
fix it or if I will just have to live with it.

Thanks.
 
Re: Long reboot


"r. wales" <rwales@discussions.microsoft.com> wrote in message
news:A31FFE88-205E-4E9B-B4A1-08E1683FA59A@microsoft.com...
>I have a win 2k3 server that takes a long time to reboot. It is fully
> patched. This is not new or recent behavior and as far as I can tell has
> always been like this. As the server boots up, it spends around 11
> minutes
> 'Preparing Network Connections'. This is a lot more time than our other
> servers spend during this same phase. Any thoughts or ideas? It's more
> of a
> nuisance than a problem, I just want to see if anyone has any ideas on how
> to
> fix it or if I will just have to live with it.
>
> Thanks.

This is often caused by inappropriate DNS settings.
 
Re: Long reboot



"Pegasus (MVP)" wrote:

>
>
> This is often caused by inappropriate DNS settings.
>

This particular server is our primary DC and primary DNS for our network.
It currently points to itself as its primary DNS with no secondary listed.
Could this be the setting you were referring to, or is it some setting deeper
inside DNS?
 
Re: Long reboot

Hello,

Did you change the NTDS default location when promoting the dc ?



--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"r. wales" <rwales@discussions.microsoft.com> wrote in message
news:18B70E5D-79D2-4DE6-BD45-8DB7F7229352@microsoft.com...
>
>
> "Pegasus (MVP)" wrote:
>
>>
>>
>> This is often caused by inappropriate DNS settings.
>>
>
> This particular server is our primary DC and primary DNS for our network.
> It currently points to itself as its primary DNS with no secondary listed.
> Could this be the setting you were referring to, or is it some setting
> deeper
> inside DNS?
 
Re: Long reboot

Not sure. Everything was already in place when I was hired on. It was all
done by a part time outside guy. I have been wading through trying to clean
things up ever since I got here.

"Mathieu CHATEAU" wrote:

> Hello,
>
> Did you change the NTDS default location when promoting the dc ?
>
>
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "r. wales" <rwales@discussions.microsoft.com> wrote in message
> news:18B70E5D-79D2-4DE6-BD45-8DB7F7229352@microsoft.com...
> >
> >
> > "Pegasus (MVP)" wrote:
> >
> >>
> >>
> >> This is often caused by inappropriate DNS settings.
> >>
> >
> > This particular server is our primary DC and primary DNS for our network.
> > It currently points to itself as its primary DNS with no secondary listed.
> > Could this be the setting you were referring to, or is it some setting
> > deeper
> > inside DNS?
>
>
 
Re: Long reboot

check where the sysvol share point to


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"r. wales" <rwales@discussions.microsoft.com> wrote in message
news:53FA1C3D-86E2-4425-8ABA-387E0B2508DA@microsoft.com...
> Not sure. Everything was already in place when I was hired on. It was
> all
> done by a part time outside guy. I have been wading through trying to
> clean
> things up ever since I got here.
>
> "Mathieu CHATEAU" wrote:
>
>> Hello,
>>
>> Did you change the NTDS default location when promoting the dc ?
>>
>>
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> http://lordoftheping.blogspot.com
>>
>>
>> "r. wales" <rwales@discussions.microsoft.com> wrote in message
>> news:18B70E5D-79D2-4DE6-BD45-8DB7F7229352@microsoft.com...
>> >
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >>
>> >>
>> >> This is often caused by inappropriate DNS settings.
>> >>
>> >
>> > This particular server is our primary DC and primary DNS for our
>> > network.
>> > It currently points to itself as its primary DNS with no secondary
>> > listed.
>> > Could this be the setting you were referring to, or is it some setting
>> > deeper
>> > inside DNS?
>>
>>
 
Re: Long reboot

What am I looking for?

"Mathieu CHATEAU" wrote:

> check where the sysvol share point to
>
 
Re: Long reboot

Start / Run / CMD
net share
post back the lines about sysvol and netlogon


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"r. wales" <rwales@discussions.microsoft.com> wrote in message
news:862F9DA0-1D8D-4865-8132-0C69382C7D92@microsoft.com...
> What am I looking for?
>
> "Mathieu CHATEAU" wrote:
>
>> check where the sysvol share point to
>>
>
 
Re: Long reboot

Third-party apps running as services with Automatic start-up can do this.

The DC I inherited took 45 minutes to get through this stage until I removed
the Powerchute UPS Monitor software.
--
Newell White


"Mathieu CHATEAU" wrote:

> Start / Run / CMD
> net share
> post back the lines about sysvol and netlogon
>
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "r. wales" <rwales@discussions.microsoft.com> wrote in message
> news:862F9DA0-1D8D-4865-8132-0C69382C7D92@microsoft.com...
> > What am I looking for?
> >
> > "Mathieu CHATEAU" wrote:
> >
> >> check where the sysvol share point to
> >>
> >
>
>
 
Re: Long reboot

If you have Powerchute UPS Monitor software installed then ensure that you
don't have version 6 as there is a very well known problem with it causing
long boots (something to do with the Java engine I seem to remember).
If you do have version 6 the remove NOW and get the version 7 from the APC
web site.


"Newell White" <NewellWhite@discussions.microsoft.com> wrote in message
news:021159F6-47B4-449A-BF4D-7CB6EEFC3FE6@microsoft.com...
> Third-party apps running as services with Automatic start-up can do this.
>
> The DC I inherited took 45 minutes to get through this stage until I
removed
> the Powerchute UPS Monitor software.
> --
> Newell White
>
>
> "Mathieu CHATEAU" wrote:
>
> > Start / Run / CMD
> > net share
> > post back the lines about sysvol and netlogon
> >
> >
> > --
> > Cordialement,
> > Mathieu CHATEAU
> > http://lordoftheping.blogspot.com
> >
> >
> > "r. wales" <rwales@discussions.microsoft.com> wrote in message
> > news:862F9DA0-1D8D-4865-8132-0C69382C7D92@microsoft.com...
> > > What am I looking for?
> > >
> > > "Mathieu CHATEAU" wrote:
> > >
> > >> check where the sysvol share point to
> > >>
> > >
> >
> >
 
Re: Long reboot

*shudder* Powerchute 6.x
.... so aweful.. definately upgrade that to 7.x

:-)
Coraleigh Miller


"NeilH" <neil@nospam.uk> wrote in message
news:%23DPaMwt6HHA.1204@TK2MSFTNGP03.phx.gbl...
> If you have Powerchute UPS Monitor software installed then ensure that you
> don't have version 6 as there is a very well known problem with it causing
> long boots (something to do with the Java engine I seem to remember).
> If you do have version 6 the remove NOW and get the version 7 from the APC
> web site.
>
>
> "Newell White" <NewellWhite@discussions.microsoft.com> wrote in message
> news:021159F6-47B4-449A-BF4D-7CB6EEFC3FE6@microsoft.com...
>> Third-party apps running as services with Automatic start-up can do this.
>>
>> The DC I inherited took 45 minutes to get through this stage until I
> removed
>> the Powerchute UPS Monitor software.
>> --
>> Newell White
>>
>>
>> "Mathieu CHATEAU" wrote:
>>
>> > Start / Run / CMD
>> > net share
>> > post back the lines about sysvol and netlogon
>> >
>> >
>> > --
>> > Cordialement,
>> > Mathieu CHATEAU
>> > http://lordoftheping.blogspot.com
>> >
>> >
>> > "r. wales" <rwales@discussions.microsoft.com> wrote in message
>> > news:862F9DA0-1D8D-4865-8132-0C69382C7D92@microsoft.com...
>> > > What am I looking for?
>> > >
>> > > "Mathieu CHATEAU" wrote:
>> > >
>> > >> check where the sysvol share point to
>> > >>
>> > >
>> >
>> >
>
>
 
Re: Long reboot

Hello,
"r. wales" <rwales@discussions.microsoft.com> schrieb im Newsbeitrag
news:A31FFE88-205E-4E9B-B4A1-08E1683FA59A@microsoft.com...
>I have a win 2k3 server that takes a long time to reboot. It is fully
> patched. This is not new or recent behavior and as far as I can tell has
> always been like this. As the server boots up, it spends around 11
> minutes
> 'Preparing Network Connections'. This is a lot more time than our other
> servers spend during this same phase. Any thoughts or ideas? It's more
> of a
> nuisance than a problem, I just want to see if anyone has any ideas on how
> to
> fix it or if I will just have to live with it.

if you have a second AD integrated DNS server, let them point to each other
in their TCP/IP settings. This could help, as long as the other server is on
while one is booting.
Best greetings from Germany
Olaf
 
Back
Top