Question : Netlogon does not start automaticly. Causes chain reaction of services not starting

Hello,

I have exchange 2003 loaded on win server 2003 r2 sp2. This morning after both pushing End Point client and applying microsofts updates and restarting, exchange would not come back up.

I've uninstalled symantic endpoint and mail security from the server

The point i am at now Is netlogon will not start automaticly when the server boots causing every service that depends on it to also not start. I CAN start it manually but I cannot start all my exchange services from that point. (Exchange System Atendend will not stay started.)

First error code after reboot is event id 40960

Thanks for Reading.

Answer : Netlogon does not start automaticly. Causes chain reaction of services not starting

You might want to read this article.

http://articles.techrepublic.com.com/5100-10877_11-6107842-2.html

RPC depends upon the Workstation Service. You might want to check the permissions on that first and make sure that is started.

I am still working out the authentication details, myself. There are three forms of authentication. The first one is LMhash. The second is NTLMhash. The third is Kerberos. Each one is a step in an authentication evolution. By default a 2003 server uses Kerberos. R2 probably only uses Kerberos.

It sounds like your client was using NTLMhash to try and authenticate with the domain controller. That is a pre-2000 method of authenticating to a domain controller. (I am just guessing why Netlogon and other services were disabled when I say), In the process of trying to authenticate with kerberos, it tried so hard that if flooded the nic and services started to shut down. By default, on XP boxes, these services should have been trying to authenticate by using kerberose. Below is a model of the NTLM authentication process and how ASP uses it. Also there is a model for Kerberose. You might have downloaded something that uses NTLM and changed the default permissions on these service applets.

http://msdn2.microsoft.com/en-us/library/aa480475.aspx

Why, you ask, is your box trying to use NTLM for authentication to the domain controller? That's a pretty good question since the documentation of authentication doesn't really go deep into detail. I am still studying this.