T
Tim Nichols
We had a problem with a domain controller in another site. It was giving a
stop error saying it couldn't load a registry hive after applying an update,
so we used the recovery console and chkdsk /p /r and a few other switches
before we got it to work. Now the domain controller boots up, but I cannot
logon to it. In the System Event log of the DC it is getting several
Netlogon event 5774 as follows:
The dynamic registration of the DNS record
'140c4fbe-b22a-44b3-be64-4b7116a8f400._msdcs.domain.com. 600 IN CNAME
dc1.domain.com.' failed on the following DNS server:
DNS server IP address: 192.168.1.10
Returned Response Code (RCODE): 5
Returned Status Code: 9017
For computers and users to locate this domain controller, this record must
be registered in DNS.
There are several of these events that get logged whenever I restart the
Netlogon service, and they all have a different DNS record listed but they
all have the same DNS server IP.
Anyone have any suggestions on what we can do to fix the problem?
-Tim Nichols
stop error saying it couldn't load a registry hive after applying an update,
so we used the recovery console and chkdsk /p /r and a few other switches
before we got it to work. Now the domain controller boots up, but I cannot
logon to it. In the System Event log of the DC it is getting several
Netlogon event 5774 as follows:
The dynamic registration of the DNS record
'140c4fbe-b22a-44b3-be64-4b7116a8f400._msdcs.domain.com. 600 IN CNAME
dc1.domain.com.' failed on the following DNS server:
DNS server IP address: 192.168.1.10
Returned Response Code (RCODE): 5
Returned Status Code: 9017
For computers and users to locate this domain controller, this record must
be registered in DNS.
There are several of these events that get logged whenever I restart the
Netlogon service, and they all have a different DNS record listed but they
all have the same DNS server IP.
Anyone have any suggestions on what we can do to fix the problem?
-Tim Nichols