HELP! Net Logon service not starting.

[rc]

Hello,

Server-1 - WIN2003 Server, AD, DC, DNS Server

Server-2 - WIN2003 Server, AD, DC

Server-3 - WIN2003 Server, AD, DC, SQL Server

We had the power go out this morning and although the servers are on a UPS,
after about 20 minutes without power, I decided to shut the servers down
(the power outage actually lasted 70 minutes). After the power came back
on, I started up the network.

Server-1 & Server-2 came up fine. Server-3 (running SQL server) indicated a
service not started correctly.

The system event log (server-3):

Event ID: 7023, "The Net logon service terminated with the following error"
bla, bla, bla....

The application log (server-3):

Event ID: 1053, "Windows cannot determine the computer or user name (Access
is denied) Group Policy processing is aborted"

If I try to manually start the Net logon service, I get the message "Could
not start the Net Logon service on Local Computer". Of course, SQL server
will not start either (I believe it is dependant on the net logon service).

All file sharing & printing on the network has been unaffected, and works
fine.

Everything was working fine last week!!

Any insight would be helpful

Thank you

[J.C. Hornbeck [MSFT]]

Unfortunately the 'bla bla bla' is going to be pretty important in resolving
the Netlogon 7023 error. Can you post the description and the data section
from this event?

--
J.C. Hornbeck, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.

"rc" <n...@email.com> wrote in message
news:uUyqsdc...@tk2msftngp13.phx.gbl...

> Hello,
>
>
>
> Server-1 - WIN2003 Server, AD, DC, DNS
>

[rc]

Ok, sorry

The data section is blank (greyed out).

Event ID: 7023
"The Net logon service terminated with the following error %%3221225572"

Thanks

"J.C. Hornbeck [MSFT]" <jcho...@online.microsoft.com> wrote in message
news:%23AFkYkc...@tk2msftngp13.phx.gbl...

[doug]

Well, you have to bla, bla, bla in order to get this
working again.

Please post the error message. You wouldn't go to the
doctor and say "Well, I have a pain in my bla, bla...fix
it" and expect him to know what to do.

doug

>.
>

[rc]

Ok,

More info..

I've run the 'netdiag' command on each server. The results are as follows:

Server-1 = everything passed

Server-2 = everything passed

Server-3 = everything passed except the following:

DNS test . : Failed

[FATAL] File \config\netlogon.dns contains invalid DNS entries.
[FATAL] No DNS servers have the DNS records for this DC registered.

Trust relationship test : Failed

[FATAL] Cannot get list of trusted domains for domain MYDOMAIN from
Netlogon. [RPC

_NT_UNKNOWN_IF]

[FATAL] Cannot get secure channel status for domain 'MYDOMAIN' from
Netlogon. [RPC

_S_UNKNOWN_IF]

So, I believe my problem is a DNS problem (oh' joy!).

Any suggestions?

Thank you

"rc" <n...@email.com> wrote in message
news:uUyqsdc...@tk2msftngp13.phx.gbl...

[rc]

Hello,

More info #2

From the command line I typed "sc query netlogon" , from Server-3, and the
results are a follows:

SERVICE_NAME: netlogon

TYPE : 20 WIN32_SHARE_PROCESS

STATE : 1 STOPPED

(NOT_STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN))

WIN32_EXIT_CODE : -1073741724 (0xc0000064)

SERVICE_EXIT_CODE : -1073741724 (0xc0000064)

CHECKPOINT : 0x0

WAIT_HINT : 0x0

Hope this is helpful.

Thank you

"rc" <n...@email.com> wrote in message
news:uUyqsdc...@tk2msftngp13.phx.gbl...

[rc]

Hello,

Never did figure out how to correct the original problem of the 'Net Logon'
service not starting. SQL Server is pretty much the core of our business and
I couldn't wait, so I took an alternate plan.

-Moved the SQL server to Server-1

-Restored the Database form the last back up.

-Re-configured all SQL apps to look to the new location.

This whole process only took a couple of hours and now we are back up and
running.

As for Server-3, I finally ended up demoting the computer from a DC to a
member server via 'dcpromo' command (since it never was logging on to AD, I
had to use the '/ forceremoval' switch).

Now Server-3 is working flawlessly as a member server. Even SQL Server loads
without any problems.

I will probably move the database back over to Server-3 next week so it can
be running on a dedicated server.

Thanks

"rc" <n...@email.com> wrote in message
news:uUyqsdc...@tk2msftngp13.phx.gbl...