Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2322
  • Last Modified:

active directory replication failurs with auto NTDS

I have about 15 servers in different locations, all except 1 (an NT4 box that runs an app we can't upgrade) is w2k3 and is both a GC, DC.   The I have had problems with replication and by repeatedly cleared all the automatic connections, rechecked topology, rebooting have been able to get the replication errors corrected.  But the problem reappears after several days.  The bridgehead for the AD is at Corp HQ and so all other DC's in the satellite offices 'should' replicate directly with that server.  When things are working the automatic NTDS connections in sites and services correctly point to the CorpHQ server, but once problems develop, multiple automatic connection objects are created to multiple sites to try to replicate but they all fail.    The symptom is that RPC communication fails and issues such as logging /mapping drivers to the satellite server is affected in addition to the obvious AD issues so if left it eventually directly affects users.   Communication between sites is via a Cisco hardware VPN (most sites have t1's) and I have done various tests to show that there is no sign of any other sort of connection problem when this occurs - it appears to be a Windows issue completely.

Suggestions?
0
thefumbler
Asked:
thefumbler
  • 11
  • 8
1 Solution
 
joedoe58Commented:
You have some good steps to take here: http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/maintain/opsguide/part1/adogd11.mspx
You also have two monitoring tools sonar and ultrasound. Sonar is easy to use and will give you a general idea when there is a problem on the horizon.
http://www.microsoft.com/windowsserver2003/technologies/storage/dfs/tshootfrs.mspx
0
 
thefumblerAuthor Commented:
I reviewed the links but still need more direction.  Most of the steps in troubleshooting for FRS don't seem to apply though.  Ultrasound looks a bit too complicated and requires a lot of attention, and while Sonar seems simpler but I am not sure what to look for.

Rebooting the problematic DC and then forcing the replication in Sites and Services on the NTDS object gets a good replication as reported in replmon.  But once a hickup occurs, replication attempts just mount and nothing less than a reboot seems to work.  Eventually network communication suffers.
0
 
joedoe58Commented:
Have you tried to install Sonar? If you have can you see a lot of backlog when the problem occurs? Is there a problem with just one server? Can it be a network problem?
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
thefumblerAuthor Commented:
Yes I installed Sonar, taking a better look at it now when another problem developed overnight.   Using a 10 min refresh, all of the 15 DC's "succeed" except the one with the problem which reports "failed" .   This is consistent with the problem - once a problem starts  there is no replication communication.  There is one interesting statistic on the main bridgehead server in CorpHQ - right now there is a count of 1254 in the backlog column and a count of 2 in the column for LongJoinCycle.  

I do not think it is a network problem because there are no other signs that something might have occurred....for example pings are always fine, even during problems, rebooting the server immediately solves the problem, and connectivity to and from other workstations in that office are not affected.  There seems to be SOMETHING on the DC itself, perhaps an application issue which corrupts one of the replication cycles and then it always fails thereafter, even the new replication links which are automatically created as new NTDS objects to other sites.  But its very strange, we went for about 5 days without any replication problems.  Then problems will develop, one DC link goes bad one day, another DC the next day and will multiply until I can reboot those DC's.  Stopping and starting the FRS service does not help.
0
 
thefumblerAuthor Commented:
I rebooted the offending server tonight just after hours as users were beginning to report problems connecting to it.  Prior to a reboot, in Sonar the backlog files were increasing to about 2700 for the CorpHQ server.  The problem server still reported "failed".  About 15 minutes after the reboot and forced replication, Sonar reported 0 backlogged files on CorpHQ and the problem server was no longer "failed" - and everything looks ok for the time being until the next problem.

The event viewer for FRS  on the problem machine reported a 13508 error that it couldn't connect at about 2:00 a.m. early this morning and thereafter failed with no corresponding 13509 success.  There is nothing that I am aware of that would impact it at that time - obviously very little WAN traffic.
0
 
thefumblerAuthor Commented:
yes... following the Procedures for Troubleshooting FRS Event 13508 without Event 13509:

1.  problem varies between server
2.  Yes all DC;s have this similar output
NtFrsApi Version Information
   NtFrsApi Major      : 0
   NtFrsApi Minor      : 0
   NtFrsApi Compiled on: Mar 24 2003 22:02:46
NtFrs Version Information
   NtFrs Major        : 0
   NtFrs Minor        : 0
   NtFrs Compiled on  : Mar 24 2003 22:03:35
   Latest changes:
   Server 2003 01-07-2003
OS Version 5.2 (3790) -
SP (0.0) SM: 0x0110  PT: 0x02
Processor:  INTEL Level: 0x0006  Revision: 0x080a  Processor num/mask: 1/0000000
3. Yes it has replicated before, no apparent networking change or bandwidth issues.
4. nothing between the 2 DC's like firewall.
5. AD is working.
0
 
joedoe58Commented:
Did you check that the time on the servers are correct?
0
 
thefumblerAuthor Commented:
Perhaps you are on to something.  

Using w32t /monitor I discovered that one of the DC's at a small office with only a handful of users was about -300 offset or about 5 min behind from the CorpHQ and the rest of the servers and had 0.0.0.0 in the Refid section

DC2.a.a.com [x.x.x.x]:
    ICMP: 0ms delay.
    NTP: -301.2185845s offset from CorpHQDC1.a.a.com
        RefID: unspecified / unsynchronized [0.0.0.0]

I have corrected the time and the reference server so that it is now correct and all the 15 DC's correctly refer back to the CorpHQ server for time and are generally accurate at no more than 1.5 seconds off.  

If this was the issue, it seems strange that it would affect much more utilized servers across the domain as I don't even recall an issue with this particular DC. Typically when replications fails I see NTDS objects automatically created at sites which I know have more users and traffic in general.  But I will monitor it to see if that appears to fix it.  
0
 
thefumblerAuthor Commented:
Nope time can't be the problem.  Discovered another replication problem (4 hours with 21 attempts since 7pm tonight) with a completely different DC.  It was within .006 seconds of the CorpHQ server.  

Other suggestions?
0
 
joedoe58Commented:
Did you try dcdiag and netdiag on the dc's when they have a replication problem?
0
 
thefumblerAuthor Commented:
Yes, here's a dcdiag and netdiag log the other night (sanitized) from a PH-DC server while it can't replicate....which looks like there are huge problems, but after a reboot everything is fine.  Same thing happened early this morning at about 4am to another DC when nothing was happening at all, another at 10:30am and another at 11:00a.m.  Reboot, check topology and force replication and that server is ok for a while.  In this latest round, I did find that there was an non-existent old NT4 DC being listed as a DC and stripped it out via ADSIEdit so maybe that will help.   But the pattern seems to be that it affects all DC's sooner or later and then life will be good for a while, until the next problem.  

=========================
5/26/2005 11:00PM
DCdiag on PH-DC
Domain Controller Diagnosis
=========================
Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   
   Testing server: WestPH\PH-DC
      Starting test: Connectivity
         ......................... PH-DC passed test Connectivity

Doing primary tests
   
   Testing server: WestPH\PH-DC
      Starting test: Replications
         [Replications Check,PH-DC] No replication recently attempted:
            From CorpHQ to PH-DC
            Naming Context: DC=ForestDnsZones,DC=corp,DC=mydomain,DC=com
            The last attempt occurred at 2005-05-26 11:13:52 (about 6 hours ago).
         [Replications Check,PH-DC] No replication recently attempted:
            From CorpHQ to PH-DC
            Naming Context: DC=DomainDnsZones,DC=corp,DC=mydomain,DC=com
            The last attempt occurred at 2005-05-26 11:13:52 (about 6 hours ago).
         [Replications Check,PH-DC] A recent replication attempt failed:
            From CorpHQ to PH-DC
            Naming Context: CN=Schema,CN=Configuration,DC=corp,DC=mydomain,DC=com
            The replication generated an error (1727):
            The remote procedure call failed and did not execute.
            The failure occurred at 2005-05-26 17:34:47.
            The last success occurred at 2005-05-26 11:13:52.
            18 failures have occurred since the last success.
         [Replications Check,PH-DC] A recent replication attempt failed:
            From CorpHQ to PH-DC
            Naming Context: CN=Configuration,DC=corp,DC=mydomain,DC=com
            The replication generated an error (1727):
            The remote procedure call failed and did not execute.
            The failure occurred at 2005-05-26 17:47:24.
            The last success occurred at 2005-05-26 11:13:52.
            21 failures have occurred since the last success.
         [Replications Check,PH-DC] A recent replication attempt failed:
            From CorpHQ to PH-DC
            Naming Context: DC=corp,DC=mydomain,DC=com
            The replication generated an error (1727):
            The remote procedure call failed and did not execute.
            The failure occurred at 2005-05-26 13:03:30.
            The last success occurred at 2005-05-26 11:13:52.
            3 failures have occurred since the last success.
         REPLICATION-RECEIVED LATENCY WARNING
         PH-DC:  Current time is 2005-05-26 17:47:34.
            DC=DomainDnsZones,DC=corp,DC=mydomain,DC=com
               Last replication recieved from NY-DC at 2005-05-26 04:31:44.
               Last replication recieved from RM-DC at 2005-05-25 23:41:47.
            CN=Schema,CN=Configuration,DC=corp,DC=mydomain,DC=com
               Last replication recieved from RM-DC at 2005-05-25 23:58:38.
               Last replication recieved from TP-DC at 2005-05-25 15:03:09.
            CN=Configuration,DC=corp,DC=mydomain,DC=com
               Last replication recieved from RM-DC at 2005-05-26 00:09:37.
               Last replication recieved from TP-DC at 2005-05-25 15:03:02.
            DC=corp,DC=mydomain,DC=com
               Last replication recieved from HR-DC at 2005-05-25 23:58:42.
               Last replication recieved from WA-DC at 2005-05-26 04:31:39.
               Last replication recieved from SS-DC at 2005-05-26 04:31:41.
               Last replication recieved from NY-DC at 2005-05-26 04:31:41.
               Last replication recieved from PH-DC at 2005-05-26 04:31:44.
               Last replication recieved from DT-DC at 2005-05-26 04:31:44.
               Last replication recieved from WM-DC at 2005-05-25 23:58:45.
               Last replication recieved from SB-DC at 2005-05-25 23:58:42.
               Last replication recieved from RM-DC at 2005-05-25 23:47:57.
               Last replication recieved from FM-DC at 2005-05-26 04:31:43.
               Last replication recieved from IN-DC at 2005-05-26 04:31:39.
               Last replication recieved from TP-DC at 2005-05-25 15:03:12.
               Last replication recieved from LV-DC at 2005-05-26 04:31:43.
         REPLICATION-RECEIVED LATENCY WARNING
          Source site:
         CN=NTDS Site Settings,CN=SoutheastTP,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
          Current time: 2005-05-26 17:47:34
          Last update time: 2005-05-25 14:24:48
          Check if source site has an elected ISTG running.
          Check replication from source site to this server.
         ......................... PH-DC passed test Replications
      Starting test: NCSecDesc
         ......................... PH-DC passed test NCSecDesc
      Starting test: NetLogons
         ......................... PH-DC passed test NetLogons
      Starting test: Advertising
         ......................... PH-DC passed test Advertising
      Starting test: KnowsOfRoleHolders

Domain Controller Diagnosis

Performing initial setup:
   * Verifying that the local machine PH-DC, is a DC.
   * Connecting to directory service on server PH-DC.
   * Collecting site info.
   * Identifying all servers.
   * Identifying all NC cross-refs.
   * Found 16 DC(s). Testing 1 of them.
   Done gathering initial info.

Doing initial required tests
   
   Testing server: WestPH\PH-DC
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... PH-DC passed test Connectivity

Doing primary tests
   
   Testing server: WestPH\PH-DC
      Starting test: Replications
         * Replications Check
         [Replications Check,PH-DC] No replication recently attempted:
            From CorpHQ to PH-DC
            Naming Context: DC=ForestDnsZones,DC=corp,DC=mydomain,DC=com
            The last attempt occurred at 2005-05-26 11:13:52 (about 6 hours ago).
         [Replications Check,PH-DC] No replication recently attempted:
            From CorpHQ to PH-DC
            Naming Context: DC=DomainDnsZones,DC=corp,DC=mydomain,DC=com
            The last attempt occurred at 2005-05-26 11:13:52 (about 6 hours ago).
         [Replications Check,PH-DC] A recent replication attempt failed:
            From CorpHQ to PH-DC
            Naming Context: CN=Schema,CN=Configuration,DC=corp,DC=mydomain,DC=com
            The replication generated an error (1727):
            The remote procedure call failed and did not execute.
            The failure occurred at 2005-05-26 17:34:47.
            The last success occurred at 2005-05-26 11:13:52.
            18 failures have occurred since the last success.
         [Replications Check,PH-DC] A recent replication attempt failed:
            From CorpHQ to PH-DC
            Naming Context: CN=Configuration,DC=corp,DC=mydomain,DC=com
            The replication generated an error (1727):
            The remote procedure call failed and did not execute.
            The failure occurred at 2005-05-26 17:47:24.
            The last success occurred at 2005-05-26 11:13:52.
            21 failures have occurred since the last success.
         [Replications Check,PH-DC] A recent replication attempt failed:
            From CorpHQ to PH-DC
            Naming Context: DC=corp,DC=mydomain,DC=com
            The replication generated an error (1727):
            The remote procedure call failed and did not execute.
            The failure occurred at 2005-05-26 13:03:30.
            The last success occurred at 2005-05-26 11:13:52.
            3 failures have occurred since the last success.
         PH-DC: There are 7 replication work items in the queue.
         REPLICATION LATENCY WARNING
         PH-DC: A long-running replication operation is in progress
            The job has been executing for 5 minutes and 30 seconds.
            Replication of new changes along this path will be delayed.
            Error: Higher priority replications are being blocked
            Enqueued 2005-05-26 17:28:52 at priority 170
            Op: SYNC FROM SOURCE
            NC CN=Schema,CN=Configuration,DC=corp,DC=mydomain,DC=com
            DSADN CN=NTDS Settings,CN=CorpHQ,CN=Servers,CN=MidwestCH,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
            DSA transport addr e93198e9-6398-4f69-9c6a-3993f55fdff6._msdcs.corp.mydomain.com
         * Replication Latency Check
            DC=ForestDnsZones,DC=corp,DC=mydomain,DC=com
               Latency information for 1 entries in the vector were ignored.
                  1 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).  
         REPLICATION-RECEIVED LATENCY WARNING
         PH-DC:  Current time is 2005-05-26 17:59:13.
            DC=DomainDnsZones,DC=corp,DC=mydomain,DC=com
               Last replication recieved from NY-DC at 2005-05-26 04:31:44.
               Last replication recieved from RM-DC at 2005-05-25 23:41:47.
               Latency information for 1 entries in the vector were ignored.
                  1 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=corp,DC=mydomain,DC=com
               Last replication recieved from RM-DC at 2005-05-25 23:58:38.
               Last replication recieved from TP-DC at 2005-05-25 15:03:09.
               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=corp,DC=mydomain,DC=com
               Last replication recieved from RM-DC at 2005-05-26 00:09:37.
               Last replication recieved from TP-DC at 2005-05-25 15:03:02.
               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=corp,DC=mydomain,DC=com
               Last replication recieved from HR-DC at 2005-05-25 23:58:42.
               Last replication recieved from WA-DC at 2005-05-26 04:31:39.
               Last replication recieved from SS-DC at 2005-05-26 04:31:41.
               Last replication recieved from NY-DC at 2005-05-26 04:31:41.
               Last replication recieved from PH-DC at 2005-05-26 04:31:44.
               Last replication recieved from DT-DC at 2005-05-26 04:31:44.
               Last replication recieved from WM-DC at 2005-05-25 23:58:45.
               Last replication recieved from SB-DC at 2005-05-25 23:58:42.
               Last replication recieved from RM-DC at 2005-05-25 23:47:57.
               Last replication recieved from FM-DC at 2005-05-26 04:31:43.
               Last replication recieved from IN-DC at 2005-05-26 04:31:39.
               Last replication recieved from TP-DC at 2005-05-25 15:03:12.
               Last replication recieved from LV-DC at 2005-05-26 04:31:43.
               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).  
         * Replication Site Latency Check
         REPLICATION-RECEIVED LATENCY WARNING
          Source site:
         CN=NTDS Site Settings,CN=SoutheastTP,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
          Current time: 2005-05-26 17:59:13
          Last update time: 2005-05-25 14:24:48
          Check if source site has an elected ISTG running.
          Check replication from source site to this server.
         ......................... PH-DC passed test Replications
      Test omitted by user request: Topology
      Test omitted by user request: CutoffServers
      Starting test: NCSecDesc
         * Security Permissions Check for
           DC=ForestDnsZones,DC=corp,DC=mydomain,DC=com
            (NDNC,Version 2)
         * Security Permissions Check for
           DC=DomainDnsZones,DC=corp,DC=mydomain,DC=com
            (NDNC,Version 2)
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=corp,DC=mydomain,DC=com
            (Schema,Version 2)
         * Security Permissions Check for
           CN=Configuration,DC=corp,DC=mydomain,DC=com
            (Configuration,Version 2)
         * Security Permissions Check for
           DC=corp,DC=mydomain,DC=com
            (Domain,Version 2)
         ......................... PH-DC passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... PH-DC passed test NetLogons
      Starting test: Advertising
         The DC PH-DC is advertising itself as a DC and having a DS.
         The DC PH-DC is advertising as an LDAP server
         The DC PH-DC is advertising as having a writeable directory
         The DC PH-DC is advertising as a Key Distribution Center
         The DC PH-DC is advertising as a time server
         The DS PH-DC is advertising as a GC.
         ......................... PH-DC passed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=CorpHQ2,CN=Servers,CN=MidwestCH,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
         [CorpHQ2] DsBindWithSpnEx() failed with error 1727,
         The remote procedure call failed and did not execute..
         Printing RPC Extended Error Info:
         Error Record 1, ProcessID is 3056 (DcDiag)        
            System Time is: 5/27/2005 0:5:32:128
            Generating component is 8 (winsock)
            Status is -1073606647: unknown
            Detection location is 292
         Error Record 2, ProcessID is 3056 (DcDiag)        
            System Time is: 5/27/2005 0:5:32:128
            Generating component is 8 (winsock)
            Status is 64: The specified network name is no longer available.
            Detection location is 290
            NumberOfParameters is 1
            Long val: 0
         Warning: CorpHQ2 is the Schema Owner, but is not responding to DS RPC Bind.
         Printing RPC Extended Error Info:
         Error Record 1, ProcessID is 3056 (DcDiag)        
            System Time is: 5/27/2005 0:5:32:128
            Generating component is 8 (winsock)
            Status is -1073606647: unknown
            Detection location is 292
         Error Record 2, ProcessID is 3056 (DcDiag)        
            System Time is: 5/27/2005 0:5:32:128
            Generating component is 8 (winsock)
            Status is 64: The specified network name is no longer available.
            Detection location is 290
            NumberOfParameters is 1
            Long val: 0
         [CorpHQ2] LDAP bind failed with error 1053,
         The service did not respond to the start or control request in a timely fashion..
         Warning: CorpHQ2 is the Schema Owner, but is not responding to LDAP Bind.
         Role Domain Owner = CN=NTDS Settings,CN=CorpHQ2,CN=Servers,CN=MidwestCH,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
         Warning: CorpHQ2 is the Domain Owner, but is not responding to DS RPC Bind.
         RPC Extended Error Info not available. Use group policy on the local machine at "Computer Configuration/Administrative Templates/System/Remote Procedure Call" to enable it.
         Warning: CorpHQ2 is the Domain Owner, but is not responding to LDAP Bind.
         Role PDC Owner = CN=NTDS Settings,CN=CorpHQ,CN=Servers,CN=MidwestCH,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
         [CorpHQ] DsBindWithSpnEx() failed with error 1727,
         The remote procedure call failed and did not execute..
         Printing RPC Extended Error Info:
         Error Record 1, ProcessID is 3056 (DcDiag)        
            System Time is: 5/27/2005 0:12:20:762
            Generating component is 8 (winsock)
            Status is -1073606647: unknown
            Detection location is 292
         Error Record 2, ProcessID is 3056 (DcDiag)        
            System Time is: 5/27/2005 0:12:20:762
            Generating component is 8 (winsock)
            Status is 64: The specified network name is no longer available.
            Detection location is 290
            NumberOfParameters is 1
            Long val: 0
         Warning: CorpHQ is the PDC Owner, but is not responding to DS RPC Bind.
         Printing RPC Extended Error Info:
         Error Record 1, ProcessID is 3056 (DcDiag)        
            System Time is: 5/27/2005 0:12:20:762
            Generating component is 8 (winsock)
            Status is -1073606647: unknown
            Detection location is 292
         Error Record 2, ProcessID is 3056 (DcDiag)        
            System Time is: 5/27/2005 0:12:20:762
            Generating component is 8 (winsock)
            Status is 64: The specified network name is no longer available.
            Detection location is 290
            NumberOfParameters is 1
            Long val: 0
         [CorpHQ] LDAP bind failed with error 1053,
         The service did not respond to the start or control request in a timely fashion..
         Warning: CorpHQ is the PDC Owner, but is not responding to LDAP Bind.
         Role Rid Owner = CN=NTDS Settings,CN=CorpHQ2,CN=Servers,CN=MidwestCH,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
         Warning: CorpHQ2 is the Rid Owner, but is not responding to DS RPC Bind.
         RPC Extended Error Info not available. Use group policy on the local machine at "Computer Configuration/Administrative Templates/System/Remote Procedure Call" to enable it.
         Warning: CorpHQ2 is the Rid Owner, but is not responding to LDAP Bind.
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=CorpHQ2,CN=Servers,CN=MidwestCH,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
         Warning: CorpHQ2 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
         RPC Extended Error Info not available. Use group policy on the local machine at "Computer Configuration/Administrative Templates/System/Remote Procedure Call" to enable it.
         Warning: CorpHQ2 is the Infrastructure Update Owner, but is not responding to LDAP Bind.
         ......................... PH-DC failed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 12763 to 1073741823
         * CorpHQ2.corp.mydomain.com is the RID Master
         ......................... PH-DC failed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/PH-DC.corp.mydomain.com/corp.mydomain.com
         * SPN found :LDAP/PH-DC.corp.mydomain.com
         * SPN found :LDAP/PH-DC
         * SPN found :LDAP/PH-DC.corp.mydomain.com/MyDomain
         * SPN found :LDAP/ad8f5cae-6dca-40d9-baae-66e569fdf9dc._msdcs.corp.mydomain.com
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/ad8f5cae-6dca-40d9-baae-66e569fdf9dc/corp.mydomain.com
         * SPN found :HOST/PH-DC.corp.mydomain.com/corp.mydomain.com
         * SPN found :HOST/PH-DC.corp.mydomain.com
         * SPN found :HOST/PH-DC
         * SPN found :HOST/PH-DC.corp.mydomain.com/MyDomain
         * SPN found :GC/PH-DC.corp.mydomain.com/corp.mydomain.com
         ......................... PH-DC passed test MachineAccount
      Starting test: Services
         * Checking Service: Dnscache
         * Checking Service: NtFrs
         * Checking Service: IsmServ
         * Checking Service: kdc
         * Checking Service: SamSs
         * Checking Service: LanmanServer
         * Checking Service: LanmanWorkstation
         * Checking Service: RpcSs
         * Checking Service: w32time
         * Checking Service: NETLOGON
         ......................... PH-DC passed test Services
      Test omitted by user request: OutboundSecureChannels
      Starting test: ObjectsReplicated
         PH-DC is in domain DC=corp,DC=mydomain,DC=com
         Checking for CN=PH-DC,OU=Domain Controllers,DC=corp,DC=mydomain,DC=com in domain DC=corp,DC=mydomain,DC=com on 1 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=PH-DC,CN=Servers,CN=WestPH,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com in domain CN=Configuration,DC=corp,DC=mydomain,DC=com on 1 servers
            Object is up-to-date on all servers.
         ......................... PH-DC passed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service SYSVOL ready test
         File Replication Service's SYSVOL is ready
         ......................... PH-DC passed test frssysvol
      Starting test: frsevent
         * The File Replication Service Event log test
         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 Warning Event occured.  EventID: 0x800034C4
            Time Generated: 05/26/2005   13:32:12
            Event String: The File Replication Service is having trouble
enabling replication from RM-DC to PH-DC for
c:\windows\sysvol\domain using the DNS name
RM-DC.corp.mydomain.com. FRS will keep
retrying.
 Following are some of the reasons you would see
this warning.
 
 [1] FRS can not correctly resolve the DNS name
RM-DC.corp.mydomain.com from this
computer.
 [2] FRS is not running on
RM-DC.corp.mydomain.com.
 [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.
         An Warning Event occured.  EventID: 0x800034C4
            Time Generated: 05/26/2005   16:17:12
            Event String: The File Replication Service is having trouble
enabling replication from IN-DC to PH-DC for
c:\windows\sysvol\domain using the DNS name
IN-DC.corp.mydomain.com. FRS will keep
retrying.
 Following are some of the reasons you would see
this warning.
 
 [1] FRS can not correctly resolve the DNS name
IN-DC.corp.mydomain.com from this
computer.
 [2] FRS is not running on
IN-DC.corp.mydomain.com.
 [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.
         ......................... PH-DC failed test frsevent
      Starting test: kccevent
         * The KCC Event log test
         An Warning Event occured.  EventID: 0x80000785
            Time Generated: 05/26/2005   18:06:20
            Event String: The attempt to establish a replication link for
the following writable directory partition
failed.
 
Directory partition:
CN=Configuration,DC=corp,DC=mydomain,DC=com

Source domain controller:
CN=NTDS Settings,CN=IN-DC,CN=Servers,CN=MidwestIN,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
 
Source domain controller address:
71943f7e-8718-439f-930f-b45fe732bd46._msdcs.corp.mydomain.com
 
Intersite transport (if any):
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
 
 
This domain controller will be unable to
replicate with the source domain controller until
this problem is corrected.  
 
User Action
Verify if the source domain controller is
accessible or network connectivity is available.
 
Additional Data
Error value:
1727
The remote procedure call failed and did not execute.

         ......................... PH-DC failed test kccevent
      Starting test: systemlog
         * The System Event log test
         Found no errors in System Event log in the last 60 minutes.
         ......................... PH-DC passed test systemlog
      Test omitted by user request: VerifyReplicas
      Starting test: VerifyReferences
         The system object reference (serverReference)
         CN=PH-DC,OU=Domain Controllers,DC=corp,DC=mydomain,DC=com and backlink on
         CN=PH-DC,CN=Servers,CN=WestPH,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
          are correct.
         The system object reference (frsComputerReferenceBL)
         CN=PH-DC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=corp,DC=mydomain,DC=com
         and backlink on CN=PH-DC,OU=Domain Controllers,DC=corp,DC=mydomain,DC=com
         are correct.
         The system object reference (serverReferenceBL)
         CN=PH-DC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=corp,DC=mydomain,DC=com
         and backlink on
         CN=NTDS Settings,CN=PH-DC,CN=Servers,CN=WestPH,CN=Sites,CN=Configuration,DC=corp,DC=mydomain,DC=com
         are correct.
         ......................... PH-DC passed test VerifyReferences
      Test omitted by user request: VerifyEnterpriseReferences
   
   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 : corp
      Starting test: CrossRefValidation
         ......................... corp passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... corp passed test CheckSDRefDom
   
   Running enterprise tests on : corp.mydomain.com
      Starting test: Intersite
         Skipping site SoutheastFM, this site is outside the scope provided by the command line arguments provided.
         Skipping site SoutheastSS, this site is outside the scope provided by the command line arguments provided.
         Skipping site WestPH, this site is outside the scope provided by the command line arguments provided.
         Skipping site SoutheastTP, this site is outside the scope provided by the command line
         arguments provided.
         Skipping site EastRM, this site is outside the scope provided by the command line arguments provided.
         Skipping site EastWM, this site is outside the scope provided by the command line arguments provided.
         Skipping site MidwestIN, this site is outside the scope provided by the
         command line arguments provided.
         Skipping site WestLV, this site is outside the scope provided by the command line arguments provided.
         Skipping site MidwestSB, this site is outside the scope provided by the command line arguments provided.
         Skipping site East-WA, this site is outside the scope provided by the command line arguments provided.
         Skipping site EastHR, this site is outside the scope provided by the command line arguments provided.
         Skipping site MidwestCH, this site is outside the scope provided by the command line arguments provided.
         Skipping site EastPH, this site is outside the scope provided by the command line arguments provided.
         Skipping site MidwestDT, this site is outside the scope provided by the command line arguments provided.
         Skipping site EastNY, this site is outside the scope provided by the command line arguments provided.
         ......................... corp.mydomain.com passed test Intersite
      Starting test: FsmoCheck
         GC Name: \\PH-DC.corp.mydomain.com
         Locator Flags: 0xe00001fc
         PDC Name: \\CorpHQ.corp.mydomain.com
         Locator Flags: 0xe000017d
         Time Server Name: \\PH-DC.corp.mydomain.com
         Locator Flags: 0xe00001fc
         Preferred Time Server Name: \\PH-DC.corp.mydomain.com
         Locator Flags: 0xe00001fc
         KDC Name: \\PH-DC.corp.mydomain.com
         Locator Flags: 0xe00001fc
         ......................... corp.mydomain.com passed test FsmoCheck

=========================
5/26/2005 11:02PM
Netdiag on PH-DC
=========================
    Gathering IPX configuration information.
    Querying status of the Netcard drivers... Passed
    Testing IpConfig - pinging the Primary WINS server... Passed
    Testing IpConfig - pinging the Secondary WINS server... Passed
    Testing Domain membership... Passed
    Gathering NetBT configuration information.
    Testing for autoconfiguration... Passed
    Testing IP loopback ping... Passed
    Testing default gateways... Passed
    Enumerating local and remote NetBT name cache... Passed
    Testing the WINS server
        Local Area Connection
            Sending name query to primary WINS server 192.168.14.10 - Passed
            Sending name query to secondary WINS server 192.168.30.12 - Passed
    Gathering Winsock information.
    Testing DNS
    PASS - All the DNS entries for DC are registered on DNS server '192.168.30.7' and other DCs also have some of the names registered.
    PASS - All the DNS entries for DC are registered on DNS server '192.168.14.10' and other DCs also have some of the names registered.
    Testing redirector and browser... Passed
    Testing DC discovery.
        Looking for a DC
        Looking for a PDC emulator
        Looking for a Windows 2000 DC
    Gathering the list of Domain Controllers for domain 'MyDomain'
    Testing trust relationships... Passed
    Testing Kerberos authentication... Passed
    Testing LDAP servers in Domain MyDomain ...
    Gathering routing information
    Gathering network statistics information.
    Gathering configuration of bindings.
    Gathering RAS connection information
    Gathering Modem information
    Gathering Netware information
    Gathering IP Security information

    Tests complete.


    Computer Name: PH-DC
    DNS Host Name: PH-DC.corp.mydomain.com
    DNS Domain Name: corp.mydomain.com
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 6 Model 11 Stepping 1, GenuineIntel
    Hotfixes :
        Installed?      Name
           Yes          KB819696
           Yes          KB823182
           Yes          KB823353
           Yes          KB823559
           Yes          KB824105
           Yes          KB824141
           Yes          KB825119
           Yes          KB828035
           Yes          KB828741
           Yes          KB830352
           Yes          KB833987
           Yes          KB834707
           Yes          KB835732
           Yes          KB837001
           Yes          KB839643
           Yes          KB839645
           Yes          KB840315
           Yes          KB840374
           Yes          KB840987
           Yes          KB841356
           Yes          KB841533
           Yes          KB842773
           Yes          KB867282
           Yes          KB867460
           Yes          KB870763
           Yes          KB871250
           Yes          KB873333
           Yes          KB873339
           Yes          KB873376
           Yes          KB885250
           Yes          KB885834
           Yes          KB885835
           Yes          KB885836
           Yes          KB886903
           Yes          KB888113
           Yes          KB890047
           Yes          KB890175
           Yes          KB890859
           Yes          KB890923
           Yes          KB891711
           Yes          KB891781
           Yes          KB893066
           Yes          KB893086
           Yes          KB893803
           Yes          KB893803v2
           Yes          Q147222
           Yes          Q828026


Netcard queries test . . . . . . . : Passed

    Information of Netcard drivers:

    ---------------------------------------------------------------------------
    Description: Intel(R) PRO/100 Network Connection
    Device: \DEVICE\{E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}

    Media State:                     Connected

    Device State:                    Connected
    Connect Time:                    8 days, 14:43:49
    Media Speed:                     100 Mbps

    Packets Sent:                    271852105
    Bytes Sent (Optional):           0

    Packets Received:                200313078
    Directed Pkts Recd (Optional):   199840036
    Bytes Received (Optional):       0
    Directed Bytes Recd (Optional):  0

    ---------------------------------------------------------------------------
    [PASS] - At least one netcard is in the 'Connected' state.



Per interface results:

    Adapter : Local Area Connection
        Adapter ID . . . . . . . . : {E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}

        Netcard queries test . . . : Passed

        Adapter type . . . . . . . : Ethernet
        Host Name. . . . . . . . . : PH-DC
        Description. . . . . . . . : Intel(R) PRO/100 Network Connection
        Physical Address . . . . . : 00-06-5B-39-71-D7
        Dhcp Enabled . . . . . . . : No
        DHCP ClassID . . . . . . . :
        Autoconfiguration Enabled. : Yes
        IP Address . . . . . . . . : 192.168.14.10
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.14.1
        Primary WINS Server. . . . : 192.168.14.10
        Secondary WINS Server. . . : 192.168.30.12
        Dns Servers. . . . . . . . : 192.168.30.7
                                     192.168.14.10

        IpConfig results . . . . . : Passed
            Pinging the Primary WINS server 192.168.14.10 - reachable
            Pinging the Secondary WINS server 192.168.30.12 - reachable

        AutoConfiguration results. . . . . . : Passed
            AutoConfiguration is not in use.

        Default gateway test . . . : Passed
            Pinging gateway 192.168.14.1 - reachable
            At least one gateway reachable for this adapter.

        NetBT name test. . . . . . : Passed
            NetBT_Tcpip_{E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}
            PH-DC         <00>  UNIQUE      REGISTERED
            MyDomain        <00>  GROUP       REGISTERED
            MyDomain        <1C>  GROUP       REGISTERED
            PH-DC         <20>  UNIQUE      REGISTERED
            MyDomain        <1E>  GROUP       REGISTERED
            MyDomain        <1D>  UNIQUE      REGISTERED
            ..__MSBROWSE__.<01>  GROUP       REGISTERED
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.

            NetBios Resolution : via DHCP

            Netbios Remote Cache Table
            Name           Type              HostAddress         Life [sec]
            ---------------------------------------------------------------
            MyDomain        <1C>  GROUP       192.168.30.12         475
            CorpHQ.CORP.GR<45>  UNIQUE      192.168.30.12         475
            CorpHQ        <20>  UNIQUE      192.168.30.12         90


        WINS service test. . . . . : Passed
            Sending name query to primary WINS server 192.168.14.10 - Passed
            Sending name query to secondary WINS server 192.168.30.12 - Passed
            The test was successful. At least one WINS server was found.
        IPX test : IPX is not installed on this machine.


Global results:


IP General configuration
    LMHOSTS Enabled. . . . . . . . : Yes
    DNS for WINS resolution. . . . : Enabled
    Node Type. . . . . . . . . . . : Hybrid
    NBT Scope ID . . . . . . . . . :
    Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled . . . . . . : No
    DNS resolution for NETBIOS . . : No



Domain membership test . . . . . . : Passed
    Machine is a . . . . . . . . . : Domain Controller
    Netbios Domain name. . . . . . : MyDomain
    Dns domain name. . . . . . . . : corp.mydomain.com
    Dns forest name. . . . . . . . : corp.mydomain.com
    Domain Guid. . . . . . . . . . : {AFE9DF5A-0DDA-4F77-9420-E1FE2D719007}
    Domain Sid . . . . . . . . . . : S-1-5-21-1816858842-627311984-9522986
    Logon User . . . . . . . . . . : MyDomain_setup
    Logon Domain . . . . . . . . . : MyDomain


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}
    1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed
    PASS - you have at least one non-autoconfigured IP address


IP loopback ping test. . . . . . . : Passed
    PASS - pinging IP loopback address was successful.
    Your IP stack is most probably OK.


Default gateway test . . . . . . . : Passed
    PASS - you have at least one reachable gateway.


NetBT name test. . . . . . . . . . : Passed
   No NetBT scope defined
    [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed
    The number of protocols which have been reported : 10
        Description: MSAFD Tcpip [TCP/IP]
            Provider Version   :2
            Max message size  : Stream Oriented
        Description: MSAFD Tcpip [UDP/IP]
            Provider Version   :2
        Description: RSVP UDP Service Provider
            Provider Version   :6
        Description: RSVP TCP Service Provider
            Provider Version   :6
            Max message size  : Stream Oriented
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}] SEQPACKET 0
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}] DATAGRAM 0
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{69D54651-5C56-48FF-89DB-F375FB6269B1}] SEQPACKET 1
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{69D54651-5C56-48FF-89DB-F375FB6269B1}] DATAGRAM 1
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{D9F6780F-B814-4DD2-8F82-CCA8B4E6312B}] SEQPACKET 2
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{D9F6780F-B814-4DD2-8F82-CCA8B4E6312B}] DATAGRAM 2
            Provider Version   :2

    Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
      Interface {E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}
        DNS Domain:
        DNS Servers: 192.168.30.7 192.168.14.10
        IP Address:         Expected registration with PDN (primary DNS domain name):
          Hostname: PH-DC.corp.mydomain.com.
          Authoritative zone: corp.mydomain.com.
          Primary DNS server: CorpHQ2.corp.mydomain.com 192.168.30.7
          Authoritative NS:192.168.2.10 192.168.12.10 192.168.3.10 192.168.17.10 192.168.1.10 192.168.15.10 192.168.30.7
Check the DNS registration for DCs entries on DNS server '192.168.30.7'
The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = corp.mydomain.com.
DNS DATA =
            A  192.168.14.10

The record on DNS server 192.168.30.7 is:
DNS NAME = corp.mydomain.com
DNS DATA =
            A  192.168.14.10
            A  192.168.30.7
            A  192.168.1.10
            A  192.168.17.10
            A  192.168.3.10
            A  192.168.12.10
            A  192.168.2.10
            A  192.168.30.18
            A  192.168.19.10
            A  192.168.30.12
            A  192.168.6.10
            A  192.168.16.10
            A  192.168.5.10
            A  192.168.4.10
            A  192.168.13.10
            A  192.168.15.10
            A  192.168.7.10
+------------------------------------------------------+

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _ldap._tcp.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.30.7'.

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.afe9df5a-0dda-4f77-9420-e1fe2d719007.domains._msdcs.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _ldap._tcp.afe9df5a-0dda-4f77-9420-e1fe2d719007.domains._msdcs.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.30.7'.

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dc._msdcs.corp.mydomain.com.
DNS DATA =
            SRV 0 100 88 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _kerberos._tcp.dc._msdcs.corp.mydomain.com
DNS DATA =
            SRV 0 100 88 LV-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ.corp.mydomain.com
            SRV 0 100 88 HR-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ2.corp.mydomain.com
            SRV 0 100 88 WM-DC.corp.mydomain.com
            SRV 0 100 88 FM-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 DT-DC.corp.mydomain.com
            SRV 0 100 88 IN-DC.corp.mydomain.com
            SRV 0 100 88 SS-DC.corp.mydomain.com
            SRV 0 100 88 TP-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 NY-DC.corp.mydomain.com
            SRV 0 100 88 WA-DC.corp.mydomain.com
            SRV 0 100 88 RM-DC.corp.mydomain.com
            SRV 0 100 88 SB-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.30.7'.

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dc._msdcs.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _ldap._tcp.dc._msdcs.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.30.7'.

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 88 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _kerberos._tcp.corp.mydomain.com
DNS DATA =
            SRV 0 100 88 LV-DC.corp.mydomain.com
            SRV 0 100 88 NY-DC.corp.mydomain.com
            SRV 0 100 88 HR-DC.corp.mydomain.com
            SRV 0 100 88 DT-DC.corp.mydomain.com
            SRV 0 100 88 WA-DC.corp.mydomain.com
            SRV 0 100 88 SB-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ.corp.mydomain.com
            SRV 0 100 88 IN-DC.corp.mydomain.com
            SRV 0 100 88 WM-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 SS-DC.corp.mydomain.com
            SRV 0 100 88 TP-DC.corp.mydomain.com
            SRV 0 100 88 RM-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ2.corp.mydomain.com
            SRV 0 100 88 FM-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.30.7'.

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._udp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 88 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _kerberos._udp.corp.mydomain.com
DNS DATA =
            SRV 0 100 88 LV-DC.corp.mydomain.com
            SRV 0 100 88 NY-DC.corp.mydomain.com
            SRV 0 100 88 HR-DC.corp.mydomain.com
            SRV 0 100 88 DT-DC.corp.mydomain.com
            SRV 0 100 88 WA-DC.corp.mydomain.com
            SRV 0 100 88 SB-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ.corp.mydomain.com
            SRV 0 100 88 IN-DC.corp.mydomain.com
            SRV 0 100 88 WM-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 SS-DC.corp.mydomain.com
            SRV 0 100 88 TP-DC.corp.mydomain.com
            SRV 0 100 88 RM-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ2.corp.mydomain.com
            SRV 0 100 88 FM-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._tcp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 464 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _kpasswd._tcp.corp.mydomain.com
DNS DATA =
            SRV 0 100 464 LV-DC.corp.mydomain.com
            SRV 0 100 464 NY-DC.corp.mydomain.com
            SRV 0 100 464 HR-DC.corp.mydomain.com
            SRV 0 100 464 WA-DC.corp.mydomain.com
            SRV 0 100 464 DT-DC.corp.mydomain.com
            SRV 0 100 464 SB-DC.corp.mydomain.com
            SRV 0 100 464 CorpHQ.corp.mydomain.com
            SRV 0 100 464 IN-DC.corp.mydomain.com
            SRV 0 100 464 WM-DC.corp.mydomain.com
            SRV 0 100 464 PH-DC.corp.mydomain.com
            SRV 0 100 464 SS-DC.corp.mydomain.com
            SRV 0 100 464 TP-DC.corp.mydomain.com
            SRV 0 100 464 RM-DC.corp.mydomain.com
            SRV 0 100 464 PH-DC.corp.mydomain.com
            SRV 0 100 464 CorpHQ2.corp.mydomain.com
            SRV 0 100 464 FM-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._udp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 464 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _kpasswd._udp.corp.mydomain.com
DNS DATA =
            SRV 0 100 464 LV-DC.corp.mydomain.com
            SRV 0 100 464 NY-DC.corp.mydomain.com
            SRV 0 100 464 HR-DC.corp.mydomain.com
            SRV 0 100 464 WA-DC.corp.mydomain.com
            SRV 0 100 464 DT-DC.corp.mydomain.com
            SRV 0 100 464 SB-DC.corp.mydomain.com
            SRV 0 100 464 CorpHQ.corp.mydomain.com
            SRV 0 100 464 IN-DC.corp.mydomain.com
            SRV 0 100 464 WM-DC.corp.mydomain.com
            SRV 0 100 464 PH-DC.corp.mydomain.com
            SRV 0 100 464 SS-DC.corp.mydomain.com
            SRV 0 100 464 TP-DC.corp.mydomain.com
            SRV 0 100 464 RM-DC.corp.mydomain.com
            SRV 0 100 464 PH-DC.corp.mydomain.com
            SRV 0 100 464 CorpHQ2.corp.mydomain.com
            SRV 0 100 464 FM-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.gc._msdcs.corp.mydomain.com.
DNS DATA =
            SRV 0 100 3268 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _ldap._tcp.gc._msdcs.corp.mydomain.com
DNS DATA =
            SRV 0 100 3268 DT-DC.corp.mydomain.com
            SRV 0 100 3268 WA-DC.corp.mydomain.com
            SRV 0 100 3268 HR-DC.corp.mydomain.com
            SRV 0 100 3268 RM-DC.corp.mydomain.com
            SRV 0 100 3268 PH-DC.corp.mydomain.com
            SRV 0 100 3268 CorpHQ.corp.mydomain.com
            SRV 0 100 3268 LV-DC.corp.mydomain.com
            SRV 0 100 3268 SS-DC.corp.mydomain.com
            SRV 0 100 3268 NY-DC.corp.mydomain.com
            SRV 0 100 3268 PH-DC.corp.mydomain.com
            SRV 0 100 3268 FM-DC.corp.mydomain.com
            SRV 0 100 3268 TP-DC.corp.mydomain.com
            SRV 0 100 3268 CorpHQ2.corp.mydomain.com
            SRV 0 100 3268 IN-DC.corp.mydomain.com
            SRV 0 100 3268 SB-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.30.7'.

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = gc._msdcs.corp.mydomain.com.
DNS DATA =
            A  192.168.14.10

The record on DNS server 192.168.30.7 is:
DNS NAME = gc._msdcs.corp.mydomain.com
DNS DATA =
            A  192.168.14.10
            A  192.168.1.10
            A  192.168.16.10
            A  192.168.15.10
            A  192.168.5.10
            A  192.168.6.10
            A  192.168.17.10
            A  192.168.12.10
            A  192.168.3.10
            A  192.168.4.10
            A  192.168.30.12
            A  192.168.30.7
            A  192.168.7.10
            A  192.168.13.10
            A  192.168.2.10
+------------------------------------------------------+

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _gc._tcp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 3268 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _gc._tcp.corp.mydomain.com
DNS DATA =
            SRV 0 100 3268 CorpHQ2.corp.mydomain.com
            SRV 0 100 3268 LV-DC.corp.mydomain.com
            SRV 0 100 3268 HR-DC.corp.mydomain.com
            SRV 0 100 3268 IN-DC.corp.mydomain.com
            SRV 0 100 3268 SS-DC.corp.mydomain.com
            SRV 0 100 3268 TP-DC.corp.mydomain.com
            SRV 0 100 3268 CorpHQ.corp.mydomain.com
            SRV 0 100 3268 DT-DC.corp.mydomain.com
            SRV 0 100 3268 FM-DC.corp.mydomain.com
            SRV 0 100 3268 NY-DC.corp.mydomain.com
            SRV 0 100 3268 WA-DC.corp.mydomain.com
            SRV 0 100 3268 SB-DC.corp.mydomain.com
            SRV 0 100 3268 RM-DC.corp.mydomain.com
            SRV 0 100 3268 PH-DC.corp.mydomain.com
            SRV 0 100 3268 PH-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.30.7'.

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.corp.mydomain.com.
DNS DATA =
            A  192.168.14.10

The record on DNS server 192.168.30.7 is:
DNS NAME = DomainDnsZones.corp.mydomain.com
DNS DATA =
            A  192.168.14.10
            A  192.168.15.10
            A  192.168.30.7
            A  192.168.19.10
            A  192.168.30.12
            A  192.168.5.10
            A  192.168.6.10
            A  192.168.17.10
            A  192.168.12.10
            A  192.168.16.10
            A  192.168.4.10
            A  192.168.7.10
            A  192.168.13.10
            A  192.168.2.10
            A  192.168.3.10
            A  192.168.1.10
+------------------------------------------------------+

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.DomainDnsZones.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _ldap._tcp.DomainDnsZones.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.30.7'.

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = ForestDnsZones.corp.mydomain.com.
DNS DATA =
            A  192.168.14.10

The record on DNS server 192.168.30.7 is:
DNS NAME = ForestDnsZones.corp.mydomain.com
DNS DATA =
            A  192.168.14.10
            A  192.168.15.10
            A  192.168.30.7
            A  192.168.19.10
            A  192.168.30.12
            A  192.168.5.10
            A  192.168.6.10
            A  192.168.17.10
            A  192.168.12.10
            A  192.168.16.10
            A  192.168.4.10
            A  192.168.7.10
            A  192.168.13.10
            A  192.168.2.10
            A  192.168.3.10
            A  192.168.1.10
+------------------------------------------------------+

The Record is different on DNS server '192.168.30.7'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.30.7', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.ForestDnsZones.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.30.7 is:
DNS NAME = _ldap._tcp.ForestDnsZones.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.30.7'.

    PASS - All the DNS entries for DC are registered on DNS server '192.168.30.7' and other DCs also have some of the names registered.
Check the DNS registration for DCs entries on DNS server '192.168.14.10'
The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = corp.mydomain.com.
DNS DATA =
            A  192.168.14.10

The record on DNS server 192.168.14.10 is:
DNS NAME = corp.mydomain.com
DNS DATA =
            A  192.168.14.10
            A  192.168.30.7
            A  192.168.1.10
            A  192.168.17.10
            A  192.168.3.10
            A  192.168.12.10
            A  192.168.2.10
            A  192.168.30.18
            A  192.168.19.10
            A  192.168.30.12
            A  192.168.6.10
            A  192.168.16.10
            A  192.168.5.10
            A  192.168.4.10
            A  192.168.13.10
            A  192.168.15.10
            A  192.168.7.10
+------------------------------------------------------+

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _ldap._tcp.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.14.10'.

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.afe9df5a-0dda-4f77-9420-e1fe2d719007.domains._msdcs.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _ldap._tcp.afe9df5a-0dda-4f77-9420-e1fe2d719007.domains._msdcs.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.14.10'.

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dc._msdcs.corp.mydomain.com.
DNS DATA =
            SRV 0 100 88 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _kerberos._tcp.dc._msdcs.corp.mydomain.com
DNS DATA =
            SRV 0 100 88 NY-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ.corp.mydomain.com
            SRV 0 100 88 WA-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ2.corp.mydomain.com
            SRV 0 100 88 RM-DC.corp.mydomain.com
            SRV 0 100 88 FM-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 SB-DC.corp.mydomain.com
            SRV 0 100 88 LV-DC.corp.mydomain.com
            SRV 0 100 88 HR-DC.corp.mydomain.com
            SRV 0 100 88 WM-DC.corp.mydomain.com
            SRV 0 100 88 DT-DC.corp.mydomain.com
            SRV 0 100 88 IN-DC.corp.mydomain.com
            SRV 0 100 88 SS-DC.corp.mydomain.com
            SRV 0 100 88 TP-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.14.10'.

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dc._msdcs.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _ldap._tcp.dc._msdcs.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.14.10'.

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 88 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _kerberos._tcp.corp.mydomain.com
DNS DATA =
            SRV 0 100 88 RM-DC.corp.mydomain.com
            SRV 0 100 88 HR-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 DT-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ2.corp.mydomain.com
            SRV 0 100 88 CorpHQ.corp.mydomain.com
            SRV 0 100 88 FM-DC.corp.mydomain.com
            SRV 0 100 88 WM-DC.corp.mydomain.com
            SRV 0 100 88 LV-DC.corp.mydomain.com
            SRV 0 100 88 NY-DC.corp.mydomain.com
            SRV 0 100 88 WA-DC.corp.mydomain.com
            SRV 0 100 88 SB-DC.corp.mydomain.com
            SRV 0 100 88 IN-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 SS-DC.corp.mydomain.com
            SRV 0 100 88 TP-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.14.10'.

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._udp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 88 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _kerberos._udp.corp.mydomain.com
DNS DATA =
            SRV 0 100 88 RM-DC.corp.mydomain.com
            SRV 0 100 88 HR-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 DT-DC.corp.mydomain.com
            SRV 0 100 88 CorpHQ2.corp.mydomain.com
            SRV 0 100 88 CorpHQ.corp.mydomain.com
            SRV 0 100 88 FM-DC.corp.mydomain.com
            SRV 0 100 88 WM-DC.corp.mydomain.com
            SRV 0 100 88 LV-DC.corp.mydomain.com
            SRV 0 100 88 NY-DC.corp.mydomain.com
            SRV 0 100 88 WA-DC.corp.mydomain.com
            SRV 0 100 88 SB-DC.corp.mydomain.com
            SRV 0 100 88 IN-DC.corp.mydomain.com
            SRV 0 100 88 PH-DC.corp.mydomain.com
            SRV 0 100 88 SS-DC.corp.mydomain.com
            SRV 0 100 88 TP-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._tcp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 464 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _kpasswd._tcp.corp.mydomain.com
DNS DATA =
            SRV 0 100 464 RM-DC.corp.mydomain.com
            SRV 0 100 464 HR-DC.corp.mydomain.com
            SRV 0 100 464 PH-DC.corp.mydomain.com
            SRV 0 100 464 DT-DC.corp.mydomain.com
            SRV 0 100 464 CorpHQ2.corp.mydomain.com
            SRV 0 100 464 CorpHQ.corp.mydomain.com
            SRV 0 100 464 FM-DC.corp.mydomain.com
            SRV 0 100 464 WM-DC.corp.mydomain.com
            SRV 0 100 464 LV-DC.corp.mydomain.com
            SRV 0 100 464 NY-DC.corp.mydomain.com
            SRV 0 100 464 WA-DC.corp.mydomain.com
            SRV 0 100 464 SB-DC.corp.mydomain.com
            SRV 0 100 464 IN-DC.corp.mydomain.com
            SRV 0 100 464 PH-DC.corp.mydomain.com
            SRV 0 100 464 SS-DC.corp.mydomain.com
            SRV 0 100 464 TP-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._udp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 464 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _kpasswd._udp.corp.mydomain.com
DNS DATA =
            SRV 0 100 464 RM-DC.corp.mydomain.com
            SRV 0 100 464 HR-DC.corp.mydomain.com
            SRV 0 100 464 PH-DC.corp.mydomain.com
            SRV 0 100 464 DT-DC.corp.mydomain.com
            SRV 0 100 464 CorpHQ2.corp.mydomain.com
            SRV 0 100 464 CorpHQ.corp.mydomain.com
            SRV 0 100 464 FM-DC.corp.mydomain.com
            SRV 0 100 464 WM-DC.corp.mydomain.com
            SRV 0 100 464 LV-DC.corp.mydomain.com
            SRV 0 100 464 NY-DC.corp.mydomain.com
            SRV 0 100 464 WA-DC.corp.mydomain.com
            SRV 0 100 464 SB-DC.corp.mydomain.com
            SRV 0 100 464 IN-DC.corp.mydomain.com
            SRV 0 100 464 PH-DC.corp.mydomain.com
            SRV 0 100 464 SS-DC.corp.mydomain.com
            SRV 0 100 464 TP-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.gc._msdcs.corp.mydomain.com.
DNS DATA =
            SRV 0 100 3268 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _ldap._tcp.gc._msdcs.corp.mydomain.com
DNS DATA =
            SRV 0 100 3268 TP-DC.corp.mydomain.com
            SRV 0 100 3268 WA-DC.corp.mydomain.com
            SRV 0 100 3268 CorpHQ2.corp.mydomain.com
            SRV 0 100 3268 RM-DC.corp.mydomain.com
            SRV 0 100 3268 IN-DC.corp.mydomain.com
            SRV 0 100 3268 CorpHQ.corp.mydomain.com
            SRV 0 100 3268 SB-DC.corp.mydomain.com
            SRV 0 100 3268 SS-DC.corp.mydomain.com
            SRV 0 100 3268 DT-DC.corp.mydomain.com
            SRV 0 100 3268 HR-DC.corp.mydomain.com
            SRV 0 100 3268 PH-DC.corp.mydomain.com
            SRV 0 100 3268 LV-DC.corp.mydomain.com
            SRV 0 100 3268 NY-DC.corp.mydomain.com
            SRV 0 100 3268 PH-DC.corp.mydomain.com
            SRV 0 100 3268 FM-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.14.10'.

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = gc._msdcs.corp.mydomain.com.
DNS DATA =
            A  192.168.14.10

The record on DNS server 192.168.14.10 is:
DNS NAME = gc._msdcs.corp.mydomain.com
DNS DATA =
            A  192.168.14.10
            A  192.168.7.10
            A  192.168.13.10
            A  192.168.2.10
            A  192.168.3.10
            A  192.168.1.10
            A  192.168.16.10
            A  192.168.15.10
            A  192.168.5.10
            A  192.168.6.10
            A  192.168.17.10
            A  192.168.12.10
            A  192.168.30.7
            A  192.168.4.10
            A  192.168.30.12
+------------------------------------------------------+

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _gc._tcp.corp.mydomain.com.
DNS DATA =
            SRV 0 100 3268 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _gc._tcp.corp.mydomain.com
DNS DATA =
            SRV 0 100 3268 LV-DC.corp.mydomain.com
            SRV 0 100 3268 HR-DC.corp.mydomain.com
            SRV 0 100 3268 SS-DC.corp.mydomain.com
            SRV 0 100 3268 TP-DC.corp.mydomain.com
            SRV 0 100 3268 DT-DC.corp.mydomain.com
            SRV 0 100 3268 NY-DC.corp.mydomain.com
            SRV 0 100 3268 CorpHQ.corp.mydomain.com
            SRV 0 100 3268 WA-DC.corp.mydomain.com
            SRV 0 100 3268 FM-DC.corp.mydomain.com
            SRV 0 100 3268 CorpHQ2.corp.mydomain.com
            SRV 0 100 3268 SB-DC.corp.mydomain.com
            SRV 0 100 3268 RM-DC.corp.mydomain.com
            SRV 0 100 3268 IN-DC.corp.mydomain.com
            SRV 0 100 3268 PH-DC.corp.mydomain.com
            SRV 0 100 3268 PH-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.14.10'.

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.corp.mydomain.com.
DNS DATA =
            A  192.168.14.10

The record on DNS server 192.168.14.10 is:
DNS NAME = DomainDnsZones.corp.mydomain.com
DNS DATA =
            A  192.168.14.10
            A  192.168.2.10
            A  192.168.3.10
            A  192.168.1.10
            A  192.168.16.10
            A  192.168.15.10
            A  192.168.30.7
            A  192.168.19.10
            A  192.168.30.12
            A  192.168.5.10
            A  192.168.6.10
            A  192.168.17.10
            A  192.168.12.10
            A  192.168.13.10
            A  192.168.4.10
            A  192.168.7.10
+------------------------------------------------------+

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.DomainDnsZones.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _ldap._tcp.DomainDnsZones.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.14.10'.

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = ForestDnsZones.corp.mydomain.com.
DNS DATA =
            A  192.168.14.10

The record on DNS server 192.168.14.10 is:
DNS NAME = ForestDnsZones.corp.mydomain.com
DNS DATA =
            A  192.168.14.10
            A  192.168.2.10
            A  192.168.3.10
            A  192.168.1.10
            A  192.168.16.10
            A  192.168.15.10
            A  192.168.30.7
            A  192.168.19.10
            A  192.168.30.12
            A  192.168.5.10
            A  192.168.6.10
            A  192.168.17.10
            A  192.168.12.10
            A  192.168.13.10
            A  192.168.4.10
            A  192.168.7.10
+------------------------------------------------------+

The Record is different on DNS server '192.168.14.10'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.14.10', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.ForestDnsZones.corp.mydomain.com.
DNS DATA =
            SRV 0 100 389 PH-DC.corp.mydomain.com.

The record on DNS server 192.168.14.10 is:
DNS NAME = _ldap._tcp.ForestDnsZones.corp.mydomain.com
DNS DATA =
            SRV 0 100 389 RM-DC.corp.mydomain.com
            SRV 0 100 389 HR-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 DT-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ2.corp.mydomain.com
            SRV 0 100 389 FM-DC.corp.mydomain.com
            SRV 0 100 389 WM-DC.corp.mydomain.com
            SRV 0 100 389 LV-DC.corp.mydomain.com
            SRV 0 100 389 CorpHQ.corp.mydomain.com
            SRV 0 100 389 NY-DC.corp.mydomain.com
            SRV 0 100 389 WA-DC.corp.mydomain.com
            SRV 0 100 389 SB-DC.corp.mydomain.com
            SRV 0 100 389 IN-DC.corp.mydomain.com
            SRV 0 100 389 PH-DC.corp.mydomain.com
            SRV 0 100 389 SS-DC.corp.mydomain.com
            SRV 0 100 389 TP-DC.corp.mydomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.14.10'.

    PASS - All the DNS entries for DC are registered on DNS server '192.168.14.10' and other DCs also have some of the names registered.


Redir and Browser test . . . . . . : Passed
    List of transports currently bound to the Redir
        NetbiosSmb
        NetBT_Tcpip_{E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}
    The redir is bound to 1 NetBt transport.

    List of transports currently bound to the browser
        NetBT_Tcpip_{E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}
    The browser is bound to 1 NetBt transport.
    Mailslot test for MyDomain* passed.


DC discovery test. . . . . . . . . : Passed

    Find DC in domain 'MyDomain':
    Found this DC in domain 'MyDomain':
        DC. . . . . . . . . . . : \\PH-DC.corp.mydomain.com
        Address . . . . . . . . : \\192.168.14.10
        Domain Guid . . . . . . : {AFE9DF5A-0DDA-4F77-9420-E1FE2D719007}
        Domain Name . . . . . . : corp.mydomain.com
        Forest Name . . . . . . : corp.mydomain.com
        DC Site Name. . . . . . : WestPH
        Our Site Name . . . . . : WestPH
        Flags . . . . . . . . . : GC DS KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

    Find PDC emulator in domain 'MyDomain':
    Found this PDC emulator in domain 'MyDomain':
        DC. . . . . . . . . . . : \\CorpHQ.corp.mydomain.com
        Address . . . . . . . . : \\192.168.30.12
        Domain Guid . . . . . . : {AFE9DF5A-0DDA-4F77-9420-E1FE2D719007}
        Domain Name . . . . . . : corp.mydomain.com
        Forest Name . . . . . . : corp.mydomain.com
        DC Site Name. . . . . . : MidwestCH
        Our Site Name . . . . . : WestPH
        Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST 0x8

    Find Windows 2000 DC in domain 'MyDomain':
    Found this Windows 2000 DC in domain 'MyDomain':
        DC. . . . . . . . . . . : \\PH-DC.corp.mydomain.com
        Address . . . . . . . . : \\192.168.14.10
        Domain Guid . . . . . . : {AFE9DF5A-0DDA-4F77-9420-E1FE2D719007}
        Domain Name . . . . . . : corp.mydomain.com
        Forest Name . . . . . . : corp.mydomain.com
        DC Site Name. . . . . . : WestPH
        Our Site Name . . . . . : WestPH
        Flags . . . . . . . . . : GC DS KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8


DC list test . . . . . . . . . . . : Passed
    List of DCs in Domain 'MyDomain':
        PH-DC.corp.mydomain.com
        CorpHQ.corp.mydomain.com  (this DC is down)
        CorpHQ2.corp.mydomain.com  (this DC is down)
        WM-DC.corp.mydomain.com  (this DC is down)
        DT-DC.corp.mydomain.com  (this DC is down)
        NY-DC.corp.mydomain.com  (this DC is down)
        PH-DC.corp.mydomain.com  (this DC is down)
        WA-DC.corp.mydomain.com
        HR-DC.corp.mydomain.com  (this DC is down)
        SB-DC.corp.mydomain.com  (this DC is down)
        RM-DC.corp.mydomain.com  (this DC is down)
        IN-DC.corp.mydomain.com  (this DC is down)
        LV-DC.corp.mydomain.com  (this DC is down)
        MyDomain_FS
        TP-DC.corp.mydomain.com  (this DC is down)
        SS-DC.corp.mydomain.com  (this DC is down)
        FM-DC.corp.mydomain.com  (this DC is down)


Trust relationship test. . . . . . : Passed
    Test to ensure DomainSid of domain 'MyDomain' is correct.
    Secure channel for domain 'MyDomain' is to '\\CorpHQ.corp.mydomain.com'.
    Secure channel for domain 'MyDomain' was successfully set to PDC emulator '\\CorpHQ.corp.mydomain.com'.


Kerberos test. . . . . . . . . . . : Passed
    Cached Tickets:
    Server: krbtgt/CORP.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: krbtgt/CORP.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/FM-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/SS-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/TP-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/LV-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/IN-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/RM-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/SB-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/HR-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/WA-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/PH-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/NY-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: LDAP/e93198e9-6398-4f69-9c6a-3993f55fdff6._msdcs.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/DT-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/WM-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/CorpHQ2.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: cifs/CorpHQ.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: ldap/CorpHQ.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: LDAP/16fe800b-a54d-4bc6-9d47-b95543d9cba2._msdcs.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: ldap/PH-DC.corp.mydomain.com/corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02
    Server: host/PH-DC.corp.mydomain.com
        End Time: 5/27/2005 3:16:02
        Renew Time: 6/2/2005 17:16:02


LDAP test. . . . . . . . . . . . . : Passed

    Do un-authenticated LDAP call to 'PH-DC.corp.mydomain.com'.
        Found 1 entries:
        Attr: currentTime
            Val: 17 20050527002922.0Z
        Attr: subschemaSubentry
            Val: 72 CN=Aggregate,CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: dsServiceName
            Val: 107 CN=NTDS Settings,CN=PH-DC,CN=Servers,CN=WestPH,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: namingContexts
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=DomainDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=ForestDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: defaultNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: schemaNamingContext
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: configurationNamingContext
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: rootDomainNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedControl
            Val: 22 1.2.840.113556.1.4.319
            Val: 22 1.2.840.113556.1.4.801
            Val: 22 1.2.840.113556.1.4.473
            Val: 22 1.2.840.113556.1.4.528
            Val: 22 1.2.840.113556.1.4.417
            Val: 22 1.2.840.113556.1.4.619
            Val: 22 1.2.840.113556.1.4.841
            Val: 22 1.2.840.113556.1.4.529
            Val: 22 1.2.840.113556.1.4.805
            Val: 22 1.2.840.113556.1.4.521
            Val: 22 1.2.840.113556.1.4.970
            Val: 23 1.2.840.113556.1.4.1338
            Val: 22 1.2.840.113556.1.4.474
            Val: 23 1.2.840.113556.1.4.1339
            Val: 23 1.2.840.113556.1.4.1340
            Val: 23 1.2.840.113556.1.4.1413
            Val: 23 2.16.840.1.113730.3.4.9
            Val: 24 2.16.840.1.113730.3.4.10
            Val: 23 1.2.840.113556.1.4.1504
            Val: 23 1.2.840.113556.1.4.1852
            Val: 22 1.2.840.113556.1.4.802
        Attr: supportedLDAPVersion
            Val: 1 3
            Val: 1 2
        Attr: supportedLDAPPolicies
            Val: 14 MaxPoolThreads
            Val: 15 MaxDatagramRecv
            Val: 16 MaxReceiveBuffer
            Val: 15 InitRecvTimeout
            Val: 14 MaxConnections
            Val: 15 MaxConnIdleTime
            Val: 11 MaxPageSize
            Val: 16 MaxQueryDuration
            Val: 16 MaxTempTableSize
            Val: 16 MaxResultSetSize
            Val: 22 MaxNotificationPerConn
            Val: 11 MaxValRange
        Attr: highestCommittedUSN
            Val: 6 221613
        Attr: supportedSASLMechanisms
            Val: 6 GSSAPI
            Val: 10 GSS-SPNEGO
            Val: 8 EXTERNAL
            Val: 10 DIGEST-MD5
        Attr: dnsHostName
            Val: 30 PH-DC.corp.mydomain.com
        Attr: ldapServiceName
            Val: 55 corp.mydomain.com:PH-DC$@CORP.mydomain.com
        Attr: serverName
            Val: 90 CN=PH-DC,CN=Servers,CN=WestPH,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedCapabilities
            Val: 22 1.2.840.113556.1.4.800
            Val: 23 1.2.840.113556.1.4.1670
            Val: 23 1.2.840.113556.1.4.1791
        Attr: isSynchronized
            Val: 4 TRUE
        Attr: isGlobalCatalogReady
            Val: 4 TRUE
        Attr: domainFunctionality
            Val: 1 0
        Attr: forestFunctionality
            Val: 1 0
        Attr: domainControllerFunctionality
            Val: 1 2

    Do NTLM authenticated LDAP call to 'PH-DC.corp.mydomain.com'.
        Found 1 entries:
        Attr: currentTime
            Val: 17 20050527002922.0Z
        Attr: subschemaSubentry
            Val: 72 CN=Aggregate,CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: dsServiceName
            Val: 107 CN=NTDS Settings,CN=PH-DC,CN=Servers,CN=WestPH,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: namingContexts
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=DomainDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=ForestDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: defaultNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: schemaNamingContext
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: configurationNamingContext
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: rootDomainNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedControl
            Val: 22 1.2.840.113556.1.4.319
            Val: 22 1.2.840.113556.1.4.801
            Val: 22 1.2.840.113556.1.4.473
            Val: 22 1.2.840.113556.1.4.528
            Val: 22 1.2.840.113556.1.4.417
            Val: 22 1.2.840.113556.1.4.619
            Val: 22 1.2.840.113556.1.4.841
            Val: 22 1.2.840.113556.1.4.529
            Val: 22 1.2.840.113556.1.4.805
            Val: 22 1.2.840.113556.1.4.521
            Val: 22 1.2.840.113556.1.4.970
            Val: 23 1.2.840.113556.1.4.1338
            Val: 22 1.2.840.113556.1.4.474
            Val: 23 1.2.840.113556.1.4.1339
            Val: 23 1.2.840.113556.1.4.1340
            Val: 23 1.2.840.113556.1.4.1413
            Val: 23 2.16.840.1.113730.3.4.9
            Val: 24 2.16.840.1.113730.3.4.10
            Val: 23 1.2.840.113556.1.4.1504
            Val: 23 1.2.840.113556.1.4.1852
            Val: 22 1.2.840.113556.1.4.802
        Attr: supportedLDAPVersion
            Val: 1 3
            Val: 1 2
        Attr: supportedLDAPPolicies
            Val: 14 MaxPoolThreads
            Val: 15 MaxDatagramRecv
            Val: 16 MaxReceiveBuffer
            Val: 15 InitRecvTimeout
            Val: 14 MaxConnections
            Val: 15 MaxConnIdleTime
            Val: 11 MaxPageSize
            Val: 16 MaxQueryDuration
            Val: 16 MaxTempTableSize
            Val: 16 MaxResultSetSize
            Val: 22 MaxNotificationPerConn
            Val: 11 MaxValRange
        Attr: highestCommittedUSN
            Val: 6 221613
        Attr: supportedSASLMechanisms
            Val: 6 GSSAPI
            Val: 10 GSS-SPNEGO
            Val: 8 EXTERNAL
            Val: 10 DIGEST-MD5
        Attr: dnsHostName
            Val: 30 PH-DC.corp.mydomain.com
        Attr: ldapServiceName
            Val: 55 corp.mydomain.com:PH-DC$@CORP.mydomain.com
        Attr: serverName
            Val: 90 CN=PH-DC,CN=Servers,CN=WestPH,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedCapabilities
            Val: 22 1.2.840.113556.1.4.800
            Val: 23 1.2.840.113556.1.4.1670
            Val: 23 1.2.840.113556.1.4.1791
        Attr: isSynchronized
            Val: 4 TRUE
        Attr: isGlobalCatalogReady
            Val: 4 TRUE
        Attr: domainFunctionality
            Val: 1 0
        Attr: forestFunctionality
            Val: 1 0
        Attr: domainControllerFunctionality
            Val: 1 2

    Do Negotiate authenticated LDAP call to 'PH-DC.corp.mydomain.com'.
        Found 1 entries:
        Attr: currentTime
            Val: 17 20050527002922.0Z
        Attr: subschemaSubentry
            Val: 72 CN=Aggregate,CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: dsServiceName
            Val: 107 CN=NTDS Settings,CN=PH-DC,CN=Servers,CN=WestPH,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: namingContexts
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=DomainDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=ForestDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: defaultNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: schemaNamingContext
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: configurationNamingContext
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: rootDomainNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedControl
            Val: 22 1.2.840.113556.1.4.319
            Val: 22 1.2.840.113556.1.4.801
            Val: 22 1.2.840.113556.1.4.473
            Val: 22 1.2.840.113556.1.4.528
            Val: 22 1.2.840.113556.1.4.417
            Val: 22 1.2.840.113556.1.4.619
            Val: 22 1.2.840.113556.1.4.841
            Val: 22 1.2.840.113556.1.4.529
            Val: 22 1.2.840.113556.1.4.805
            Val: 22 1.2.840.113556.1.4.521
            Val: 22 1.2.840.113556.1.4.970
            Val: 23 1.2.840.113556.1.4.1338
            Val: 22 1.2.840.113556.1.4.474
            Val: 23 1.2.840.113556.1.4.1339
            Val: 23 1.2.840.113556.1.4.1340
            Val: 23 1.2.840.113556.1.4.1413
            Val: 23 2.16.840.1.113730.3.4.9
            Val: 24 2.16.840.1.113730.3.4.10
            Val: 23 1.2.840.113556.1.4.1504
            Val: 23 1.2.840.113556.1.4.1852
            Val: 22 1.2.840.113556.1.4.802
        Attr: supportedLDAPVersion
            Val: 1 3
            Val: 1 2
        Attr: supportedLDAPPolicies
            Val: 14 MaxPoolThreads
            Val: 15 MaxDatagramRecv
            Val: 16 MaxReceiveBuffer
            Val: 15 InitRecvTimeout
            Val: 14 MaxConnections
            Val: 15 MaxConnIdleTime
            Val: 11 MaxPageSize
            Val: 16 MaxQueryDuration
            Val: 16 MaxTempTableSize
            Val: 16 MaxResultSetSize
            Val: 22 MaxNotificationPerConn
            Val: 11 MaxValRange
        Attr: highestCommittedUSN
            Val: 6 221613
        Attr: supportedSASLMechanisms
            Val: 6 GSSAPI
            Val: 10 GSS-SPNEGO
            Val: 8 EXTERNAL
            Val: 10 DIGEST-MD5
        Attr: dnsHostName
            Val: 30 PH-DC.corp.mydomain.com
        Attr: ldapServiceName
            Val: 55 corp.mydomain.com:PH-DC$@CORP.mydomain.com
        Attr: serverName
            Val: 90 CN=PH-DC,CN=Servers,CN=WestPH,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedCapabilities
            Val: 22 1.2.840.113556.1.4.800
            Val: 23 1.2.840.113556.1.4.1670
            Val: 23 1.2.840.113556.1.4.1791
        Attr: isSynchronized
            Val: 4 TRUE
        Attr: isGlobalCatalogReady
            Val: 4 TRUE
        Attr: domainFunctionality
            Val: 1 0
        Attr: forestFunctionality
            Val: 1 0
        Attr: domainControllerFunctionality
            Val: 1 2

    Registered Service Principal Names:
        MSSQLSvc/PH-DC.corp.mydomain.com:1124
        ldap/PH-DC.corp.mydomain.com/DomainDnsZones.corp.mydomain.com
        ldap/PH-DC.corp.mydomain.com/ForestDnsZones.corp.mydomain.com
        exchangeAB/PH-DC.corp.mydomain.com
        exchangeAB/PH-DC
        HOST/PH-DC.corp.mydomain.com/MyDomain
        HOST/PH-DC.corp.mydomain.com/corp.mydomain.com
        GC/PH-DC.corp.mydomain.com/corp.mydomain.com
        ldap/ad8f5cae-6dca-40d9-baae-66e569fdf9dc._msdcs.corp.mydomain.com
        ldap/PH-DC.corp.mydomain.com/MyDomain
        ldap/PH-DC
        ldap/PH-DC.corp.mydomain.com
        ldap/PH-DC.corp.mydomain.com/corp.mydomain.com
        DNS/PH-DC.corp.mydomain.com
        NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/PH-DC.corp.mydomain.com
        E3514235-4B06-11D1-AB04-00C04FC2DCD2/ad8f5cae-6dca-40d9-baae-66e569fdf9dc/corp.mydomain.com
        HOST/PH-DC.corp.mydomain.com
        HOST/PH-DC
    Since 'CorpHQ.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'CorpHQ.corp.mydomain.com'.
    Since 'CorpHQ2.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'CorpHQ2.corp.mydomain.com'.
    Since 'WM-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'WM-DC.corp.mydomain.com'.
    Since 'DT-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'DT-DC.corp.mydomain.com'.
    Since 'NY-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'NY-DC.corp.mydomain.com'.
    Since 'PH-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'PH-DC.corp.mydomain.com'.

    Do un-authenticated LDAP call to 'WA-DC.corp.mydomain.com'.
        Found 1 entries:
        Attr: currentTime
            Val: 17 20050527003237.0Z
        Attr: subschemaSubentry
            Val: 72 CN=Aggregate,CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: dsServiceName
            Val: 111 CN=NTDS Settings,CN=WA-DC,CN=Servers,CN=East-WA,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: namingContexts
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=DomainDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=ForestDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: defaultNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: schemaNamingContext
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: configurationNamingContext
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: rootDomainNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedControl
            Val: 22 1.2.840.113556.1.4.319
            Val: 22 1.2.840.113556.1.4.801
            Val: 22 1.2.840.113556.1.4.473
            Val: 22 1.2.840.113556.1.4.528
            Val: 22 1.2.840.113556.1.4.417
            Val: 22 1.2.840.113556.1.4.619
            Val: 22 1.2.840.113556.1.4.841
            Val: 22 1.2.840.113556.1.4.529
            Val: 22 1.2.840.113556.1.4.805
            Val: 22 1.2.840.113556.1.4.521
            Val: 22 1.2.840.113556.1.4.970
            Val: 23 1.2.840.113556.1.4.1338
            Val: 22 1.2.840.113556.1.4.474
            Val: 23 1.2.840.113556.1.4.1339
            Val: 23 1.2.840.113556.1.4.1340
            Val: 23 1.2.840.113556.1.4.1413
            Val: 23 2.16.840.1.113730.3.4.9
            Val: 24 2.16.840.1.113730.3.4.10
            Val: 23 1.2.840.113556.1.4.1504
            Val: 23 1.2.840.113556.1.4.1852
            Val: 22 1.2.840.113556.1.4.802
        Attr: supportedLDAPVersion
            Val: 1 3
            Val: 1 2
        Attr: supportedLDAPPolicies
            Val: 14 MaxPoolThreads
            Val: 15 MaxDatagramRecv
            Val: 16 MaxReceiveBuffer
            Val: 15 InitRecvTimeout
            Val: 14 MaxConnections
            Val: 15 MaxConnIdleTime
            Val: 11 MaxPageSize
            Val: 16 MaxQueryDuration
            Val: 16 MaxTempTableSize
            Val: 16 MaxResultSetSize
            Val: 22 MaxNotificationPerConn
            Val: 11 MaxValRange
        Attr: highestCommittedUSN
            Val: 7 2722120
        Attr: supportedSASLMechanisms
            Val: 6 GSSAPI
            Val: 10 GSS-SPNEGO
            Val: 8 EXTERNAL
            Val: 10 DIGEST-MD5
        Attr: dnsHostName
            Val: 31 WA-DC.corp.mydomain.com
        Attr: ldapServiceName
            Val: 56 corp.mydomain.com:WA-DC$@CORP.mydomain.com
        Attr: serverName
            Val: 94 CN=WA-DC,CN=Servers,CN=East-WA,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedCapabilities
            Val: 22 1.2.840.113556.1.4.800
            Val: 23 1.2.840.113556.1.4.1670
            Val: 23 1.2.840.113556.1.4.1791
        Attr: isSynchronized
            Val: 4 TRUE
        Attr: isGlobalCatalogReady
            Val: 4 TRUE
        Attr: domainFunctionality
            Val: 1 0
        Attr: forestFunctionality
            Val: 1 0
        Attr: domainControllerFunctionality
            Val: 1 2

    Do NTLM authenticated LDAP call to 'WA-DC.corp.mydomain.com'.
        Found 1 entries:
        Attr: currentTime
            Val: 17 20050527003238.0Z
        Attr: subschemaSubentry
            Val: 72 CN=Aggregate,CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: dsServiceName
            Val: 111 CN=NTDS Settings,CN=WA-DC,CN=Servers,CN=East-WA,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: namingContexts
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=DomainDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=ForestDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: defaultNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: schemaNamingContext
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: configurationNamingContext
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: rootDomainNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedControl
            Val: 22 1.2.840.113556.1.4.319
            Val: 22 1.2.840.113556.1.4.801
            Val: 22 1.2.840.113556.1.4.473
            Val: 22 1.2.840.113556.1.4.528
            Val: 22 1.2.840.113556.1.4.417
            Val: 22 1.2.840.113556.1.4.619
            Val: 22 1.2.840.113556.1.4.841
            Val: 22 1.2.840.113556.1.4.529
            Val: 22 1.2.840.113556.1.4.805
            Val: 22 1.2.840.113556.1.4.521
            Val: 22 1.2.840.113556.1.4.970
            Val: 23 1.2.840.113556.1.4.1338
            Val: 22 1.2.840.113556.1.4.474
            Val: 23 1.2.840.113556.1.4.1339
            Val: 23 1.2.840.113556.1.4.1340
            Val: 23 1.2.840.113556.1.4.1413
            Val: 23 2.16.840.1.113730.3.4.9
            Val: 24 2.16.840.1.113730.3.4.10
            Val: 23 1.2.840.113556.1.4.1504
            Val: 23 1.2.840.113556.1.4.1852
            Val: 22 1.2.840.113556.1.4.802
        Attr: supportedLDAPVersion
            Val: 1 3
            Val: 1 2
        Attr: supportedLDAPPolicies
            Val: 14 MaxPoolThreads
            Val: 15 MaxDatagramRecv
            Val: 16 MaxReceiveBuffer
            Val: 15 InitRecvTimeout
            Val: 14 MaxConnections
            Val: 15 MaxConnIdleTime
            Val: 11 MaxPageSize
            Val: 16 MaxQueryDuration
            Val: 16 MaxTempTableSize
            Val: 16 MaxResultSetSize
            Val: 22 MaxNotificationPerConn
            Val: 11 MaxValRange
        Attr: highestCommittedUSN
            Val: 7 2722120
        Attr: supportedSASLMechanisms
            Val: 6 GSSAPI
            Val: 10 GSS-SPNEGO
            Val: 8 EXTERNAL
            Val: 10 DIGEST-MD5
        Attr: dnsHostName
            Val: 31 WA-DC.corp.mydomain.com
        Attr: ldapServiceName
            Val: 56 corp.mydomain.com:WA-DC$@CORP.mydomain.com
        Attr: serverName
            Val: 94 CN=WA-DC,CN=Servers,CN=East-WA,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedCapabilities
            Val: 22 1.2.840.113556.1.4.800
            Val: 23 1.2.840.113556.1.4.1670
            Val: 23 1.2.840.113556.1.4.1791
        Attr: isSynchronized
            Val: 4 TRUE
        Attr: isGlobalCatalogReady
            Val: 4 TRUE
        Attr: domainFunctionality
            Val: 1 0
        Attr: forestFunctionality
            Val: 1 0
        Attr: domainControllerFunctionality
            Val: 1 2

    Do Negotiate authenticated LDAP call to 'WA-DC.corp.mydomain.com'.
        Found 1 entries:
        Attr: currentTime
            Val: 17 20050527003239.0Z
        Attr: subschemaSubentry
            Val: 72 CN=Aggregate,CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: dsServiceName
            Val: 111 CN=NTDS Settings,CN=WA-DC,CN=Servers,CN=East-WA,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: namingContexts
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=DomainDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
            Val: 50 DC=ForestDnsZones,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: defaultNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: schemaNamingContext
            Val: 59 CN=Schema,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: configurationNamingContext
            Val: 49 CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: rootDomainNamingContext
            Val: 32 DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedControl
            Val: 22 1.2.840.113556.1.4.319
            Val: 22 1.2.840.113556.1.4.801
            Val: 22 1.2.840.113556.1.4.473
            Val: 22 1.2.840.113556.1.4.528
            Val: 22 1.2.840.113556.1.4.417
            Val: 22 1.2.840.113556.1.4.619
            Val: 22 1.2.840.113556.1.4.841
            Val: 22 1.2.840.113556.1.4.529
            Val: 22 1.2.840.113556.1.4.805
            Val: 22 1.2.840.113556.1.4.521
            Val: 22 1.2.840.113556.1.4.970
            Val: 23 1.2.840.113556.1.4.1338
            Val: 22 1.2.840.113556.1.4.474
            Val: 23 1.2.840.113556.1.4.1339
            Val: 23 1.2.840.113556.1.4.1340
            Val: 23 1.2.840.113556.1.4.1413
            Val: 23 2.16.840.1.113730.3.4.9
            Val: 24 2.16.840.1.113730.3.4.10
            Val: 23 1.2.840.113556.1.4.1504
            Val: 23 1.2.840.113556.1.4.1852
            Val: 22 1.2.840.113556.1.4.802
        Attr: supportedLDAPVersion
            Val: 1 3
            Val: 1 2
        Attr: supportedLDAPPolicies
            Val: 14 MaxPoolThreads
            Val: 15 MaxDatagramRecv
            Val: 16 MaxReceiveBuffer
            Val: 15 InitRecvTimeout
            Val: 14 MaxConnections
            Val: 15 MaxConnIdleTime
            Val: 11 MaxPageSize
            Val: 16 MaxQueryDuration
            Val: 16 MaxTempTableSize
            Val: 16 MaxResultSetSize
            Val: 22 MaxNotificationPerConn
            Val: 11 MaxValRange
        Attr: highestCommittedUSN
            Val: 7 2722120
        Attr: supportedSASLMechanisms
            Val: 6 GSSAPI
            Val: 10 GSS-SPNEGO
            Val: 8 EXTERNAL
            Val: 10 DIGEST-MD5
        Attr: dnsHostName
            Val: 31 WA-DC.corp.mydomain.com
        Attr: ldapServiceName
            Val: 56 corp.mydomain.com:WA-DC$@CORP.mydomain.com
        Attr: serverName
            Val: 94 CN=WA-DC,CN=Servers,CN=East-WA,CN=Sites,CN=Configuration,DC=corp,DC=MyDomain-hansen,DC=com
        Attr: supportedCapabilities
            Val: 22 1.2.840.113556.1.4.800
            Val: 23 1.2.840.113556.1.4.1670
            Val: 23 1.2.840.113556.1.4.1791
        Attr: isSynchronized
            Val: 4 TRUE
        Attr: isGlobalCatalogReady
            Val: 4 TRUE
        Attr: domainFunctionality
            Val: 1 0
        Attr: forestFunctionality
            Val: 1 0
        Attr: domainControllerFunctionality
            Val: 1 2

    Registered Service Principal Names:
        DNS/PH-DC.corp.mydomain.com
        NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/PH-DC.corp.mydomain.com
        exchangeAB/PH-DC
        exchangeAB/PH-DC.corp.mydomain.com
        ldap/PH-DC.corp.mydomain.com/ForestDnsZones.corp.mydomain.com
        ldap/PH-DC.corp.mydomain.com/DomainDnsZones.corp.mydomain.com
        ldap/ad8f5cae-6dca-40d9-baae-66e569fdf9dc._msdcs.corp.mydomain.com
        GC/PH-DC.corp.mydomain.com/corp.mydomain.com
        HOST/PH-DC.corp.mydomain.com/corp.mydomain.com
        HOST/PH-DC.corp.mydomain.com/MyDomain
        ldap/PH-DC.corp.mydomain.com/corp.mydomain.com
        ldap/PH-DC.corp.mydomain.com
        ldap/PH-DC
        ldap/PH-DC.corp.mydomain.com/MyDomain
        E3514235-4B06-11D1-AB04-00C04FC2DCD2/ad8f5cae-6dca-40d9-baae-66e569fdf9dc/corp.mydomain.com
        MSSQLSvc/PH-DC.corp.mydomain.com:1124
        HOST/PH-DC.corp.mydomain.com
        HOST/PH-DC
    Since 'HR-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'HR-DC.corp.mydomain.com'.
    Since 'SB-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'SB-DC.corp.mydomain.com'.
    Since 'RM-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'RM-DC.corp.mydomain.com'.
    Since 'IN-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'IN-DC.corp.mydomain.com'.
    Since 'LV-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'LV-DC.corp.mydomain.com'.
    Cannot test LDAP to 'MyDomain_FS' since it isn't running the DS. [Test skipped.]
    Since 'TP-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'TP-DC.corp.mydomain.com'.
    Since 'SS-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'SS-DC.corp.mydomain.com'.
    Since 'FM-DC.corp.mydomain.com' is down, it cannot be tested.
    [WARNING] Failed to query SPN registration on DC 'FM-DC.corp.mydomain.com'.


Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination        Netmask           Gateway         Interface  Metric
         0.0.0.0           0.0.0.0      192.168.14.1     192.168.14.10      20
       127.0.0.0         255.0.0.0         127.0.0.1         127.0.0.1       1
   192.168.13.10   255.255.255.255      192.168.14.1     192.168.14.10      20
    192.168.14.0     255.255.255.0     192.168.14.10     192.168.14.10      20
   192.168.14.10   255.255.255.255         127.0.0.1         127.0.0.1      20
  192.168.14.255   255.255.255.255     192.168.14.10     192.168.14.10      20
   192.168.30.12   255.255.255.255      192.168.14.1     192.168.14.10      20
       224.0.0.0         240.0.0.0     192.168.14.10     192.168.14.10      20
 255.255.255.255   255.255.255.255     192.168.14.10     192.168.14.10       1
No persistent route entries.


Netstat information test . . . . . : Passed


    Interface Statistics

                                    Received             Sent
    Unicast Packets               2254441460       1324460830
    Non-unicast packets               119980            10220
    Discards                               0                0
    Errors                                 0                0
    Unknown protocols                 365021           458284

    Interface index         =  1
    Description             =  MS TCP Loopback interface
    Type                    =  24
    MTU                     =  1520
    Speed                   =  10000000
    Physical Address        =  00-00-00-00-00-00
    Administrative Status   =  1
    Operational Status      =  1
    Last Changed            =  482829702
    Output Queue Length     =  0


    Interface index         =  65539
    Description             =  Intel(R) PRO/100 Network Connection
    Type                    =  6
    MTU                     =  1500
    Speed                   =  100000000
    Physical Address        =  00-06-5B-39-71-D7
    Administrative Status   =  1
    Operational Status      =  1
    Last Changed            =  482829706
    Output Queue Length     =  0



    Active Connections

  Proto Local Address         Foreign Address                           State
    TCP   PH-DC:nameserver     PH-DC.corp.mydomain.com:39035      LISTENING
    TCP   PH-DC:domain         PH-DC.corp.mydomain.com:59479      LISTENING
    TCP   PH-DC:kerberos       PH-DC.corp.mydomain.com:2160       LISTENING
    TCP   PH-DC:epmap          PH-DC.corp.mydomain.com:32890      LISTENING
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:45302      LISTENING
    TCP   PH-DC:microsoft-ds   PH-DC.corp.mydomain.com:2160       LISTENING
    TCP   PH-DC:kpasswd        PH-DC.corp.mydomain.com:26714      LISTENING
    TCP   PH-DC:593            PH-DC.corp.mydomain.com:2083       LISTENING
    TCP   PH-DC:ldaps          PH-DC.corp.mydomain.com:49349      LISTENING
    TCP   PH-DC:1025           PH-DC.corp.mydomain.com:6198       LISTENING
    TCP   PH-DC:1026           PH-DC.corp.mydomain.com:6375       LISTENING
    TCP   PH-DC:1031           PH-DC.corp.mydomain.com:30871      LISTENING
    TCP   PH-DC:1073           PH-DC.corp.mydomain.com:32940      LISTENING
    TCP   PH-DC:1088           PH-DC.corp.mydomain.com:43214      LISTENING
    TCP   PH-DC:1124           PH-DC.corp.mydomain.com:26802      LISTENING
    TCP   PH-DC:1126           PH-DC.corp.mydomain.com:57548      LISTENING
    TCP   PH-DC:1147           PH-DC.corp.mydomain.com:10421      LISTENING
    TCP   PH-DC:2080           PH-DC.corp.mydomain.com:6332       LISTENING
    TCP   PH-DC:3268           PH-DC.corp.mydomain.com:53440      LISTENING
    TCP   PH-DC:3269           PH-DC.corp.mydomain.com:59478      LISTENING
    TCP   PH-DC:3389           PH-DC.corp.mydomain.com:43086      LISTENING
    TCP   PH-DC:5800           PH-DC.corp.mydomain.com:8276       LISTENING
    TCP   PH-DC:5900           PH-DC.corp.mydomain.com:26855      LISTENING
    TCP   PH-DC:6101           PH-DC.corp.mydomain.com:26795      LISTENING
    TCP   PH-DC:6106           PH-DC.corp.mydomain.com:2067       LISTENING
    TCP   PH-DC:10000          PH-DC.corp.mydomain.com:63722      LISTENING
    TCP   PH-DC:27000          PH-DC.corp.mydomain.com:57546      LISTENING
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:1051       ESTABLISHED
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:1052       ESTABLISHED
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:1053       ESTABLISHED
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:2623       ESTABLISHED
    TCP   PH-DC:1051           PH-DC.corp.mydomain.com:ldap       ESTABLISHED
    TCP   PH-DC:1052           PH-DC.corp.mydomain.com:ldap       ESTABLISHED
    TCP   PH-DC:1053           PH-DC.corp.mydomain.com:ldap       ESTABLISHED
    TCP   PH-DC:2623           PH-DC.corp.mydomain.com:ldap       ESTABLISHED
    TCP   PH-DC:nameserver     CorpHQ:3266                              ESTABLISHED
    TCP   PH-DC:epmap          PH-DC.corp.mydomain.com:4514       ESTABLISHED
    TCP   PH-DC:epmap          CorpHQ:2908                              ESTABLISHED
    TCP   PH-DC:epmap          CorpHQ:2956                              ESTABLISHED
    TCP   PH-DC:epmap          CorpHQ:2961                              ESTABLISHED
    TCP   PH-DC:netbios-ssn    PH-DC.corp.mydomain.com:12434      LISTENING
    TCP   PH-DC:netbios-ssn    PHNX-51C:4157                             ESTABLISHED
    TCP   PH-DC:netbios-ssn    PHNX-102C:3137                            ESTABLISHED
    TCP   PH-DC:netbios-ssn    PHNX-52C:1828                             ESTABLISHED
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:2637       ESTABLISHED
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4339       ESTABLISHED
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4443       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4511       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4512       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4513       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4517       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4518       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4519       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4520       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4521       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4522       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4523       TIME_WAIT
    TCP   PH-DC:ldap           PH-DC.corp.mydomain.com:4524       TIME_WAIT
    TCP   PH-DC:ldap           CorpHQ2:8689                              ESTABLISHED
    TCP   PH-DC:ldap           CorpHQ2:8701                              ESTABLISHED
    TCP   PH-DC:ldap           GH-OWA1:48381                             ESTABLISHED
    TCP   PH-DC:ldap           GH-OWA1:48412                             ESTABLISHED
    TCP   PH-DC:ldap           GH-OWA1:48424                             ESTABLISHED
    TCP   PH-DC:microsoft-ds   PHNX-38C:1147                             ESTABLISHED
    TCP   PH-DC:microsoft-ds   PHNX-29C:2791                             ESTABLISHED
    TCP   PH-DC:microsoft-ds   PHNX-101C:1040                            ESTABLISHED
    TCP   PH-DC:1025           PH-DC.corp.mydomain.com:1080       ESTABLISHED
    TCP   PH-DC:1025           PH-DC.corp.mydomain.com:4515       ESTABLISHED
    TCP   PH-DC:1025           PH-DC.corp.mydomain.com:4516       ESTABLISHED
    TCP   PH-DC:1025           192.168.14.120:1530                       ESTABLISHED
    TCP   PH-DC:1025           CorpHQ:2910                              ESTABLISHED
    TCP   PH-DC:1072           TP-DC:ldap                               CLOSE_WAIT
    TCP   PH-DC:1073           CorpHQ:2962                              ESTABLISHED
    TCP   PH-DC:1080           PH-DC.corp.mydomain.com:1025       ESTABLISHED
    TCP   PH-DC:2637           PH-DC.corp.mydomain.com:ldap       ESTABLISHED
    TCP   PH-DC:3389           RIMINI:2859                               ESTABLISHED
    TCP   PH-DC:4029           CorpHQ:nameserver                        ESTABLISHED
    TCP   PH-DC:4187           PH-DC.corp.mydomain.com:ldap       CLOSE_WAIT
    TCP   PH-DC:4339           PH-DC.corp.mydomain.com:ldap       ESTABLISHED
    TCP   PH-DC:4347           CorpHQ:epmap                             TIME_WAIT
    TCP   PH-DC:4348           IN-DC:epmap                              TIME_WAIT
    TCP   PH-DC:4428           WA-DC:ldap                              ESTABLISHED
    TCP   PH-DC:4507           IN-DC:ldap                               FIN_WAIT_1
    TCP   PH-DC:4508           CorpHQ:1025                              ESTABLISHED
    TCP   PH-DC:4509           LV-DC:ldap                                 FIN_WAIT_1
    TCP   PH-DC:4510           TP-DC:ldap                               FIN_WAIT_1
    TCP   PH-DC:4514           PH-DC.corp.mydomain.com:epmap      ESTABLISHED
    TCP   PH-DC:4515           PH-DC.corp.mydomain.com:1025       ESTABLISHED
    TCP   PH-DC:4516           PH-DC.corp.mydomain.com:1025       ESTABLISHED
    TCP   PH-DC:4525           SS-DC:ldap                              FIN_WAIT_1
    TCP   PH-DC:4526           FM-DC:ldap                               FIN_WAIT_1
    UDP  PH-DC:nameserver     *:*                                    
    UDP  PH-DC:microsoft-ds   *:*                                    
    UDP  PH-DC:isakmp         *:*                                    
    UDP  PH-DC:1029           *:*                                    
    UDP  PH-DC:1032           *:*                                    
    UDP  PH-DC:1050           *:*                                    
    UDP  PH-DC:1056           *:*                                    
    UDP  PH-DC:1063           *:*                                    
    UDP  PH-DC:1071           *:*                                    
    UDP  PH-DC:1074           *:*                                    
    UDP  PH-DC:1112           *:*                                    
    UDP  PH-DC:1120           *:*                                    
    UDP  PH-DC:1133           *:*                                    
    UDP  PH-DC:1156           *:*                                    
    UDP  PH-DC:1191           *:*                                    
    UDP  PH-DC:1214           *:*                                    
    UDP  PH-DC:1219           *:*                                    
    UDP  PH-DC:ms-sql-m       *:*                                    
    UDP  PH-DC:2148           *:*                                    
    UDP  PH-DC:3383           *:*                                    
    UDP  PH-DC:3739           *:*                                    
    UDP  PH-DC:4094           *:*                                    
    UDP  PH-DC:4336           *:*                                    
    UDP  PH-DC:4500           *:*                                    
    UDP  PH-DC:domain         *:*                                    
    UDP  PH-DC:ntp            *:*                                    
    UDP  PH-DC:1055           *:*                                    
    UDP  PH-DC:1086           *:*                                    
    UDP  PH-DC:domain         *:*                                    
    UDP  PH-DC:bootps         *:*                                    
    UDP  PH-DC:bootpc         *:*                                    
    UDP  PH-DC:kerberos       *:*                                    
    UDP  PH-DC:ntp            *:*                                    
    UDP  PH-DC:netbios-ns     *:*                                    
    UDP  PH-DC:netbios-dgm    *:*                                    
    UDP  PH-DC:389            *:*                                    
    UDP  PH-DC:kpasswd        *:*                                    
    UDP  PH-DC:2535           *:*                                    


    IP  Statistics

    Packets Received              =   203,491,498
    Received Header Errors        =   0
    Received Address Errors       =   297
    Datagrams Forwarded           =   0
    Unknown Protocols Received    =   0
    Received Packets Discarded    =   0
    Received Packets Delivered    =   203,491,429
    Output Requests               =   105,073,014
    Routing Discards              =   0
    Discarded Output Packets      =   0
    Output Packet No Route        =   0
    Reassembly  Required          =   137
    Reassembly Successful         =   68
    Reassembly Failures           =   1
    Datagrams successfully fragmented  =   70
    Datagrams failing fragmentation    =   2,548
    Fragments Created                  =   140
    Forwarding                        =    2
    Default TTL                       =    128
    Reassembly  timeout               =    60


    TCP Statistics

    Active Opens               =    57,611
    Passive Opens              =    88,987
    Failed Connection Attempts =    614
    Reset Connections          =    4,901
    Current Connections        =    45
    Received Segments          =    203,267,034
    Segment Sent               =    104,859,981
    Segment Retransmitted      =    24,278
    Retransmission Timeout Algorithm  =   vanj
    Minimum Retransmission Timeout  = 300
    Maximum Retransmission Timeout  = 120,000
    Maximum Number of Connections   = -1


    UDP Statistics

    Datagrams Received    =   137,995
    No Ports              =   37,372
    Receive Errors        =   0
    Datagrams Sent        =   110,970


    ICMP Statistics

                              Received           Sent
    Messages                    85,994         85,994
    Errors                           0              0
    Destination  Unreachable     8,310          8,310
    Time    Exceeded                 0              0
    Parameter Problems               0              0
    Source Quenchs                   0              0
    Redirects                        0              0
    Echos                       49,029         49,029
    Echo Replies                28,655         28,655
    Timestamps                       0              0
    Timestamp Replies                0              0
    Address Masks                    0              0
    Address Mask Replies             0              0


Bindings test. . . . . . . . . . . : Passed
    Component Name : Network Monitor Driver
    Bind Name: NM
    Binding Paths:
        Owner of the binding path : Network Monitor Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Network Monitor Driver
            Lower Component: Intel(R) PRO/100 Network Connection

        Owner of the binding path : Network Monitor Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanbh
            Upper Component: Network Monitor Driver
            Lower Component: WAN Miniport (Network Monitor)


    Component Name : NDIS Usermode I/O Protocol
    Bind Name: Ndisuio
    Binding Paths:
        Owner of the binding path : NDIS Usermode I/O Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: NDIS Usermode I/O Protocol
            Lower Component: Intel(R) PRO/100 Network Connection


    Component Name : Point to Point Protocol Over Ethernet
    Bind Name: RasPppoe
    Binding Paths:
        Owner of the binding path : Point to Point Protocol Over Ethernet
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Point to Point Protocol Over Ethernet
            Lower Component: Intel(R) PRO/100 Network Connection


    Component Name : Point to Point Tunneling Protocol
    Bind Name: mspptp
    Binding Paths:

    Component Name : Layer 2 Tunneling Protocol
    Bind Name: msl2tp
    Binding Paths:

    Component Name : Remote Access NDIS WAN Driver
    Bind Name: NdisWan
    Binding Paths:
        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiscowan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: Direct Parallel

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (PPPOE)

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (PPTP)

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiscowan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (L2TP)

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanasync
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: RAS Async Adapter


    Component Name : Message-oriented TCP/IP Protocol (SMB session)
    Bind Name: NetbiosSmb
    Binding Paths:

    Component Name : WINS Client(TCP/IP) Protocol
    Bind Name: NetBT
    Binding Paths:
        Owner of the binding path : WINS Client(TCP/IP) Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/100 Network Connection

        Owner of the binding path : WINS Client(TCP/IP) Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : Internet Protocol (TCP/IP)
    Bind Name: Tcpip
    Binding Paths:
        Owner of the binding path : Internet Protocol (TCP/IP)
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/100 Network Connection

        Owner of the binding path : Internet Protocol (TCP/IP)
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : Client for Microsoft Networks
    Bind Name: LanmanWorkstation
    Binding Paths:
        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios_smb
            Upper Component: Client for Microsoft Networks
            Lower Component: Message-oriented TCP/IP Protocol (SMB session)

        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: Client for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/100 Network Connection

        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: Client for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : WebClient
    Bind Name: WebClient
    Binding Paths:

    Component Name : DHCP Server
    Bind Name: DHCPServer
    Binding Paths:

    Component Name : Wireless Configuration
    Bind Name: wzcsvc
    Binding Paths:

    Component Name : Network Load Balancing
    Bind Name: Wlbs
    Binding Paths:
        Owner of the binding path : Network Load Balancing
        Binding Enabled: No
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Network Load Balancing
            Lower Component: Intel(R) PRO/100 Network Connection


    Component Name : Steelhead
    Bind Name: RemoteAccess
    Binding Paths:

    Component Name : Dial-Up Server
    Bind Name: msrassrv
    Binding Paths:

    Component Name : Remote Access Connection Manager
    Bind Name: RasMan
    Binding Paths:

    Component Name : Dial-Up Client
    Bind Name: msrascli
    Binding Paths:

    Component Name : File and Printer Sharing for Microsoft Networks
    Bind Name: LanmanServer
    Binding Paths:
        Owner of the binding path : File and Printer Sharing for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios_smb
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: Message-oriented TCP/IP Protocol (SMB session)

        Owner of the binding path : File and Printer Sharing for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/100 Network Connection

        Owner of the binding path : File and Printer Sharing for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : NetBIOS Interface
    Bind Name: NetBIOS
    Binding Paths:
        Owner of the binding path : NetBIOS Interface
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: NetBIOS Interface
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/100 Network Connection

        Owner of the binding path : NetBIOS Interface
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: NetBIOS Interface
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : Generic Packet Classifier
    Bind Name: Gpc
    Binding Paths:

    Component Name : Application Layer Gateway
    Bind Name: ALG
    Binding Paths:

    Component Name : WAN Miniport (Network Monitor)
    Bind Name: NdisWanBh
    Binding Paths:

    Component Name : WAN Miniport (IP)
    Bind Name: NdisWanIp
    Binding Paths:

    Component Name : Direct Parallel
    Bind Name: {3331F6AC-9028-45DA-AF76-47B978EECEDB}
    Binding Paths:

    Component Name : WAN Miniport (PPPOE)
    Bind Name: {1C705A3F-F68A-4FE0-9638-1893FC1F3D99}
    Binding Paths:

    Component Name : WAN Miniport (PPTP)
    Bind Name: {C0D020FE-9BC4-426F-939E-F6C4B98994E1}
    Binding Paths:

    Component Name : WAN Miniport (L2TP)
    Bind Name: {EE9D7BA6-BD74-4F2E-822B-F6F6ECCE05D1}
    Binding Paths:

    Component Name : RAS Async Adapter
    Bind Name: {969C8185-984B-4430-9957-C4825D762957}
    Binding Paths:

    Component Name : Intel(R) PRO/100 Network Connection
    Bind Name: {E94604BC-7D39-4F2F-96BD-2D0ADC66BC40}
    Binding Paths:



WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
0
 
joedoe58Commented:
If the problem comes back I would try a metadata cleanup. See this link: http://www.petri.co.il/fix_unsuccessful_demotion.htm
0
 
thefumblerAuthor Commented:
Looking at the link, this removes a server from AD.  Did you realize that it was an old NT4 server that didn't have AD that I removed or are you suggesting to remove another server completely?

I actually haven't tried simply using DCPROMO in demoting, replicating and then promoting yet.  That would probably be a solution to completely clean house, but a lot of work for all these DC's.  
0
 
joedoe58Commented:
I was just thinking that you might have another server added that was AD and then removed wihtout you knowing about it. Why I say that is since to me it seems that there are something that is bothering the replication and if it is not a firewall or routing problem then many times it is a problem with the metadata. To do a dcpromo would not solve such a problem but only by forecully remove any entries that is existing but not valid
0
 
thefumblerAuthor Commented:
Sorry I didn't realize you meant the ntdsutil when you mentioned 'metadata cleanup'.  I poked around with the metadata cleanup in ntdsutil by listing domains, sites and then servers in each site but didn't see anything that didn't belong.  Anything specific I should be looking for?  
0
 
thefumblerAuthor Commented:
I opened a case with Microsoft.  It appears the cause is recent Security Update 893066 that changed the MTU size of packets.  

http://support.microsoft.com/default.aspx?scid=kb;en-us;898060
Installing security update MS05-019 or Windows Server 2003 Service Pack 1 may cause network connectivity between clients and servers to fail

Network connectivity between clients and servers may fail. This failure occurs after the installation of either security update MS05-019 or Microsoft Windows Server 2003 Service Pack 1 (SP1). Any one or more of the following symptoms may occur: • Inability to connect to terminal servers or to file share access.
• Failure of domain controller replication across WAN links.
• Inability of Microsoft Exchange servers to connect to domain controllers.
0
 
thefumblerAuthor Commented:
The hotfix was the issue.  But many thanks for sticking with it Joe.
0
 
joedoe58Commented:
Glad you got it fixed, sorry you had to pay Microsoft though :-)
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 11
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now