|
|
 |
|
|
Pages: 1
netlogon error 5774 in event viewer
(Click here to view the original thread with full colors/images)
Posted by: Bleyn
I'm working with a Win2k SP4 server (configured as a domain controller) that keeps getting Netlogon error 5774 in the Event Viewer.
The message that it is getting is basically:
Registration of the DNS record '*hostname*. 600 IN A *ip-addy*.' failed with the following error:
DNS operation refused.
or
Registration of the DNS record '*hostname*. 600 IN SRV 0 100 88
*hostname*.' failed with the following error:
DNS operation refused.
I've looked this up in the MS Knowledge base. Unfortunantly, there are a number of potential causes for this, but most of the explainations and suggested solutions either don't appear to apply to my situation or don't make much sense(to me at least). And the ones that do appear to apply involve Registry editing that I would prefer to avoid at this time.
From what I can gather, the most likely source of this is that the server is trying to register internal SRV records to the DNS(a seperate machine) via dynamic update and the DNS isn't set for dynamic update.
Is there a way to stop this without going into the registry? Or does anyone have any other suggestions as to what to do?
Posted by: Kdr Kane
Sure.
Add the SRV records to the DNS server manually.
Posted by: Bleyn
Unfortunantly, the DNS is not under my control. That and from what I can tell, I don't think those SRV records are supposed to be going out to the DNS.
Posted by: Kdr Kane
You should have worked that out with the folks that do control the DNS.
It's absolutely necessary to update the SRV records in DNS for DCs. What are you going to do later when WINS is no longer supported?
You don't really have any choice here. I'm assuming your DNS is controlled by your UNIX people. That's normal. But, they have to allow you to make requests to update the SRV records. If their software is so outdated that it won't support the SRV records, then they HAVE to update. Otherwise, your only option is to institute Microsoft's DNS for your W2K/2003 infrastructure. And that's just a bad idea.
Posted by: Bleyn
A lot of the configuration of this server(including its setup as a DC) was done a couple of years ago, well before I started working here. To be honest, the server really isn't being used as a DC at this time. They wanted to do it, but some software that our group absolutely has to use was at the time less than fully compatible with Win2k and prevented us from actually utilizing that server as a DC.
I am very seriously considering reformatting the server when I get a chance and not reviving it as a DC.
|
|
|
|
|
