We have 1 DFS server running 2008 R2, for some reason a few of the folder targets are showing the wrong site name. The ones that are showing incorrect when you go to the properties of the folder target and click share permissions it gives this error message: "Information about the shared folder cannot be retrieved. This shared resource does not exist". All the folder targets that show the correct site where the DFS server resides are working correctly. If you go on the server and view the shares in Server Manager, they work correctly. I have tried to delete the namespace and recreate it but it comes back with the wrong site name. I even tried creating a "test" namespace and it still using the wrong site name for the folder target. I can view the share folder permissions and ntfs permissions.We recently upgrade AD to functional level 2012, we aren't sure if this had anything to do with the issue we are now seeing.  I am at a complete lost why this is happening. Please help.

• Edited by 3cks82 Thursday, February 12, 2015 10:35 PM

Hi,

I'm a little unclear about "site name" in your description. Do you mean a "server name"?

When I right click on a DFS path, there is no "share" tab. If I right click on the local folder and go to Sharing tab, it will show a network path.

If that is "server name", as all folder targets are manually added when setup DFS namespace, can you find out the exact server which shows incorrect?

And if it is the real "site name", it is defined in AD sites and  Services (on DC), so check if each server is in the correct site. 

Sorry for any confusion.

If you expand the Namespace and select a folder under it, on the right you see this:

The site listed is not the site where the DFS resides. Nothing has changed in Sites and Services and everything is working correctly.

If you right click the folder target and select properties and in that window click Share Permissions this is the error I get.

All folder targets with incorrect site name stopped working, if the folder target has the site listed where the DFS server is located they work fine.

Hi,

Can you run the below command and provide the output

DFSDiag /TestSites /DFSPath:\\<domain name>\<Namespace>\<Folder> /Full

Thanks,

Umesh.S.K

This is the output when I ran that command from the DFS server.

I masked some of the internal information. Thank you for responding. :)

dfsdiag /testsites /dfspath:"\\DOMAIN\NAMESPACE\FOLDER"

Starting TestSites...

Validating the site associations on every domain controller of the following: <DFS Server>

Warning: The server has IP addresses with conflicting site associations

Host name: <DFS Server>

Site: <Site Name> (This is the site that is working)

Domain controller: DC02 (This DC is at the site where the DFS server is)

-------------------------------------------------------------------------------

Host IP address                         Subnet-SiteMapping in AD

-------------------------------------------------------------------------------

::1                                     No mapping exists

-------------------------------------------------------------------------------

Warning: The server has IP addresses with conflicting site associations

Host name: <DFS Server>

Site: <Site Name> (This is the site that is working)

Domain controller: DC01 (This DC is at the site where the DFS server is)

-------------------------------------------------------------------------------

Host IP address                         Subnet-SiteMapping in AD

-------------------------------------------------------------------------------

::1                                     No mapping exists

-------------------------------------------------------------------------------

Warning: The server has IP addresses with conflicting site associations

Host name: <DFS Server>

Site: <Site Name> (This is the site that is working)

Domain controller: DC03 (This DC is at the site where DFS is showing the wrong site)

-------------------------------------------------------------------------------

Host IP address                         Subnet-SiteMapping in AD

-------------------------------------------------------------------------------

::1                                     No mapping exists

-------------------------------------------------------------------------------

Success: The site associated with the following host name is consistent on all accessible domain controllers: <DFS Server>

Finished TestSites.

Hi,

Is DC3 on correct site? Can you run dcdiag /e and post the result? Are you able to access the shared folder(the one which is giving problem) using UNC path?

Thanks,

Umesh.S.K

Yes, DC3 is in the correct site within Sites and Services. I am able to browse the share using UNC path.

Here are the results from dcdiag /e ran on DC3, there are some alerts about DHCP scope but we can multiple subnets so they aren't really a issue.

Directory Server Diagnosis


Performing initial setup:

   Trying to find home server...

   Home Server = DC3

   * Identified AD Forest. 
   Done gathering initial info.


Doing initial required tests

   
   Testing server: Site1\DC1

      Starting test: Connectivity

         ......................... DC1 passed test Connectivity

   
   Testing server: Site1\DC2

      Starting test: Connectivity

         ......................... DC2 passed test Connectivity

   
   Testing server: Site2\DC3

      Starting test: Connectivity

         ......................... DC3 passed test Connectivity



Doing primary tests

   
   Testing server: Site1\DC1

      Starting test: Advertising

         ......................... DC1 passed test Advertising

      Starting test: FrsEvent

         ......................... DC1 passed test FrsEvent

      Starting test: DFSREvent

         ......................... DC1 passed test DFSREvent

      Starting test: SysVolCheck

         ......................... DC1 passed test SysVolCheck

      Starting test: KccEvent

         ......................... DC1 passed test KccEvent

      Starting test: KnowsOfRoleHolders

         ......................... DC1 passed test KnowsOfRoleHolders

      Starting test: MachineAccount

         ......................... DC1 passed test MachineAccount

      Starting test: NCSecDesc

         ......................... DC1 passed test NCSecDesc

      Starting test: NetLogons

         ......................... DC1 passed test NetLogons

      Starting test: ObjectsReplicated

         ......................... DC1 passed test ObjectsReplicated

      Starting test: Replications

         ......................... DC1 passed test Replications

      Starting test: RidManager

         ......................... DC1 passed test RidManager

      Starting test: Services

         ......................... DC1 passed test Services

      Starting test: SystemLog

         An error event occurred.  EventID: 0x0000165B

            Time Generated: 02/25/2015   12:48:21

            Event String:

            The session setup from computer '<ComputerName>' failed because the security database does not contain a trust account '<ComputerName>$' referenced by the specified computer.  


         A warning event occurred.  EventID: 0x000003FC

            Time Generated: 02/25/2015   13:10:43

            Event String:

            Scope, X.X.10.128, is 100 percent full with only 0 IP addresses remaining.

         A warning event occurred.  EventID: 0x000003FC

            Time Generated: 02/25/2015   13:10:43

            Event String:

            Scope, X.X.10.192, is 100 percent full with only 0 IP addresses remaining.

         A warning event occurred.  EventID: 0x000003FC

            Time Generated: 02/25/2015   13:10:43

            Event String:

            Scope, X.X.13.128, is 85 percent full with only 9 IP addresses remaining.

         A warning event occurred.  EventID: 0x000003FC

            Time Generated: 02/25/2015   13:10:43

            Event String:

            Scope, X.X.142.64, is 100 percent full with only 0 IP addresses remaining.

         A warning event occurred.  EventID: 0x000003FC

            Time Generated: 02/25/2015   13:10:43

            Event String:

            Scope, X.X.170.160, is 100 percent full with only 0 IP addresses remaining.

         A warning event occurred.  EventID: 0x00000560

            Time Generated: 02/25/2015   13:10:43

            Event String:

            IP address range of scope X.X.10.128 is 100 percent full with only 0 IP addresses available.

         A warning event occurred.  EventID: 0x00000560

            Time Generated: 02/25/2015   13:10:43

            Event String:

            IP address range of scope X.X.10.192 is 100 percent full with only 0 IP addresses available.

         A warning event occurred.  EventID: 0x00000560

            Time Generated: 02/25/2015   13:10:43

            Event String:

            IP address range of scope X.X.13.128 is 85 percent full with only 9 IP addresses available.

         A warning event occurred.  EventID: 0x00000560

            Time Generated: 02/25/2015   13:10:43

            Event String:

            IP address range of scope X.X.142.64 is 100 percent full with only 0 IP addresses available.

         A warning event occurred.  EventID: 0x00000560

            Time Generated: 02/25/2015   13:10:43

            Event String:

            IP address range of scope X.X.170.160 is 100 percent full with only 0 IP addresses available.

         An error event occurred.  EventID: 0x000016AD

            Time Generated: 02/25/2015   13:23:22

            Event String:

            The session setup from the computer <ComputerName> failed to authenticate. The following error occurred: 


         ......................... DC1 failed test SystemLog

      Starting test: VerifyReferences

         ......................... DC1 passed test VerifyReferences

   
   Testing server: Site1\DC2

      Starting test: Advertising

         ......................... DC2 passed test Advertising

      Starting test: FrsEvent

         ......................... DC2 passed test FrsEvent

      Starting test: DFSREvent

         ......................... DC2 passed test DFSREvent

      Starting test: SysVolCheck

         ......................... DC2 passed test SysVolCheck

      Starting test: KccEvent

         ......................... DC2 passed test KccEvent

      Starting test: KnowsOfRoleHolders

         ......................... DC2 passed test KnowsOfRoleHolders

      Starting test: MachineAccount

         ......................... DC2 passed test MachineAccount

      Starting test: NCSecDesc

         ......................... DC2 passed test NCSecDesc

      Starting test: NetLogons

         ......................... DC2 passed test NetLogons

      Starting test: ObjectsReplicated

         ......................... DC2 passed test ObjectsReplicated

      Starting test: Replications

         ......................... DC2 passed test Replications

      Starting test: RidManager

         ......................... DC2 passed test RidManager

      Starting test: Services

         ......................... DC2 passed test Services

      Starting test: SystemLog

         ......................... DC2 passed test SystemLog

      Starting test: VerifyReferences

         ......................... DC2 passed test VerifyReferences

   
   Testing server: Site2\DC3

      Starting test: Advertising

         ......................... DC3 passed test Advertising

      Starting test: FrsEvent

         ......................... DC3 passed test FrsEvent

      Starting test: DFSREvent

         ......................... DC3 passed test DFSREvent

      Starting test: SysVolCheck

         ......................... DC3 passed test SysVolCheck

      Starting test: KccEvent

         ......................... DC3 passed test KccEvent

      Starting test: KnowsOfRoleHolders

         ......................... DC3 passed test KnowsOfRoleHolders

      Starting test: MachineAccount

         ......................... DC3 passed test MachineAccount

      Starting test: NCSecDesc

         ......................... DC3 passed test NCSecDesc

      Starting test: NetLogons

         ......................... DC3 passed test NetLogons

      Starting test: ObjectsReplicated

         ......................... DC3 passed test ObjectsReplicated

      Starting test: Replications

         ......................... DC3 passed test Replications

      Starting test: RidManager

         ......................... DC3 passed test RidManager

      Starting test: Services

         ......................... DC3 passed test Services

      Starting test: SystemLog

         A warning event occurred.  EventID: 0x000016AF

            Time Generated: 02/25/2015   12:46:29

            Event String:

            During the past 4.25 hours there have been 90 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined sites and may connect to any Domain Controller including those that are in far distant locations from the clients. A client's site is determined by the mapping of its subnet to one of the existing sites. To move the above clients to one of the sites, please consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites.  The names and IP addresses of the clients in question have been logged on this computer in the following log file '%SystemRoot%\debug\netlogon.log' and, potentially, in the log file '%SystemRoot%\debug\netlogon.bak' created if the former log becomes full. The log(s) may contain additional unrelated debugging information. To filter out the needed information, please search for lines which contain text 'NO_CLIENT_SITE:'. The first word after this string is the client name and the second word is the client IP address. The maximum size of the log(s) is controlled by the following registry DWORD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize'; the default is 20000000 bytes.  The current maximum size is 20000000 bytes.  To set a different maximum size, create the above registry value and set the desired maximum size in bytes.

         ......................... DC3 passed test SystemLog

      Starting test: VerifyReferences

         ......................... DC3 passed test VerifyReferences

   
   
   
   
   Running partition tests on : DomainDnsZones

      Starting test: CheckSDRefDom

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

      Starting test: CrossRefValidation

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

         CrossRefValidation

   
   Running partition tests on : ForestDnsZones

      Starting test: CheckSDRefDom

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

      Starting test: CrossRefValidation

         ......................... ForestDnsZones 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 : DOMAIN

      Starting test: CheckSDRefDom

         ......................... DOMAIN passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DOMAIN passed test CrossRefValidation

   
   Running enterprise tests on : DOMAIN.COM

      Starting test: LocatorCheck

         ......................... DOMAIN.COM passed test LocatorCheck

      Starting test: Intersite

         Doing intersite inbound replication test on site Site2: 
         Doing intersite inbound replication test on site Site1: 
         ......................... DOMAIN.COM passed test Intersite

• Edited by 3cks82 Wednesday, February 25, 2015 11:47 PM

------------------------------------------------------------------------------------------------------------ 

During the past 4.25 hours there have been 90 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined sites and may connect to any Domain Controller including those that are in far distant locations from the clients. A client's site is determined by the mapping of its subnet to one of the existing sites. To move the above clients to one of the sites, please consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites.  The names and IP addresses of the clients in question have been logged on this computer in the following log file '%SystemRoot%\debug\netlogon.log' and, potentially, in the log file '%SystemRoot%\debug\netlogon.bak' created if the former log becomes full. The log(s) may contain additional unrelated debugging information. To filter out the needed information, please search for lines which contain text 'NO_CLIENT_SITE:'. The first word after this string is the client name and the second word is the client IP address. The maximum size of the log(s) is controlled by the following registry DWORD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize'; the default is 20000000 bytes.  The current maximum size is 20000000 bytes.  To set a different maximum size, create the above registry value and set the desired maximum size in bytes.

------------------------------------------------------------------------------------------------------------

Looks like some client machines are not in the same site as DC3? Do you have shared folder in the same site as DC3? Can you run "nltest /dsgetsite" on all DC and provide the result? Also run repadmin /kcc, repadmin /showrepl and provide the result.

Please run the below commands

dfsdiag /testdcs /domain:<domain name>

DFSDiag /TestDFSConfig /DFSRoot:<namespace>

Thanks,

Umesh.S.K

• Edited by Umesh S K Saturday, February 28, 2015 11:53 AM

Yes, we have systems in both sites. No, we only have DFS running in Site 1.

What is odd is now when I click the namespace and on the right the folder targets that were showing the wrong site now say "Not Applicable (Namespace Root)".

I will post results from each Domain Controller for all the commands below in there own replies so they are easier to read through.

Thank you again for helping me with this issue.

Domain Controller 1:

Site1
The command completed successfully

Repadmin: running command /kcc against full DC localhost
Site1
Current Site Options: (none)
Consistency check on localhost successful.

Repadmin: running command /showrepl against full DC localhost

Site1\DC1

DSA Options: IS_GC

Site Options: (none)

DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

DSA invocationID: dc63cc9e-764e-4ede-b40c-39ed9cca5971

==== INBOUND NEIGHBORS ======================================

DC=domain,DC=com

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:23:20 was successful.

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:29:21 was successful.

CN=Configuration,DC=domain,DC=com

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:23:20 was successful.

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:23:20 was successful.

CN=Schema,CN=Configuration,DC=domain,DC=com

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:23:20 was successful.

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:23:20 was successful.

DC=ForestDnsZones,DC=domain,DC=com

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:23:20 was successful.

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:23:20 was successful.

DC=DomainDnsZones,DC=domain,DC=com

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:23:20 was successful.

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:23:20 was successful.

Starting TestDcs...

Validating the DFS Namespace service...

Validating DFS Namespace service on DC1.

Success: The DFS Namespace service on the following server is started and set to start automatically: DC1

Validating DFS Namespace service on DC2.

Success: The DFS Namespace service on the following server is started and set to start automatically: DC2

Validating DFS Namespace service on DC3.

Success: The DFS Namespace service on the following server is started and set to start automatically: DC3

Validating SiteCostedReferrals Key...

Validating site costed referrals in DC1.

Success: Site costing is enabled on SYSVOL/NETLOGON referrals.

Validating site costed referrals in DC2.

Success: Site costing is enabled on SYSVOL/NETLOGON referrals.

Validating site costed referrals in DC3.

Success: Site costing is enabled on SYSVOL/NETLOGON referrals.

Validating registry entries...

Comparing DC1 - DC2.

Comparing DC2 - DC3.

Success: The registry values under HKLM\CCS\Services\Dfs\Parameters are consistent on all compared servers.

Validating site associations...

Validating the site associations on every domain controller of the following: DC1

Success: The site associated with the following host name is consistent on all accessible domain controllers: DC1

Validating the site associations on every domain controller of the following: DC2

Success: The site associated with the following host name is consistent on all accessible domain controllers: DC2

Validating the site associations on every domain controller of the following: DC3

Success: The site associated with the following host name is consistent on all accessible domain controllers: DC3

Finished TestDcs.

Starting TestDfsConfig...

Retrieving all the namespace servers...

Validating the DFS Namespace service...

Validating DFS Namespace service on DFSServer.

Success: The DFS Namespace service on the following server is started and set to start automatically: DFSServer

Validating registry entries...

Information: No comparison was made. To make a comparison, a minimum of two namespace servers are required.

Finished TestDfsConfig.

• Edited by 3cks82 Friday, March 06, 2015 1:03 AM

Domain Controller 2:

Site1
The command completed successfully

Repadmin: running command /kcc against full DC localhost

Site1

Current Site Options: (none)

Consistency check on localhost successful.

Repadmin: running command /showrepl against full DC localhost

Site1\DC2

DSA Options: IS_GC

Site Options: (none)

DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

DSA invocationID: 817e3920-81ad-4b38-bdee-d6bd5e49d05a

==== INBOUND NEIGHBORS ======================================

DC=domain,DC=com

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:01:13 was successful.

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:08:51 was successful.

CN=Configuration,DC=domain,DC=com

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:01:13 was successful.

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:01:34 was successful.

CN=Schema,CN=Configuration,DC=domain,DC=com

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:01:13 was successful.

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:01:13 was successful.

DC=ForestDnsZones,DC=domain,DC=com

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:01:13 was successful.

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:01:13 was successful.

DC=DomainDnsZones,DC=domain,DC=com

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:01:13 was successful.

    Site2\DC3 via RPC

        DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

        Last attempt @ 2015-03-05 16:01:13 was successful.

Starting TestDcs...

Validating the DFS Namespace service...

Validating DFS Namespace service on DC2.

Success: The DFS Namespace service on the following server is started and set to start automatically: DC2

Validating DFS Namespace service on DC1.

Success: The DFS Namespace service on the following server is started and set to start automatically: DC1

Validating DFS Namespace service on DC3.

Success: The DFS Namespace service on the following server is started and set to start automatically: DC3

Validating SiteCostedReferrals Key...

Validating site costed referrals in DC2.

Success: Site costing is enabled on SYSVOL/NETLOGON referrals.

Validating site costed referrals in DC1.

Success: Site costing is enabled on SYSVOL/NETLOGON referrals.

Validating site costed referrals in DC3.

Success: Site costing is enabled on SYSVOL/NETLOGON referrals.

Validating registry entries...

Comparing DC2 - DC1.

Comparing DC1 - DC3.

Success: The registry values under HKLM\CCS\Services\Dfs\Parameters are consistent on all compared servers.

Validating site associations...

Validating the site associations on every domain controller of the following: DC2

Success: The site associated with the following host name is consistent on all accessible domain controllers: DC2

Validating the site associations on every domain controller of the following: DC1

Success: The site associated with the following host name is consistent on all accessible domain controllers: DC1

Validating the site associations on every domain controller of the following: DC3

Success: The site associated with the following host name is consistent on all accessible domain controllers: DC3

Finished TestDcs.

Starting TestDfsConfig...

Retrieving all the namespace servers...

Validating the DFS Namespace service...

Validating DFS Namespace service on DFSServer.

Success: The DFS Namespace service on the following server is started and set to start automatically: DFSServer

Validating registry entries...

Information: No comparison was made. To make a comparison, a minimum of two namespace servers are required.

Finished TestDfsConfig.

Domain Controller 3:

Site2
The command completed successfully

Repadmin: running command /kcc against full DC localhost

Site2

Current Site Options: (none)

Consistency check on localhost successful.

Repadmin: running command /showrepl against full DC localhost

Site2\DC3

DSA Options: IS_GC

Site Options: (none)

DSA object GUID: f170b59b-7480-44e8-bc59-fbd189233308

DSA invocationID: 25d23fc4-4d36-4e73-a471-7a02b2bcb4a2

==== INBOUND NEIGHBORS ======================================

DC=domain,DC=com

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:01:31 was successful.

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:01:31 was successful.

CN=Configuration,DC=domain,DC=com

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:01:31 was successful.

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:01:31 was successful.

CN=Schema,CN=Configuration,DC=domain,DC=com

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:01:31 was successful.

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:01:31 was successful.

DC=ForestDnsZones,DC=domain,DC=com

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:01:31 was successful.

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:01:31 was successful.

DC=DomainDnsZones,DC=domain,DC=com

    Site1\DC1 via RPC

        DSA object GUID: b1fcca97-da83-4ebc-b21c-d9a43d192b6e

        Last attempt @ 2015-03-05 16:01:31 was successful.

    Site1\DC2 via RPC

        DSA object GUID: 75cb63dd-4b7b-4bc8-a612-7994de453f75

        Last attempt @ 2015-03-05 16:01:31 was successful.

Starting TestDcs...

Validating the DFS Namespace service...

Validating DFS Namespace service on DC2.

Success: The DFS Namespace service on the following server is started and set to start automatically: DC2

Validating DFS Namespace service on DC1.

Success: The DFS Namespace service on the following server is started and set to start automatically: DC1

Validating DFS Namespace service on DC3.

Success: The DFS Namespace service on the following server is started and set to start automatically: DC3

Validating SiteCostedReferrals Key...

Validating site costed referrals in DC2.

Success: Site costing is enabled on SYSVOL/NETLOGON referrals.

Validating site costed referrals in DC1.

Success: Site costing is enabled on SYSVOL/NETLOGON referrals.

Validating site costed referrals in DC3.

Success: Site costing is enabled on SYSVOL/NETLOGON referrals.

Validating registry entries...

Comparing DC2 - DC1.

Comparing DC1 - DC3.

Success: The registry values under HKLM\CCS\Services\Dfs\Parameters are consistent on all compared servers.

Validating site associations...

Validating the site associations on every domain controller of the following: DC2

Success: The site associated with the following host name is consistent on all accessible domain controllers: DC2

Validating the site associations on every domain controller of the following: DC1

Success: The site associated with the following host name is consistent on all accessible domain controllers: DC1

Validating the site associations on every domain controller of the following: DC3

Success: The site associated with the following host name is consistent on all accessible domain controllers: DC3

Finished TestDcs.

Starting TestDfsConfig...

Retrieving all the namespace servers...

Validating the DFS Namespace service...

Validating DFS Namespace service on DFSServer.

Success: The DFS Namespace service on the following server is started and set to start automatically: DFSServer

Validating registry entries...

Information: No comparison was made. To make a comparison, a minimum of two namespace servers are required.

Finished TestDfsConfig.

As far as replication and dfsdiag report is concerned, things looks normal. Do you still see "Not applicable" after performing the above actions? Can you please re-post the current DFS namespace screenshot? Do you see any error event log?

Thanks,

Umesh.S.K