Discussion Locked

Windows 2000 Server Slow after 7 days

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Our windows 2000 server has been working without problems since may/june 2000. But in the last few weeks the server runs very slow after 7 days and gives an event error 2019 just before a warning 5781. If the server is re-booted all is fine for another 7 days. The problem is always over the week end when the server is not being used. Users cannot logon first thing monday morning, but PC's that are logged on are still connected, but data transfer is very slow.

7 replies

by fgarber

General Troubleshooting
In general, these error messages are logged because the Netlogon service does not receive a "success" message from the DNS server that owns the zones of the records that are being registered. There are several reasons why the Netlogon service does not receive a "success" message:
Domain controller configuration: DNS server entries in the Transmission Control Protocol/Internet Protocol (TCP/IP) properties of the domain controller are not properly configured.

Connectivity: This domain controller does not have Internet Protocol (IP), or Transmission Control Protocol/User Datagram Protocol (TCP/UDP), connectivity to the DNS servers that own the zones to which records need to be registered or deregistered.

DNS server configuration: The DNS server cannot accept dynamic updates or is not configured to accept dynamic updates, as described in the Request For Comments (RFC) 2136 specification. If the DNS server that is used by the domain controller is not authoritative for the zones to which the Netlogon service is attempting to register or deregister, the DNS server must be able to provide (to this domain controller) the IP address of the DNS servers that are authoritative for the affected zones.

You might want to diagnose this by trying to ping the DNS server from the 2000 box if they are on different boxes. If they are on the same box check the dns and its database.

by data-dr

Good suggestions from the above posting, but I'd add this:

Check your firewall to be sure the server hasn't been compromised and is being used by outside sources for reasons unknown. One common hack is to take control of a server on someone's network and use it to launch scans against other networks to hide the hackers identity.

Just a thought.

by sgraham

In addition to the prior postings, the Event ID 2019 suggests that Nonpaged pool pages are not being paged out to the paging file. Most likely an application on your systems is making incorrect system calls, and is using up all the allocated nonpaged pool. It could even be the netlogon service itself.

You need to monitor the applications running on the system, and their respective nonpaged pool allocation. I recommend using PerfMon or even better, PMON.exe from the Win2K Resource Kit.

My $0.02

This discussion is closed to new replies.