Re: What happened after a simple reboot?

"sektor" <sektor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2FF7F474-9000-43DD-9A24-A782D5D64240@xxxxxxxxxxxxxxxx
Some recent patches came out. I read all the details and patched my DC and
then rebooted. No big deal I thought.

the first thing that caught my attention was how long it took for the
login
screen to pop up at the terminal. Probably a good 5 minutes which
concerned
me. During that time, i tried to RDP into the DC and got a message saying
something like "the specified domain could not be found." Not cool at all.

No big deal IF it eventually works AND next boot is not also slower
than expected.

The reason for the reboot after upgrade is that certain update functions
must be performed before certain services, drivers, and dlls are loaded
into memory.

The login screen eevntually came up and I could then RDP into it. I
immediately checked the Event viewer logs and say all sorts of things in
there.

Here are some of the EventID's that popped up:

SYSTEM LOG:

WARNING: 5781-Netlogon
ERROR: 1059-DhcpServer
WARNING: 40960-LSASRV

What is curious is that the DhcpServer error says it failed to see a
directory server for auhtorization, even though this DC is running DHCP
and
DNS for my network.

It happens when the network services get started in other than
the expected order (or with delays), which really shouldn't happen
due to dependency settings in the registry, but nevertheless apparently
does happen.

In the Application Event viewer, I had the infamous: 1058 and 1030 errors
(which bugs the crud out of me because they always seem to pop up when I
make
a change in GP.)

So, this DC has been humming along nicely until today and now im trying to
figure out what caused this.

Is there any chance that because of the 1058 and 1030 errors regarding GPO
and permission denied...could that delay the startup of the DC, causing
the
errors I see in my System log?

Reboot and see what happens when no updates are pending.

Like I said, i've had some 1058 and 1030 errors on this DC before, but
i've
never had anything in the SYSTEM log like I did today.

Anyone have suggestions?
I just want to know what happened so I can correct it in the future. I
like
to know what is going on with my systems.

Run DCDiag a lot. Generally your DCs are ok if DCDiag passes with
NO errors and NO warnings and you experience no significant difficulties.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Thanks,

Sektor


.

Relevant Pages

  • Re: STARTUP PROGRAMS
    ... detective work. ... key to unlocking what is wrong. ... Sometimes it's best to clear all logs, do a reboot and check. ... XP should not have ANY errors in it's System log, ...
    (microsoft.public.windowsxp.general)
  • Re: What happened after a simple reboot?
    ... I had to put more updates on and reboot...same thing happened. ... wait for a time when their are no updates and reboot and see what happens. ... All my XP machines are fully patched and I have a GPO setup to disable the ... errors I see in my System log? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Blue screen
    ... the error will appear in the system log under savedump ... to stop the reboot from occuring during a stop, ... the computer restarts. ...
    (microsoft.public.windowsxp.general)
  • How to axs the system log??
    ... "The next time it does this, go into your control panel\administrative ... that correspond to the time of your reboot. ... or the problem\conflict if in the system log. ... there is a log file or something that I can look at to see this same thing ...
    (microsoft.public.windowsxp.general)
  • RE: How to axs the system log??
    ... > "The next time it does this, go into your control panel\administrative ... > tools\event viewer and then click either the system, or applications log, on ... > that correspond to the time of your reboot. ... or the problem\conflict if in the system log. ...
    (microsoft.public.windowsxp.general)