Question : net logon and computer browser shutdown automatically

Hi,

I'm trying to figure out this problem with services shutting down by themselves several times every day.  The primary services that are doing it are net logon and computer browser.  We used to have Exchange 2000 server running, and several exchange services would shutdown and require us to manually restart them as well, but we uninstalled exchange for other reasons..  What are some logical troubleshooting steps?  

Thanks - Trevor

Answer : net logon and computer browser shutdown automatically

ok, is this server a domain controller? It looks like your having active directory issues.  Check to see where your master roles are located, you may have to move them:
http://is-it-true.org/nt/nt2000/atips/atips56.shtml

Go to a command prompt and type this:
netdom query fsmo

it will return a list of the 5 roles and who they belong to. that would help in finding out why your having ldap and global catalog issues
*****

Error messages=

This below can be ignored, its just telling you that when you remote in it doesn't have the drivers to map your printers
Event Type:     Error
Event Source:     TermServDevices
Event Category:     None
Event ID:     1106
*****

below Netlogon errors:
Event Type:     Warning
Event Source:     NETLOGON
Event Category:     None
Event ID:     5781

http://support.microsoft.com/default.aspx?scid=kb;EN-US;259277
Excerpt:
NOTE: A common cause for these errors is that a domain controller references itself as a primary DNS server in its TCP/IP properties. When the domain controller starts in this configuration, the Netlogon service may start before the DNS service starts. Because the Netlogon service must register records in DNS and the DNS service is not yet available, errors may occur. In this situation, you can safely ignore the errors because the Netlogon service will again try to register the records in approximately five minutes, at which time it will be successful. However, there are two ways to avoid the errors in this scenario: • Make sure that domain controllers do not reference themselves as a primary DNS server in their TCP/IP properties.
• Configure the Netlogon service to depend on the DNS service. This will cause the Netlogon service to start after the DNS service starts. To do this, run REGEDT32, and go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon
In the right pane, double-click the value DependOnService and add DNS to the next available blank line. Click OK and exit Registry Editor. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:


Seems like a couple of different problems here, first thing first check out the DNS first, then check out your schema roles as the links show.