slow login - Net Logon service not starting

[Matt Leonard]

I manage a small 10 node network with a Win2K DC. I noticed several days ago
after a power failure and subsequent reboot of the server that it takes what
seems like forever for the server to present the login dialog, and after
logging in, it takes forever again for the server desktop to appear. First
indication that something was wrong was that the "At least one service or
driver failed..." dialog appeared at the server after the power failure. The
average boot-up time is 10 mins., where before it was 2-3 mins. Second
indication that something was wrong was the phone calls that I received from
clients not able to access mapped drives. They get the following message:
"H:\ is not accessible. The system detected a possible attempt to compromise
security...".

The System event log on the server yields the following error: "The Net
Logon service terminated with service-specific error 2138." If I start the
service everyone can access their mapped drives.

The problem seems to be that the Net Logon service won't start automatically
upon reboot as it's supposed to. Has anyone experienced this before? Thanks
in advance.
Matt

 

[Marina Roos]

How many nics in the server? Which service or driver didn't load? What
errormessages do you see in the eventlogs?
What OS on the clients? Does the ipconfig/all from the clients show that
everything is pointing to the server-IP?

Marina

 

[Matt Leonard]

1 Nic in the server. The Net Logon service and Workstation service (Event
ID's 7024 and 2138 respectively) aren't starting automatically, even though
they're both set to do so in Services. Exact error messages follow:

Source: NETLOGON
Time: 11:01:07 AM
Category: None
Type: Error
EventID: 2138

Description:
The Workstation service has not been started.

Source: Service Control Manager
Time: 11:01:07 AM
Category: None
Type: Error
EventID: 7024

Description:
The Net Logon service terminated with service-specific error 2138.

The OS's of the clients are NT 4.0 and XP. Ipconfig from all clients reveals
nothing out of the ordinary, and all IP settings are set accurately and
aside from the IP address, none of the settings have changed since the new
server implementation (a year ago). After starting the Net Logon service on
the server, no problems are reported from the clients.

 

[Marina Roos]

Is the server and are the clients fully patched?

Marina

 

[Matt Leonard]

Yes, that was one of the first things I did...that is, if you mean
installing the latest MS updates.

 

[Marina Roos]

Hi Matt,

This is what I found on
http://www.eventid.net/display.asp?eventid=2138&source=

Nikolay Mamaev (Last update 10/8/2003):
This event take place if the dependencies of Netlogon service are not set
correctly, i.e. Netlogon doesn't depend on Workstation service. To correct
it, I have followed the next steps:
1. Start Registry Editor (Regedt32.exe).
2. Locate and then click the "DependOnService" value under the following key
in the registry:
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon"
3. On the Edit menu, click Multi String, add line "LanmanWorkstation", and
then click OK.
4. Quit Registry Editor.

Marina