EddyGurge
asked on
Multiple DCDIAG errors on remote server.
Here is the (long) list of errors. I hope they are all just related to one issue. The servers can ping each other just fine, DNS is simply my three servers all pointing to themselves and each other. I must be missing something here.
Testing server: Default-First-Site-Name\SE
Starting test: Replications
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: DC=ForestDnsZones,DC=mycom
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-08-02 09:12:54.
The last success occurred at 2005-07-23 06:49:43.
242 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 SERVER1.
[SERVER1] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[MAIL] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: DC=DomainDnsZones,DC=mycom
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-08-02 09:09:51.
The last success occurred at 2005-07-23 06:49:42.
242 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 SERVER1.
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-08-02 09:06:47.
The last success occurred at 2005-07-23 06:49:42.
243 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 SERVER1.
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: CN=Configuration,DC=mycomp
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-08-02 10:03:47.
The last success occurred at 2005-07-23 07:01:02.
508 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 SERVER1.
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: DC=mycompany,DC=org
The replication generated an error (1818):
The remote procedure call was cancelled.
The failure occurred at 2005-08-02 09:59:06.
The last success occurred at 2005-07-23 06:55:59.
1098 failures have occurred since the last success.
......................... SERVER2 passed test Replications
Starting test: NCSecDesc
......................... SERVER2 passed test NCSecDesc
Starting test: NetLogons
[SERVER2] An net use or LsaPolicy operation failed with error 64, The specified network name is no longer available..
......................... SERVER2 failed test NetLogons
Starting test: Advertising
......................... SERVER2 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: SERVER1 is the Schema Owner, but is not responding to DS RPC Bind.
[SERVER1] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
Warning: SERVER1 is the Schema Owner, but is not responding to LDAP Bind.
Warning: SERVER1 is the Domain Owner, but is not responding to DS RPC Bind.
Warning: SERVER1 is the Domain Owner, but is not responding to LDAP Bind.
Warning: SERVER1 is the PDC Owner, but is not responding to DS RPC Bind.
Warning: SERVER1 is the PDC Owner, but is not responding to LDAP Bind.
Warning: SERVER1 is the Rid Owner, but is not responding to DS RPC Bind.
Warning: SERVER1 is the Rid Owner, but is not responding to LDAP Bind.
Warning: SERVER1 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: SERVER1 is the Infrastructure Update Owner, but is not responding to LDAP Bind.
......................... SERVER2 failed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER2 failed test RidManager
Starting test: MachineAccount
Could not open pipe with [SERVER2]:failed with 64: The specified network name is no longer available.
Could not get NetBIOSDomainName
Failed can not test for HOST SPN
Failed can not test for HOST SPN
* Missing SPN :(null)
* Missing SPN :(null)
......................... SERVER2 failed test MachineAccount
Starting test: Services
Could not open Remote ipc to [SERVER2]:failed with 64: The specified network name is no longer available.
......................... SERVER2 failed test Services
Starting test: ObjectsReplicated
......................... SERVER2 passed test ObjectsReplicated
Starting test: frssysvol
[SERVER2] An net use or LsaPolicy operation failed with error 64, The specified network name is no longer available..
......................... SERVER2 failed test frssysvol
Starting test: frsevent
......................... SERVER2 failed test frsevent
Starting test: kccevent
Failed to enumerate event log records, error The specified network name is no longer available.
......................... SERVER2 failed test kccevent
Starting test: systemlog
Failed to enumerate event log records, error The specified network name is no longer available.
......................... SERVER2 failed test systemlog
Starting test: VerifyReferences
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQU
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
......................... mycompany.org failed test FsmoCheck
Testing server: Default-First-Site-Name\SE
Starting test: Replications
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: DC=ForestDnsZones,DC=mycom
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-08-02 09:12:54.
The last success occurred at 2005-07-23 06:49:43.
242 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 SERVER1.
[SERVER1] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[MAIL] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: DC=DomainDnsZones,DC=mycom
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-08-02 09:09:51.
The last success occurred at 2005-07-23 06:49:42.
242 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 SERVER1.
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-08-02 09:06:47.
The last success occurred at 2005-07-23 06:49:42.
243 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 SERVER1.
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: CN=Configuration,DC=mycomp
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-08-02 10:03:47.
The last success occurred at 2005-07-23 07:01:02.
508 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 SERVER1.
[Replications Check,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: DC=mycompany,DC=org
The replication generated an error (1818):
The remote procedure call was cancelled.
The failure occurred at 2005-08-02 09:59:06.
The last success occurred at 2005-07-23 06:55:59.
1098 failures have occurred since the last success.
......................... SERVER2 passed test Replications
Starting test: NCSecDesc
......................... SERVER2 passed test NCSecDesc
Starting test: NetLogons
[SERVER2] An net use or LsaPolicy operation failed with error 64, The specified network name is no longer available..
......................... SERVER2 failed test NetLogons
Starting test: Advertising
......................... SERVER2 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: SERVER1 is the Schema Owner, but is not responding to DS RPC Bind.
[SERVER1] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
Warning: SERVER1 is the Schema Owner, but is not responding to LDAP Bind.
Warning: SERVER1 is the Domain Owner, but is not responding to DS RPC Bind.
Warning: SERVER1 is the Domain Owner, but is not responding to LDAP Bind.
Warning: SERVER1 is the PDC Owner, but is not responding to DS RPC Bind.
Warning: SERVER1 is the PDC Owner, but is not responding to LDAP Bind.
Warning: SERVER1 is the Rid Owner, but is not responding to DS RPC Bind.
Warning: SERVER1 is the Rid Owner, but is not responding to LDAP Bind.
Warning: SERVER1 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: SERVER1 is the Infrastructure Update Owner, but is not responding to LDAP Bind.
......................... SERVER2 failed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER2 failed test RidManager
Starting test: MachineAccount
Could not open pipe with [SERVER2]:failed with 64: The specified network name is no longer available.
Could not get NetBIOSDomainName
Failed can not test for HOST SPN
Failed can not test for HOST SPN
* Missing SPN :(null)
* Missing SPN :(null)
......................... SERVER2 failed test MachineAccount
Starting test: Services
Could not open Remote ipc to [SERVER2]:failed with 64: The specified network name is no longer available.
......................... SERVER2 failed test Services
Starting test: ObjectsReplicated
......................... SERVER2 passed test ObjectsReplicated
Starting test: frssysvol
[SERVER2] An net use or LsaPolicy operation failed with error 64, The specified network name is no longer available..
......................... SERVER2 failed test frssysvol
Starting test: frsevent
......................... SERVER2 failed test frsevent
Starting test: kccevent
Failed to enumerate event log records, error The specified network name is no longer available.
......................... SERVER2 failed test kccevent
Starting test: systemlog
Failed to enumerate event log records, error The specified network name is no longer available.
......................... SERVER2 failed test systemlog
Starting test: VerifyReferences
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQU
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
......................... mycompany.org failed test FsmoCheck
ASKER
Please tell me that was not meant for me ;)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Two servers are here on the same subnet, one is over a VPN.
Checked AD, made user, is not replicated.
Not sure what you mean by "see the same database" as far as the DNS servers go? If I run the DNS plugin, there are differences displayed in the lookups.
I have users on two of the DC's during the day. Is there any way to just restart the DNS without a full reboot? Or is that necessary?
Checked AD, made user, is not replicated.
Not sure what you mean by "see the same database" as far as the DNS servers go? If I run the DNS plugin, there are differences displayed in the lookups.
I have users on two of the DC's during the day. Is there any way to just restart the DNS without a full reboot? Or is that necessary?
ASKER
Kinda bummed nobody got back to me on this. Most of what you said helped, I also demoted and repromoted one server to help the issue. Thanks.
You can check the dns DB status by looking at the serial numbers.. every time a change is made it increments by one.
If you are running the PBE agent prior to v7, you can disable it in Safte Mode.
You may be able to upgrade to Powerchute 7 as well. Finally the following paq mentions a patch.
https://www.experts-exchange.com/questions/21511603/Access-denied-when-using-UNC-path.html
-gsgi