dcdiag results help

[Candie]

Hi All,
I ran dcdiag /a on a server on my child domain. It's receiving 1311 and
1566 ntds kcc errors. The parent domain and child domain use to communicate
with no problems. Now, users in the child domain have sporadic problems with
email hanginf up because of waiting for a response. I assume something has
gone wrong in DNS. If anyone can assist with diagnosing the results below
that would be great! Serverb refers to the child DC, servera and coeus are
the two parent dc's

C:\>dcdiag /a

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: SiteB\serverb
Starting test: Connectivity
......................... serverb passed test Connectivity

Doing primary tests

Testing server: SiteB\serverb
Starting test: Replications
[Replications Check,serverb] A recent replication attempt failed:
From servera to serverb
Naming Context: CN=Schema,CN=Configuration,DC=(domain name),DC=com
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-06-08 11:49.05.
The last success occurred at 2005-06-04 12:51.06.
166 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on servera.
[Replications Check,serverb] A recent replication attempt failed:
From servera to serverb
Naming Context: CN=Configuration,DC=(domain name),DC=com
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-06-08 12:01.41.
The last success occurred at 2005-06-04 13:16.18.
168 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on servera.
[Replications Check,serverb] A recent replication attempt failed:
From COEUS to serverb
Naming Context: DC=(domain name),DC=com
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup
failu
re.
The failure occurred at 2005-06-07 18:35.45.
The last success occurred at 2005-06-03 14:14.25.
18 failures have occurred since the last success.
The guid-based DNS name
715c02be-6d6d-4889-a712-06f73a4de168._msdcs.
(domain name).com
is not registered on one or more DNS servers.
[Replications Check,serverb] A recent replication attempt failed:
From servera to serverb
Naming Context: DC=(domain name),DC=com
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup
failu
re.
The failure occurred at 2005-06-07 18:36.17.
The last success occurred at 2005-06-03 14:14.25.
18 failures have occurred since the last success.
The guid-based DNS name
bb2f2953-abd9-4421-b07d-422c6ce268b9._msdcs.
(domain name).com
is not registered on one or more DNS servers.
REPLICATION LATENCY WARNING
serverb: A long-running replication operation is in progress
The job has been executing for 9 minutes and 14 seconds.
Replication of new changes along this path will be delayed.
This is normal for a new connection, or for a system
that has been down a long time.
Enqueued 2005-06-08 11:44.54 at priority 90
Op: SYNC FROM SOURCE
NC CN=Schema,CN=Configuration,DC=(domain name),DC=com
DSADN CN=NTDS
Settings,CN=servera,CN=Servers,CN=Default-First-Site-N
ame,CN=Sites,CN=Configuration,DC=(domain name),DC=com
DSA transport addr
bb2f2953-abd9-4421-b07d-422c6ce268b9._msdcs.melit
ta-na.com
......................... serverb passed test Replications
Starting test: NCSecDesc
......................... serverb passed test NCSecDesc
Starting test: NetLogons
......................... serverb passed test NetLogons
Starting test: Advertising
......................... serverb passed test Advertising
Starting test: KnowsOfRoleHolders
......................... serverb passed test KnowsOfRoleHolders
Starting test: RidManager
......................... serverb passed test RidManager
Starting test: MachineAccount
* serverb is not trusted for account delegation
......................... serverb failed test MachineAccount
Starting test: Services
......................... serverb passed test Services
Starting test: ObjectsReplicated
......................... serverb passed test ObjectsReplicated
Starting test: frssysvol
......................... serverb passed test frssysvol
Starting test: kccevent
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/08/2005 12:04:54
Event String: All servers in site
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/08/2005 12:04:54
Event String: The Directory Service consistency checker has
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/08/2005 12:04:54
Event String: All servers in site
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/08/2005 12:04:54
Event String: The Directory Service consistency checker has
......................... serverb failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00004E43
Time Generated: 06/08/2005 11:38:01
Event String: Remote Access Connection Manager failed to start
An Error Event occured. EventID: 0xC0001B6F
Time Generated: 06/08/2005 11:38:01
Event String: The Remote Access Connection Manager service
An Error Event occured. EventID: 0x00004E43
Time Generated: 06/08/2005 11:49:53
Event String: Remote Access Connection Manager failed to start
An Error Event occured. EventID: 0xC0001B6F
Time Generated: 06/08/2005 11:49:53
Event String: The Remote Access Connection Manager service
......................... serverb failed test systemlog

Running enterprise tests on : (domain name).com
Starting test: Intersite
Doing intersite inbound replication test on site SiteB:
*Warning: Remote bridgehead Default-First-Site-Name\servera is not
eligible as a bridgehead due to too many failures. Replication
may
be disrupted into the local site SiteB.
*Warning: Remote bridgehead Default-First-Site-Name\COEUS is not
eligible as a bridgehead due to too many failures. Replication
may
be disrupted into the local site SiteB.
......................... (domain name).com passed test Intersite
Starting test: FsmoCheck
......................... (domain name).com passed test FsmoCheck

[xlove]

have you at any point demoted a dc improperly? It's a lookup problem. You
need to revisit all you dns configurations. I'd check and make sure their are
no orphan objects in there first and then go to dns and make sure you can do
lookups on all your other dcs. Do a netdiag as well and check for
connectivity issues.
--
dave love

[Candie]

We haven't demoted a DC. I can do DNS lookups on all of my servers. On the
server that the dcdiag was ran on which is the DC for the child domain, I can
get to shares on all servers in the parent domain. When I run netdiag
/test:dns it says that DNS registration for "FQDN" is incorrect on all
servers. I'm not a DNS expert so I'm not sure what specifics to change or add
to correct registration issues.

Thanks!

"xlove" wrote:

> have you at any point demoted a dc improperly? It's a lookup problem. You
> need to revisit all you dns configurations. I'd check and make sure their are
> no orphan objects in there first and then go to dns and make sure you can do

> lookups on all your other dcs. Da netdiag as well and check for

[xlove]

what you need to do is identify the GUIDs that are failing with what you have
in dns. So you look at the output from your tests and then go into dns and
compare those numbers with the dns entries under msdcs under your dns zone.
Another thing is to ping the guids specifically and see if they resolve to
the correct server. It sound slike you have some redundant entries that are
no longer valid.

ping bb2f2953-abd9-4421-b07d-422c6ce268b9._msdcs.
(domain name).com

--
dave love
Director of IT

[Candie]

Hi Dave,
I compared all of the numbers on all servers. I also pinged all numbers
(bb3635-dge5-dddd-hdhd-422rt565wr4._msdcs) from all servers and got correct
replies back. Any other thoughts?

Thanks!!

[xlove]

scroll down through all of the dns entries under msdcs and make sure there
are no other entries besides the ones you want.