NETLOGON Service fails to start automatically upon server reboot

Maybe this solution may help you:

The Netlogon service does not start and event IDs 2114 and 7024 are logged in Windows Server 2003 and in Windows 2000 Server

http://support.microsoft.com/kb/269375/en-us

Please view the following thread as it should have the info you need. Otherwise please post back.
https://www.experts-exchange.com/questions/22828193/NETLOGON-5722-ADMIN.html

Thanks
0xSaPx0

You said: "I have searched the net and all I could find was that problem with error codes 2114 and 7024. This is not the same as mine" Sorry but, have you tried already the solution in this microsoft document ?

Have you seend this one (look for 2003 server part of it)?
http://support.microsoft.com/kb/109626/en-us

you need to run the workstation service as the netlogon service depends on that
does the services start manually?

is your domain controller a stand alone or not ?
do you also have a windows server 2000 machine running in your network?

DCenaculo:

I went to that article and it states:
Windows Server 2003, Windows XP Professional and Windows 2000 Server versions
The version of Netlogon.dll that has tracing included is installed by default. To enable debug logging, set the debug flag that you want in the registry and restart the service by using the following steps: 1. Start the Regedt32 program.
2. Delete the Reg_SZ value of the following registry entry, create a REG_DWORD value with the same name, and then add the 2080FFFF hexadecimal value.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DBFlag
3. At a command prompt, type net stop netlogon, and then type net start netlogon. This enables debug logging.
4. To disable debug logging, change the data value to 0x0 in the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DBFlag
5. Quit Regedt32.
6. Stop Net Logon, and then restart Net Logon.
Note On Windows Server 2003-based computers, you can use the following Group Policy to configure the log file size:
\Computer Configuration\Administrative Templates\System\Net Logon\Maximum Log File Size
Note As an alternate method, you can set the dbflag without using the registry. To do this run the following command from a command prompt:

nltest /dbflag:0x2080ffff

After you finish debugging, you can run the nltest /dbflag:0x0 command from a command prompt to reset the debug flag to 0. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

But the first registry value it refers to is not there?!
Could that be the Problem? Is it possible for someone to send me the registry keys that SHOULD be there?

And the Workstation service Is and Does start automatically. I am able to start NETLOGON manually, but just doesnt start by itself

I'll try too see this for/with you today, but you only have one DC ? You should have two at least :)

I have 2 DC's and both are GC servers as well. (Read somewhere that this may clear up some errors in my event log but hasnt).

The problem started after installing Backup Exec, worth mentioning those services dont start automtically either. Have called support and they cant COMPLETLY get it working.. So Im guess the two probably go hand-in-hand.

Have sent a mail to the company saying Im taking the server down at 12pm EST time for 1 hr to uninstall/reinstall the Backup program to see if this fixes..

Will keep you posted, but would appreciate it if anyone can come up with other solutions/possible causes

Thank you so much

Did you compare the registry of the DC with problems with the other one that I supose has netlogon starting ok ?

Create a file with reg extension. Example: dbflag.reg with notepad and copy paste there this text between the lines (not the lines):
----------------------------------------------------------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters]
"DBFlag"=dword:2080ffff
-----------------------------------------------------------------------------------------------------

Double click the file and it will create these entry for you.

Ok so I just compared the two.. both look exzctly the same.

This command will create that debug entry also :)

nltest /dbflag:0x2080ffff

Ok :)

Well Reinstalled Backup Exec - All is well!
Thanks anyway for all your help guys!!!!

We're wellcome. Thanks for sharing your prob with us :)

Closed, 500 points refunded.
Vee_Mod
Experts Exchange Moderator