Removing a dead replication server?

**nethfel** · 02-04-2012

Hi all,

I have a windows 2008 DC that failed. The second one is up and running and properly authenticating users. Unfortunately, the one that failed happened during its initial backup (but after replication had occurred - the server had been up for a few days and we just finished configuring it) - Here is the relevant portion of dcdiag (actual server names and domains changed due to our in house policies) DeadServer is the server that no longer physically exists (that we are planning to replace with the same name/ip) - goodserver is the remaining AD server that is still functional and is currently running - goodserver is the one complaining (obviously) about the failed replication.

Starting test: DFSREvent

The DFS Replication Event Log.
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.
An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/01/2012 16:24:17

Event String:

The DFS Replication service failed to communicate with partner DeadServer for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: DeadServer.mydomain.com

Optional data if available:

Partner WINS Address: DeadServer

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/01/2012 23:15:55

Event String:

The DFS Replication service failed to communicate with partner DeadServer for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: DeadServer.mydomain.com

Optional data if available:

Partner WINS Address: DeadServer

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/01/2012 23:35:22

Event String:

The DFS Replication service failed to communicate with partner DeadServer for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: DeadServer.mydomain.com

Optional data if available:

Partner WINS Address: DeadServer

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/01/2012 23:54:34

Event String:

The DFS Replication service failed to communicate with partner DeadServer for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: DeadServer.mydomain.com

Optional data if available:

Partner WINS Address: DeadServer

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/02/2012 00:57:50

Event String:

The DFS Replication service failed to communicate with partner DeadServer for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: DeadServer.mydomain.com

Optional data if available:

Partner WINS Address: DeadServer

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/02/2012 04:59:30

Event String:

The DFS Replication service failed to communicate with partner DeadServer for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: DeadServer.mydomain.com

Optional data if available:

Partner WINS Address: DeadServer

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

......................... goodserver failed test DFSREvent

Microsofts KB was talking about removing an entry from sites and services - namely Default-First-Site-Name -> Servers -> Server and removing the NTDS settings. The problem was in the example they gave it appeared they were originally working with 2 DC's then all of a sudden it seemed to be 3 DC's and I was afraid to remove this entry on mine because this is my last surviving DC, but I need to get this replication issue dealt with so I can bring up more DC's again.

Any help would be appreciated.

**EINSTEIN_007** · 02-04-2012

Can you make sure with dcdiag /v on the both existing DCs that they are working correct, also run repadmin /showrepl to exlcude replication problems. If problems exist you should never start adding new machines, first solve the existing problems. If still problems exist please post the complete dcdiag and repadmin output, also an unedited ipconfig /all so we can exclude DNS problems.

**nethfel** · 03-04-2012

Hi,

Thanks for responding -

I think I wasn't quite clear on something -

I haven't added any new, and don't plan to add a new DC until I get this issue resolved.

There is currently *one* DC left in the domain - there were two, the original one and the new one - the two were working fine with no problems. The new one had a major failure after having been finally configured and prior to a successful backup run so there is currently only one DC left (the original)

The portion I posted was the issues I am getting from DCDiag - they are all related to replication attempts to the server that no longer exists.

The DNS is fine.

I have removed all references to the other (gone for good) machine except obviously in one place..

But to satisfy (once again, our specific domain name and server names removed for privacy) -

here's repadmin:

Repadmin: running command /showrepl against full DC localhost

Default-First-Site-Name\goodserver
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: f702fe35-1f3c-4cb3-b80f-47159df961cd
DSA invocationID: 3c2c4e0e-4625-4337-97ff-6a4e522d9bae

Here's ipconfig:

Windows IP Configuration

Host Name . . . . . . . . . . . . : ttch-172vsn1
Primary Dns Suffix . . . . . . . : goodserver.mydomain.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
Physical Address. . . . . . . . . : 00-0C-29-6D-B6-8D
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.3.218(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.3.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
172.16.3.218
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Tun Miniport Adapter
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1820:3348:31e8:abd3(Preferred)
Link-local IPv6 Address . . . . . : fe80::1820:3348:31e8:abd3%17(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{9DF262A1-F4FB-40D8-BCC7-D9CB938C6112}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

dcdiag:

Directory Server Diagnosis

Performing initial setup:

Trying to find home server...

* Verifying that the local machine goodserver, is a Directory Server.
Home Server = goodserver

* Connecting to directory service on server goodserver.

* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.

Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
Getting ISTG and options for the site
* Identifying all servers.

Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=goodserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.

* Found 1 DC(s). Testing 1 of them.

Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\goodserver

Starting test: Connectivity

* Active Directory LDAP Services Check
Determining IP4 connectivity
Determining IP6 connectivity
* Active Directory RPC Services Check
......................... goodserver passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\goodserver

Starting test: Advertising

The DC goodserver is advertising itself as a DC and having a DS.
The DC goodserver is advertising as an LDAP server
The DC goodserver is advertising as having a writeable directory
The DC goodserver is advertising as a Key Distribution Center
The DC goodserver is advertising as a time server
The DS goodserver is advertising as a GC.
......................... goodserver passed test Advertising

Test omitted by user request: CheckSecurityError

Test omitted by user request: CutoffServers

Starting test: FrsEvent

* The File Replication Service Event log test
......................... goodserver passed test FrsEvent

Starting test: DFSREvent

The DFS Replication Event Log.
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.
An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/01/2012 16:24:17

Event String:

The DFS Replication service failed to communicate with partner destroyedserver for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: destroyedserver.mydomain.com

Optional data if available:

Partner WINS Address: destroyedserver

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/01/2012 23:15:55

Event String:

The DFS Replication service failed to communicate with partner destroyedserver for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: destroyedserver.mydomain.com

Optional data if available:

Partner WINS Address: destroyedserver

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/01/2012 23:35:22

Event String:

The DFS Replication service failed to communicate with partner destroyedserver for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: destroyedserver.mydomain.com

Optional data if available:

Partner WINS Address: destroyedserver

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/01/2012 23:54:34

Event String:

The DFS Replication service failed to communicate with partner destroyedserver for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: destroyedserver.mydomain.com

Optional data if available:

Partner WINS Address: destroyedserver

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/02/2012 00:57:50

Event String:

The DFS Replication service failed to communicate with partner destroyedserver for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: destroyedserver.mydomain.com

Optional data if available:

Partner WINS Address: destroyedserver

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

An Error Event occurred. EventID: 0xC0001390

Time Generated: 04/02/2012 04:59:30

Event String:

The DFS Replication service failed to communicate with partner destroyedserver for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: destroyedserver.mydomain.com

Optional data if available:

Partner WINS Address: destroyedserver

Partner IP Address: 172.16.3.217

The service will retry the connection periodically.

Additional Information:

Error: 1722 (The RPC server is unavailable.)

Connection ID: F55C65ED-3CA8-4A60-AB19-B4EA94666B2C

Replication Group ID: F6DBF874-25A1-44E0-B83E-893E943208CF

......................... goodserver failed test DFSREvent

Starting test: SysVolCheck

* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... goodserver passed test SysVolCheck

Starting test: KccEvent

* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
......................... goodserver passed test KccEvent

Starting test: KnowsOfRoleHolders

Role Schema Owner = CN=NTDS Settings,CN=goodserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
Role Domain Owner = CN=NTDS Settings,CN=goodserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
Role PDC Owner = CN=NTDS Settings,CN=goodserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
Role Rid Owner = CN=NTDS Settings,CN=goodserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
Role Infrastructure Update Owner = CN=NTDS Settings,CN=goodserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
......................... goodserver passed test KnowsOfRoleHolders

Starting test: MachineAccount

Checking machine account for DC goodserver on DC goodserver.
* SPN found :LDAP/goodserver.mydomain.com/mydomain.com
* SPN found :LDAP/goodserver.mydomain.com
* SPN found :LDAP/goodserver
* SPN found :LDAP/goodserver.mydomain.com/TTCH-FNS
* SPN found :LDAP/f702fe35-1f3c-4cb3-b80f-47159df961cd._msdcs.mydomain.com
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/f702fe35-1f3c-4cb3-b80f-47159df961cd/mydomain.com
* SPN found :HOST/goodserver.mydomain.com/mydomain.com
* SPN found :HOST/goodserver.mydomain.com
* SPN found :HOST/goodserver
* SPN found :HOST/goodserver.mydomain.com/TTCH-FNS
* SPN found :GC/goodserver.mydomain.com/mydomain.com
......................... goodserver passed test MachineAccount

Starting test: NCSecDesc

* Security Permissions check for all NC's on DC goodserver.
* Security Permissions Check for

DC=ForestDnsZones,DC=ttch-fns,DC=ttchohenwald,DC=edu
(NDNC,Version 3)
* Security Permissions Check for

DC=DomainDnsZones,DC=ttch-fns,DC=ttchohenwald,DC=edu
(NDNC,Version 3)
* Security Permissions Check for

CN=Schema,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
(Schema,Version 3)
* Security Permissions Check for

CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
(Configuration,Version 3)
* Security Permissions Check for

DC=ttch-fns,DC=ttchohenwald,DC=edu
(Domain,Version 3)
......................... goodserver passed test NCSecDesc

Starting test: NetLogons

* Network Logons Privileges Check
Verified share \\goodserver\netlogon
Verified share \\goodserver\sysvol
......................... goodserver passed test NetLogons

Starting test: ObjectsReplicated

goodserver is in domain DC=ttch-fns,DC=ttchohenwald,DC=edu
Checking for CN=goodserver,OU=Domain Controllers,DC=ttch-fns,DC=ttchohenwald,DC=edu in domain DC=ttch-fns,DC=ttchohenwald,DC=edu on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=goodserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu in domain CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu on 1 servers
Object is up-to-date on all servers.
......................... goodserver passed test ObjectsReplicated

Test omitted by user request: OutboundSecureChannels

Starting test: Replications

* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=ttch-fns,DC=ttchohenwald,DC=edu
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=DomainDnsZones,DC=ttch-fns,DC=ttchohenwald,DC=edu
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=ttch-fns,DC=ttchohenwald,DC=edu
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
......................... goodserver passed test Replications

Starting test: RidManager

* Available RID Pool for the Domain is 2600 to 1073741823
* goodserver.mydomain.com is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2100 to 2599
* rIDPreviousAllocationPool is 2100 to 2599
* rIDNextRID: 2100
......................... goodserver passed test RidManager

Starting test: Services

* Checking Service: EventSystem
* Checking Service: RpcSs
* Checking Service: NTDS
* Checking Service: DnsCache
* Checking Service: DFSR
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: w32time
* Checking Service: NETLOGON
......................... goodserver passed test Services

Starting test: SystemLog

* The System Event log test
Found no errors in "System" Event log in the last 60 minutes.
......................... goodserver passed test SystemLog

Test omitted by user request: Topology

Test omitted by user request: VerifyEnterpriseReferences

Starting test: VerifyReferences

The system object reference (serverReference)

CN=goodserver,OU=Domain Controllers,DC=ttch-fns,DC=ttchohenwald,DC=edu

and backlink on

CN=goodserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu

are correct.
The system object reference (serverReferenceBL)

CN=goodserver,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=ttch-fns,DC=ttchohenwald,DC=edu

and backlink on

CN=NTDS Settings,CN=goodserver,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ttch-fns,DC=ttchohenwald,DC=edu

are correct.
......................... goodserver passed test VerifyReferences

Test omitted by user request: VerifyReplicas

Test omitted by user request: DNS

Test omitted by user request: DNS

Running partition tests on : ForestDnsZones

Starting test: CheckSDRefDom

......................... ForestDnsZones passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... ForestDnsZones passed test

CrossRefValidation

Running partition tests on : DomainDnsZones

Starting test: CheckSDRefDom

......................... DomainDnsZones passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... DomainDnsZones passed test

CrossRefValidation

Running partition tests on : Schema

Starting test: CheckSDRefDom

......................... Schema passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... Schema passed test CrossRefValidation

Running partition tests on : Configuration

Starting test: CheckSDRefDom

......................... Configuration passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... Configuration passed test CrossRefValidation

Running partition tests on : ttch-fns

Starting test: CheckSDRefDom

......................... ttch-fns passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... ttch-fns passed test CrossRefValidation

Running enterprise tests on : mydomain.com

Test omitted by user request: DNS

Test omitted by user request: DNS

Starting test: LocatorCheck

GC Name: \\goodserver.mydomain.com

Locator Flags: 0xe00013fd
PDC Name: \\goodserver.mydomain.com
Locator Flags: 0xe00013fd
Time Server Name: \\goodserver.mydomain.com
Locator Flags: 0xe00013fd
Preferred Time Server Name: \\goodserver.mydomain.com
Locator Flags: 0xe00013fd
KDC Name: \\goodserver.mydomain.com
Locator Flags: 0xe00013fd
......................... mydomain.com passed test

LocatorCheck

Starting test: Intersite

Skipping site Default-First-Site-Name, this site is outside the scope

provided by the command line arguments provided.
......................... mydomain.com passed test

Intersite

As you can see, the only place it fails is with replication - which would be expected since the server it's attempting to replicate with doesn't exist any more. There is one place that seemed to reference removing the replication but I am not convinced that this is what I should do - here in the picture attached - the NTDS settings for the good server still refer to the replication. On MS site they referred to deleting the NTDS settings entry, but the example wasn't as clear as I'd like and I couldn't locate any clearer information about whether it was safe to modify/delete the NTDS settings on the last surviving DC.

**nethfel** · 03-04-2012

Ok, looks like I found the problem - needless to say I went back and re-read the DCDiag output very carefully and found that those messages regarding DFSR were old messages in the event log from when this whole mess started - after confirming there were no new errors since this morning when I got the the single DC operating like it should be, I've cleared (and saved) the various event logs and the warnings in dcdiag have gone away. I'm going to give it 24 hours and check again tomorrow - if there are no other warnings/errors/etc. in dcdiag or in the relevant DC event logs I think I'll be in decent shape to replace the failed DC.