Windows 2000 Server DNS problem

[sierrapacific]

Currently running Windows 2000 Server with Exchange 5.5 No changes have been made to the system, besides a power outage that was protected by a battery back-up system, so shouldn't be any problem there. However, the DNS service will run for about 2 sometimes 4 hours and then quit and then I can't access the server through network neighborhood or remote desktop. It is a domain controller. Not sure what is going on. Any ideas? I did have an error about RPC, but not sure why.

 

[GlenJohnson]

How do you solve the problem, reboots? What kind of error messages do you get? Need just a little more info. Good luck.

Glen A. Johnson
If you're from the Illinois, Wisconsin or Florida area, check out Tek-Tips in Chicago IL
To get the best answers to your questions, check out faq950-5848

 

[sierrapacific]

Yes, reboots work. I used to think it was a DNS problem, but now I think it is a AD problem. The DNS server is now running fine, however, I am not allowed to browse the server from the network. It says: The remote computer is not available. Some of the erros in event viewer are:

Event ID 5000
Source LsaSrv
Category Devices

The security package Negotiate generated an exception. The package is now disabled. The exception information is the data.

Event ID 3034
Source MRxSmb
Category None

The redirector was unable to initialize security context or query context attributes.

 

[netometer]

Hi!
Here is what I found on MS support (Article ID : 328948, Last Review : June 13, 2005, Revision : 3.0):

http://support.microsoft.com/kb/328948

I would suggest to install/reinstall SP4 for windows and if the problem still exists - deinstall and install the DNS service. Reboot after deinstalling it. If that is the only one Domain Controller with AD integrated zone that is not a problem. Before you proceed with deinstalling the DNS server in that case backup Active Directory. After installing again the DNS service - run netdiag /fix in order to create the server records again. I've had this problem and deinstalling/installing the DNS service fixed the problem. In my case there was only one DC so I had to go through the whole procedure.

Good Luck!

NetoMeter

http://www.netometer.net

 

[GlenJohnson]

Neto is correct. Check out the article he posted, it's the best one I found. Good luck.

Glen A. Johnson
If you're from the Illinois, Wisconsin or Florida area, check out Tek-Tips in Chicago IL
To get the best answers to your questions, check out faq950-5848

 

[sierrapacific]

So, should I deinstall/reinstall the DNS service or should I use the hotfix referenced in the Microsoft Article?

By the way, I have two more DCs running DNS, should I still back it up?