• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 511
  • Last Modified:

Users authenticating to remote DC server

My company has a corporate office in VA but regional offices across the country. Each office has a domain controller but I've been finding more and more machines that are pointed back to our corporate DC when I run "set l". Is there a way for me to repoint locally?
0
mhmservices
Asked:
mhmservices
  • 21
  • 20
1 Solution
 
Darius GhassemCommented:
A couple of things will make clients go to a different DC for authentication. Make sure the clients are pointing to local DNS servers to their site. Make sure the site DC is a GC. Make sure you have sites setup in AD Sites and Services with the correct subnet.
0
 
mhmservicesAuthor Commented:
Can you go into a little more detail as to where to look for each item?
0
 
Darius GhassemCommented:
Go into the clients at each site make sure that their TCP\IP properties that the primary DNS is pointed to their local DNS server at the site.

Go into AD Sites and Services right-click NTDS Settings on each DC go to properties check Make this a Global Catalog.

In AD Sites and Services make sure you have the sites broken down in each site all DCs under one site. You want each site to have their own site in AD Sites and Services if you don't have them broken up then the clients and DCs think they are all on Site location.
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
mhmservicesAuthor Commented:
Dariusg,


I checked the scope on the local DHCP server and the primary DNS is pointed to the proper server.


I found this setting and will make it overnight although I have a question. Will having multiple GC's in a domain cause "fighting" over the service? I know in 2000 server Microsoft suggested having only one GC.


Each state has its own site.
0
 
Darius GhassemCommented:
No, the more you have the better it doesn't matter how many GCs you have but you should have at least one at each site.
0
 
mhmservicesAuthor Commented:
OK, I seem to remember certain items that servers tend to fight over that could cause issues. I'll make the GC change and reevaluate.
0
 
Darius GhassemCommented:
Do you have the sites broken out in AD sites and services?
0
 
mhmservicesAuthor Commented:
Here is what I see
ad.JPG
0
 
Darius GhassemCommented:
Looking good.
0
 
mhmservicesAuthor Commented:
I'll let you know the results of promotion to GC. Thanks for all your help so far.
0
 
Darius GhassemCommented:
Please let me know if you need anymore help. Once you make the a server a GC. Run a netdiag /fix on the system and allow it to replicate before trying.
0
 
mhmservicesAuthor Commented:
How long should we allow for replication once we select the GC option before testing with netdiag and dcdiag?
0
 
Darius GhassemCommented:
You have a pretty nice size network I would allow replication to take place overnight to make sure everything is replicated but if you want to try before then you can just try again tomorrow morning if it doesn't work today.
0
 
mhmservicesAuthor Commented:
One of the sysadmins went ahead and made the GC change a short while ago and ran dcdiag shortly after and got replication errors. I assume that he would get errors unless the GC replication had completed. I'll try dcdiag on the remote server again tomorrow morning and report back.
0
 
Darius GhassemCommented:
Ok.
0
 
mhmservicesAuthor Commented:
This is the output of dcdiag this morning on the server we changed to be a GC yesterday.





C:\>dcdiag /test:dns /s:mhmdc1 /dnsbasic

Domain Controller Diagnosis

Performing initial setup:
   [mhmdc1] Directory Binding Error 1753:
   There are no more endpoints available from the endpoint mapper.
   This may limit some of the tests that can be performed.
   Done gathering initial info.

Doing initial required tests

   Testing server: Virginia\MHMDC1
      Starting test: Connectivity
         [MHMDC1] DsBindWithSpnEx() failed with error 1753,
         There are no more endpoints available from the endpoint mapper..
         ......................... MHMDC1 failed test Connectivity

Doing primary tests

   Testing server: Virginia\MHMDC1

DNS Tests are running and not hung. Please wait a few minutes...

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : mhmnet

   Running enterprise tests on : mhmnet.mhm-services.local
      Starting test: DNS
         Test results for domain controllers:

            DC: mhmdc1.mhmnet.mhm-services.local
            Domain: mhmnet.mhm-services.local


               TEST: Basic (Basc)
                  Error: No DS RPC connectivity
                  Error: No WMI connectivity

         Summary of DNS test results:

                                            Auth Basc Forw Del  Dyn  RReg Ext
               ______________________________________________________________
            Domain: mhmnet.mhm-services.local
               mhmdc1                       PASS FAIL n/a  n/a  n/a  n/a  n/a

         ......................... mhmnet.mhm-services.local failed test DNS
0
 
Darius GhassemCommented:
The DNS is having trouble it looks like. You are having problems with DNS. What errors are you getting in the Event log?



0
 
mhmservicesAuthor Commented:
In event viewer under directory services I see multiple errors with numbers 1865, 1311, 1566, and 1925.


Under FRS I see 13508, 13562 and 13565
0
 
Darius GhassemCommented:
That is why the clients aren't authenicating to the server is because it hasn't replicated the 13508 errors. Can you post the whole error for me please to make sure you aren't tombstoned.
0
 
mhmservicesAuthor Commented:
The File Replication Service is having trouble enabling replication from MHMDC1 to MDDC1 for c:\windows\sysvol\domain using the DNS name mhmdc1.mhmnet.mhm-services.local. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name mhmdc1.mhmnet.mhm-services.local from this computer.
 [2] FRS is not running on mhmdc1.mhmnet.mhm-services.local.
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
 
 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 
Darius GhassemCommented:
DNS is your problem. On the server make sure you are only pointing to internal DNS servers in your TCP\IP properties.
0
 
mhmservicesAuthor Commented:
The primary DNS is set to the local server. The secondary is pointed back to corporate. Should I take out the secondary?
0
 
Darius GhassemCommented:
For now take out corporate then run ipconfig /flushdns, ipconfig /registerdns, dcdiag /fix.
0
 
mhmservicesAuthor Commented:
My results are below.


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

T:\>c:

C:\>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\>ipconfig /registerdns

Windows IP Configuration

Registration of the DNS resource records for all adapters of this computer has b
een initiated. Any errors will be reported in the Event Viewer in 15 minutes..

C:\>dcdiag /fix

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Maryland\MDDC1
      Starting test: Connectivity
         ......................... MDDC1 passed test Connectivity

Doing primary tests

   Testing server: Maryland\MDDC1
      Starting test: Replications
         REPLICATION-RECEIVED LATENCY WARNING
         MDDC1:  Current time is 2009-04-23 14:25:10.
            DC=ForestDnsZones,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=DomainDnsZones,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Schema,CN=Configuration,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:11.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Configuration,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:11.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

         ......................... MDDC1 passed test Replications
      Starting test: NCSecDesc
         ......................... MDDC1 passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\MDDC1\netlogon)
         [MDDC1] An net use or LsaPolicy operation failed with error 1203, No ne
twork provider accepted the given network path..
         ......................... MDDC1 failed test NetLogons
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\mhmdc1.mhmnet.mhm-servi
ces.local, when we were trying to reach MDDC1.
         Server is not responding or is not considered suitable.
         ......................... MDDC1 failed test Advertising
      Starting test: KnowsOfRoleHolders
         [MHMDC1] DsBindWithSpnEx() failed with error 1753,
         There are no more endpoints available from the endpoint mapper..
         Warning: MHMDC1 is the Schema Owner, but is not responding to DS RPC Bi
nd.
         Warning: MHMDC1 is the Domain Owner, but is not responding to DS RPC Bi
nd.
         Warning: MHMDC1 is the PDC Owner, but is not responding to DS RPC Bind.

         Warning: MHMDC1 is the Rid Owner, but is not responding to DS RPC Bind.

         ......................... MDDC1 failed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... MDDC1 failed test RidManager
      Starting test: MachineAccount
         ......................... MDDC1 passed test MachineAccount
      Starting test: Services
         ......................... MDDC1 passed test Services
      Starting test: ObjectsReplicated
         ......................... MDDC1 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... MDDC1 passed test frssysvol
      Starting test: frsevent
         ......................... MDDC1 passed test frsevent
      Starting test: kccevent
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/23/2009   14:15:07
            Event String: All domain controllers in the following site that
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/23/2009   14:15:07
            Event String: The Knowledge Consistency Checker (KCC) has
         An Warning Event occured.  EventID: 0x80000749
            Time Generated: 04/23/2009   14:15:07
            Event String: The Knowledge Consistency Checker (KCC) was
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/23/2009   14:15:07
            Event String: All domain controllers in the following site that
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/23/2009   14:15:07
            Event String: The Knowledge Consistency Checker (KCC) has
         An Warning Event occured.  EventID: 0x80000749
            Time Generated: 04/23/2009   14:15:07
            Event String: The Knowledge Consistency Checker (KCC) was
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/23/2009   14:15:07
            Event String: All domain controllers in the following site that
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/23/2009   14:15:07
            Event String: The Knowledge Consistency Checker (KCC) has
         An Warning Event occured.  EventID: 0x80000749
            Time Generated: 04/23/2009   14:15:07
            Event String: The Knowledge Consistency Checker (KCC) was
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/23/2009   14:15:07
            Event String: All domain controllers in the following site that
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/23/2009   14:15:07
            Event String: The Knowledge Consistency Checker (KCC) has
         An Warning Event occured.  EventID: 0x80000749
            Time Generated: 04/23/2009   14:15:07
            Event String: The Knowledge Consistency Checker (KCC) was
         An Warning Event occured.  EventID: 0x80000785
            Time Generated: 04/23/2009   14:15:28
            Event String: The attempt to establish a replication link for
         An Warning Event occured.  EventID: 0x80000785
            Time Generated: 04/23/2009   14:15:49
            Event String: The attempt to establish a replication link for
         An Warning Event occured.  EventID: 0x80000785
            Time Generated: 04/23/2009   14:16:10
            Event String: The attempt to establish a replication link for
         An Warning Event occured.  EventID: 0x80000785
            Time Generated: 04/23/2009   14:16:31
            Event String: The attempt to establish a replication link for
         An Warning Event occured.  EventID: 0x80000785
            Time Generated: 04/23/2009   14:16:53
            Event String: The attempt to establish a replication link for
         An Warning Event occured.  EventID: 0x80000785
            Time Generated: 04/23/2009   14:17:14
            Event String: The attempt to establish a replication link for
         An Error Event occured.  EventID: 0xC0000748
            Time Generated: 04/23/2009   14:22:38
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC0000748
            Time Generated: 04/23/2009   14:22:38
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC0000748
            Time Generated: 04/23/2009   14:22:38
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC0000748
            Time Generated: 04/23/2009   14:22:38
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC0000748
            Time Generated: 04/23/2009   14:22:38
            (Event String could not be retrieved)
         ......................... MDDC1 failed test kccevent
      Starting test: systemlog
         ......................... MDDC1 passed test systemlog
      Starting test: VerifyReferences
         ......................... MDDC1 passed test VerifyReferences

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : mhmnet
      Starting test: CrossRefValidation
         ......................... mhmnet passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... mhmnet passed test CheckSDRefDom

   Running enterprise tests on : mhmnet.mhm-services.local
      Starting test: Intersite
         ......................... mhmnet.mhm-services.local passed test Intersi
te
      Starting test: FsmoCheck
         ......................... mhmnet.mhm-services.local passed test FsmoChe
ck

C:\>
0
 
Darius GhassemCommented:
It seems like the server is Tombstoned and needs to be demoted. Run a dcpromo /forceremoval on the system. Then run a metadata cleanup.

http://www.petri.co.il/delete_failed_dcs_from_ad.htm
0
 
mhmservicesAuthor Commented:
This server was only promoted to a DC on tuesday. How is it already tombstoned?
0
 
Darius GhassemCommented:
Are you sure? Because this error states that last time it was replicated was 2009-02-17. Is this server using a name from a prior DC.

This server:

REPLICATION-RECEIVED LATENCY WARNING
         MDDC1:  Current time is 2009-04-23 14:25:10.
            DC=ForestDnsZones,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!
0
 
mhmservicesAuthor Commented:
I'm absolutely sure it was promoted on Tuesday. Prior to Tuesday it wasn't a DC. We had a SA on site who did the promotion. This is the only server we've given the name MDdc1
0
 
Darius GhassemCommented:
Are you getting errors on RCEXBE1?
0
 
mhmservicesAuthor Commented:
rcexbe1 is in a remote disaster recovery site and can not be reached. We have to send a tech to that site to fix it.
0
 
Darius GhassemCommented:
Are you running the dcdiag from the server you are having trouble with? Run it from another server.
0
 
mhmservicesAuthor Commented:
I was running dcdiag from MDdc1 which is the server I was having issues with. Am I running dcdiag /fix on another server? I can run it from our main domain controller here in corporate which is mhmdc1.
0
 
Darius GhassemCommented:
Run it from mhmdc1
0
 
mhmservicesAuthor Commented:
Below is the output of dcdiag /fix from mhmdc1 and hqdc2. MHMdc1 is the primary corporate DC and hqdc2 is the backup.


from mhmdc1


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

T:\>c:

C:\>dcdiag /fix

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Virginia\MHMDC1
      Starting test: Connectivity
         ......................... MHMDC1 passed test Connectivity

Doing primary tests

   Testing server: Virginia\MHMDC1
      Starting test: Replications
         [Replications Check,MHMDC1] A recent replication attempt failed:
            From RCEXBE1 to MHMDC1
            Naming Context: DC=ForestDnsZones,DC=mhmnet,DC=mhm-services,DC=local

            The replication generated an error (1256):
            The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
            The failure occurred at 2009-04-23 15:14:42.
            The last success occurred at 2009-02-17 09:17:47.
            6253 failures have occurred since the last success.
         [Replications Check,MHMDC1] A recent replication attempt failed:
            From RCEXBE1 to MHMDC1
            Naming Context: DC=DomainDnsZones,DC=mhmnet,DC=mhm-services,DC=local

            The replication generated an error (1256):
            The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
            The failure occurred at 2009-04-23 15:14:42.
            The last success occurred at 2009-02-17 09:17:47.
            6254 failures have occurred since the last success.
         [Replications Check,MHMDC1] A recent replication attempt failed:
            From RCEXBE1 to MHMDC1
            Naming Context: CN=Schema,CN=Configuration,DC=mhmnet,DC=mhm-services
,DC=local
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2009-04-23 15:15:24.
            The last success occurred at 2009-02-17 09:33:29.
            6253 failures have occurred since the last success.
            [RCEXBE1] DsBindWithSpnEx() failed with error 1722,
            The RPC server is unavailable..
            The source remains down. Please check the machine.
         [Replications Check,MHMDC1] A recent replication attempt failed:
            From RCEXBE1 to MHMDC1
            Naming Context: CN=Configuration,DC=mhmnet,DC=mhm-services,DC=local
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2009-04-23 15:15:03.
            The last success occurred at 2009-02-17 09:17:47.
            6254 failures have occurred since the last success.
            The source remains down. Please check the machine.
         [Replications Check,MHMDC1] A recent replication attempt failed:
            From RCEXBE1 to MHMDC1
            Naming Context: DC=mhmnet,DC=mhm-services,DC=local
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2009-04-23 15:14:42.
            The last success occurred at 2009-02-17 09:17:47.
            6254 failures have occurred since the last success.
            The source remains down. Please check the machine.
         REPLICATION-RECEIVED LATENCY WARNING
         MHMDC1:  Current time is 2009-04-23 15:23:40.
            DC=ForestDnsZones,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=DomainDnsZones,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Schema,CN=Configuration,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:11.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Configuration,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:11.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

         ......................... MHMDC1 passed test Replications
      Starting test: NCSecDesc
         ......................... MHMDC1 passed test NCSecDesc
      Starting test: NetLogons
         ......................... MHMDC1 passed test NetLogons
      Starting test: Advertising
         ......................... MHMDC1 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... MHMDC1 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... MHMDC1 passed test RidManager
      Starting test: MachineAccount
         ......................... MHMDC1 passed test MachineAccount
      Starting test: Services
         ......................... MHMDC1 passed test Services
      Starting test: ObjectsReplicated
         ......................... MHMDC1 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... MHMDC1 passed test frssysvol
      Starting test: frsevent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... MHMDC1 failed test frsevent
      Starting test: kccevent
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:09:36
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:11:36
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:12:06
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:12:06
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:12:06
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:12:06
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/23/2009   15:12:25
            Event String: All domain controllers in the following site that
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/23/2009   15:12:25
            Event String: The Knowledge Consistency Checker (KCC) has
         An Warning Event occured.  EventID: 0x80000749
            Time Generated: 04/23/2009   15:12:25
            Event String: The Knowledge Consistency Checker (KCC) was
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/23/2009   15:12:25
            Event String: All domain controllers in the following site that
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/23/2009   15:12:25
            Event String: The Knowledge Consistency Checker (KCC) has
         An Warning Event occured.  EventID: 0x80000749
            Time Generated: 04/23/2009   15:12:25
            Event String: The Knowledge Consistency Checker (KCC) was
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/23/2009   15:12:25
            Event String: All domain controllers in the following site that
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/23/2009   15:12:25
            Event String: The Knowledge Consistency Checker (KCC) has
         An Warning Event occured.  EventID: 0x80000749
            Time Generated: 04/23/2009   15:12:25
            Event String: The Knowledge Consistency Checker (KCC) was
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/23/2009   15:12:25
            Event String: All domain controllers in the following site that
         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/23/2009   15:12:25
            Event String: The Knowledge Consistency Checker (KCC) has
         An Warning Event occured.  EventID: 0x80000749
            Time Generated: 04/23/2009   15:12:25
            Event String: The Knowledge Consistency Checker (KCC) was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:12:36
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:12:36
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:12:36
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:15:36
            Event String: Internal event: An LDAP client connection was
         An Warning Event occured.  EventID: 0x800004C0
            Time Generated: 04/23/2009   15:23:06
            Event String: Internal event: An LDAP client connection was
         ......................... MHMDC1 failed test kccevent
      Starting test: systemlog
         ......................... MHMDC1 passed test systemlog
      Starting test: VerifyReferences
         ......................... MHMDC1 passed test VerifyReferences

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : mhmnet
      Starting test: CrossRefValidation
         ......................... mhmnet passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... mhmnet passed test CheckSDRefDom

   Running enterprise tests on : mhmnet.mhm-services.local
      Starting test: Intersite
         ......................... mhmnet.mhm-services.local passed test Intersi
te
      Starting test: FsmoCheck
         ......................... mhmnet.mhm-services.local passed test FsmoChe
ck

C:\>






from hqdc2



Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

T:\>c:

C:\>dcdiag /fix

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Virginia\HQDC2
      Starting test: Connectivity
         ......................... HQDC2 passed test Connectivity

Doing primary tests

   Testing server: Virginia\HQDC2
      Starting test: Replications
         [Replications Check,HQDC2] A recent replication attempt failed:
            From RCEXBE1 to HQDC2
            Naming Context: DC=ForestDnsZones,DC=mhmnet,DC=mhm-services,DC=local

            The replication generated an error (1256):
            The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
            The failure occurred at 2009-04-23 15:19:47.
            The last success occurred at 2009-02-17 10:05:12.
            6238 failures have occurred since the last success.
         [Replications Check,HQDC2] A recent replication attempt failed:
            From RCEXBE1 to HQDC2
            Naming Context: DC=DomainDnsZones,DC=mhmnet,DC=mhm-services,DC=local

            The replication generated an error (1256):
            The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
            The failure occurred at 2009-04-23 15:19:47.
            The last success occurred at 2009-02-17 10:05:12.
            6239 failures have occurred since the last success.
         [Replications Check,HQDC2] A recent replication attempt failed:
            From RCEXBE1 to HQDC2
            Naming Context: CN=Schema,CN=Configuration,DC=mhmnet,DC=mhm-services
,DC=local
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2009-04-23 15:20:30.
            The last success occurred at 2009-02-17 10:05:11.
            6238 failures have occurred since the last success.
            [RCEXBE1] DsBindWithSpnEx() failed with error 1722,
            The RPC server is unavailable..
            The source remains down. Please check the machine.
         [Replications Check,HQDC2] A recent replication attempt failed:
            From RCEXBE1 to HQDC2
            Naming Context: CN=Configuration,DC=mhmnet,DC=mhm-services,DC=local
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2009-04-23 15:20:08.
            The last success occurred at 2009-02-17 10:05:11.
            6239 failures have occurred since the last success.
            The source remains down. Please check the machine.
         [Replications Check,HQDC2] A recent replication attempt failed:
            From RCEXBE1 to HQDC2
            Naming Context: DC=mhmnet,DC=mhm-services,DC=local
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2009-04-23 15:19:47.
            The last success occurred at 2009-02-17 10:05:12.
            6241 failures have occurred since the last success.
            The source remains down. Please check the machine.
         REPLICATION-RECEIVED LATENCY WARNING
         HQDC2:  Current time is 2009-04-23 15:26:57.
            DC=ForestDnsZones,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=DomainDnsZones,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Schema,CN=Configuration,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:11.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Configuration,DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:11.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=mhmnet,DC=mhm-services,DC=local
               Last replication recieved from RCEXBE1 at 2009-02-17 10:05:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

         ......................... HQDC2 passed test Replications
      Starting test: NCSecDesc
         ......................... HQDC2 passed test NCSecDesc
      Starting test: NetLogons
         ......................... HQDC2 passed test NetLogons
      Starting test: Advertising
         ......................... HQDC2 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... HQDC2 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... HQDC2 passed test RidManager
      Starting test: MachineAccount
         ......................... HQDC2 passed test MachineAccount
      Starting test: Services
         ......................... HQDC2 passed test Services
      Starting test: ObjectsReplicated
         ......................... HQDC2 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... HQDC2 passed test frssysvol
      Starting test: frsevent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... HQDC2 failed test frsevent
      Starting test: kccevent
         ......................... HQDC2 passed test kccevent
      Starting test: systemlog
         ......................... HQDC2 passed test systemlog
      Starting test: VerifyReferences
         ......................... HQDC2 passed test VerifyReferences

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : mhmnet
      Starting test: CrossRefValidation
         ......................... mhmnet passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... mhmnet passed test CheckSDRefDom

   Running enterprise tests on : mhmnet.mhm-services.local
      Starting test: Intersite
         ......................... mhmnet.mhm-services.local passed test Intersi
te
      Starting test: FsmoCheck
         ......................... mhmnet.mhm-services.local passed test FsmoChe
ck

C:\>
0
 
Darius GhassemCommented:
Well it looks like the DR site DC is tombstoned but it is funny that the dcdiag was saying that the server hasn't replicated since Feb maybe I was looking at it wrong. Also, it seems that the DCs might be replicating from the DR DC.
0
 
mhmservicesAuthor Commented:
What does tombstone mean?


Where do we go from here?
0
 
Darius GhassemCommented:
Tombstone means that it hasn't replicated for a time period so that AD database is consider obsolete and has to be removed from that failed DC. So, you must demote the DC run a metadata cleanup on the AD. Are you getting any other errors on the DCs? Are other DCs getting the 13508 errors?

Find out what your replication topology is.

http://technet.microsoft.com/en-us/library/cc738415.aspx

http://www.tech-faq.com/replication-topology-active-directory.shtml
0
 
mhmservicesAuthor Commented:
I'm checking all my DC's and every one I've looked at so far has 13508 errors.
0
 
Darius GhassemCommented:
I think they are all pointing to the remote DC for primary replication.
0
 
mhmservicesAuthor Commented:
You mean the DR site that is currently unreachable? Is there a way to change the primary?
0
 
Darius GhassemCommented:
The links I posted above should tell you how to view your current replication scope and change it.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 21
  • 20
Tackle projects and never again get stuck behind a technical roadblock.
Join Now