Re: Forced client disconnect problem.

From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxx>
Date: Tue, 6 Dec 2005 11:19:41 -0600

>From what I can tell the dcdiag output looks pretty good. I don't think that
latency test is showing any fatal type error and after all it did pass the
test. --- Steve

"Gerry Armstrong" <gerrya@xxxxxxxxxxx> wrote in message
news:11pavvkh93rthe5@xxxxxxxxxxxxxxxxxxxxx
>I am getting the following results from the 2003 Standard server when I run
>the dcdiag /v, not sure if the Latency check results should be the way they
>are, any advice?
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> * Verifying that the local machine towner-s2, is a DC.
> * Connecting to directory service on server towner-s2.
> * Collecting site info.
> * Identifying all servers.
> * Identifying all NC cross-refs.
> * Found 2 DC(s). Testing 1 of them.
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\TOWNER-S2
> Starting test: Connectivity
> * Active Directory LDAP Services Check
> * Active Directory RPC Services Check
> ......................... TOWNER-S2 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\TOWNER-S2
> Starting test: Replications
> * Replications Check
> * Replication Latency Check
> CN=Schema,CN=Configuration,DC=towner,DC=local
> 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=Configuration,DC=towner,DC=local
> 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).
> DC=towner,DC=local
> 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 Site Latency Check
> ......................... TOWNER-S2 passed test Replications
> Test omitted by user request: Topology
> Test omitted by user request: CutoffServers
> Starting test: NCSecDesc
> * Security Permissions Check for
> CN=Schema,CN=Configuration,DC=towner,DC=local
> (Schema,Version 2)
> * Security Permissions Check for
> CN=Configuration,DC=towner,DC=local
> (Configuration,Version 2)
> * Security Permissions Check for
> DC=towner,DC=local
> (Domain,Version 2)
> ......................... TOWNER-S2 passed test NCSecDesc
> Starting test: NetLogons
> * Network Logons Privileges Check
> ......................... TOWNER-S2 passed test NetLogons
> Starting test: Advertising
> The DC TOWNER-S2 is advertising itself as a DC and having a DS.
> The DC TOWNER-S2 is advertising as an LDAP server
> The DC TOWNER-S2 is advertising as having a writeable directory
> The DC TOWNER-S2 is advertising as a Key Distribution Center
> The DC TOWNER-S2 is advertising as a time server
> ......................... TOWNER-S2 passed test Advertising
> Starting test: KnowsOfRoleHolders
> Role Schema Owner = CN=NTDS
> Settings,CN=TOWNER-S1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=towner,DC=local
> Role Domain Owner = CN=NTDS
> Settings,CN=TOWNER-S1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=towner,DC=local
> Role PDC Owner = CN=NTDS
> Settings,CN=TOWNER-S1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=towner,DC=local
> Role Rid Owner = CN=NTDS
> Settings,CN=TOWNER-S1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=towner,DC=local
> Role Infrastructure Update Owner = CN=NTDS
> Settings,CN=TOWNER-S1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=towner,DC=local
> ......................... TOWNER-S2 passed test KnowsOfRoleHolders
> Starting test: RidManager
> * Available RID Pool for the Domain is 2609 to 1073741823
> * towner-s1.towner.local is the RID Master
> * DsBind with RID Master was successful
> * rIDAllocationPool is 2109 to 2608
> * rIDPreviousAllocationPool is 2109 to 2608
> * rIDNextRID: 2110
> ......................... TOWNER-S2 passed test RidManager
> Starting test: MachineAccount
> * SPN found :LDAP/towner-s2.towner.local/towner.local
> * SPN found :LDAP/towner-s2.towner.local
> * SPN found :LDAP/TOWNER-S2
> * SPN found :LDAP/towner-s2.towner.local/TOWNER
> * SPN found
> :LDAP/74842282-8658-41f9-a574-6597860d3a3c._msdcs.towner.local
> * SPN found
> :E3514235-4B06-11D1-AB04-00C04FC2DCD2/74842282-8658-41f9-a574-6597860d3a3c/towner.local
> * SPN found :HOST/towner-s2.towner.local/towner.local
> * SPN found :HOST/towner-s2.towner.local
> * SPN found :HOST/TOWNER-S2
> * SPN found :HOST/towner-s2.towner.local/TOWNER
> * SPN found :GC/towner-s2.towner.local/towner.local
> ......................... TOWNER-S2 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
> ......................... TOWNER-S2 passed test Services
> Test omitted by user request: OutboundSecureChannels
> Starting test: ObjectsReplicated
> TOWNER-S2 is in domain DC=towner,DC=local
> Checking for CN=TOWNER-S2,OU=Domain Controllers,DC=towner,DC=local
> in domain DC=towner,DC=local on 1 servers
> Object is up-to-date on all servers.
> Checking for CN=NTDS
> Settings,CN=TOWNER-S2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=towner,DC=local
> in domain CN=Configuration,DC=towner,DC=local on 1 servers
> Object is up-to-date on all servers.
> ......................... TOWNER-S2 passed test ObjectsReplicated
> Starting test: frssysvol
> * The File Replication Service SYSVOL ready test
> File Replication Service's SYSVOL is ready
> ......................... TOWNER-S2 passed test frssysvol
> Starting test: frsevent
> * The File Replication Service Event log test
> ......................... TOWNER-S2 passed test frsevent
> Starting test: kccevent
> * The KCC Event log test
> Found no KCC errors in Directory Service Event log in the last 15
> minutes.
> ......................... TOWNER-S2 passed test kccevent
> Starting test: systemlog
> * The System Event log test
> Found no errors in System Event log in the last 60 minutes.
> ......................... TOWNER-S2 passed test systemlog
> Test omitted by user request: VerifyReplicas
> Starting test: VerifyReferences
> The system object reference (serverReference)
>
> CN=TOWNER-S2,OU=Domain Controllers,DC=towner,DC=local and backlink
> on
>
>
> CN=TOWNER-S2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=towner,DC=local
>
> are correct.
> The system object reference (frsComputerReferenceBL)
>
> CN=TOWNER-S2,CN=Domain System Volume (SYSVOL share),CN=File
> Replication Service,CN=System,DC=towner,DC=local
>
> and backlink on CN=TOWNER-S2,OU=Domain
> Controllers,DC=towner,DC=local
>
> are correct.
> The system object reference (serverReferenceBL)
>
> CN=TOWNER-S2,CN=Domain System Volume (SYSVOL share),CN=File
> Replication Service,CN=System,DC=towner,DC=local
>
> and backlink on
>
> CN=NTDS
> Settings,CN=TOWNER-S2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=towner,DC=local
>
> are correct.
> ......................... TOWNER-S2 passed test VerifyReferences
> Test omitted by user request: VerifyEnterpriseReferences
>
> 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 : towner
> Starting test: CrossRefValidation
> ......................... towner passed test CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... towner passed test CheckSDRefDom
>
> Running enterprise tests on : towner.local
> Starting test: Intersite
> Skipping site Default-First-Site-Name, this site is outside the
> scope
>
> provided by the command line arguments provided.
> ......................... towner.local passed test Intersite
> Starting test: FsmoCheck
> GC Name: \\towner-s1.towner.local
> Locator Flags: 0xe00003fd
> PDC Name: \\towner-s1.towner.local
> Locator Flags: 0xe00003fd
> Time Server Name: \\towner-s2.towner.local
> Locator Flags: 0xe00001f8
> Preferred Time Server Name: \\towner-s1.towner.local
> Locator Flags: 0xe00003fd
> KDC Name: \\towner-s2.towner.local
> Locator Flags: 0xe00001f8
> ......................... towner.local passed test FsmoCheck
>
>

.

References:
- Forced client disconnect problem.
  - From: Gerry Armstrong
- Re: Forced client disconnect problem.
  - From: Steven L Umbach
- Re: Forced client disconnect problem.
  - From: Gerry Armstrong

Prev by Date: Re: Forced client disconnect problem.
Next by Date: Re: Forced client disconnect problem.
Previous by thread: Re: Forced client disconnect problem.
Next by thread: Re: Forced client disconnect problem.
Index(es):
- Date
- Thread

Relevant Pages

Re: dcdiag information
... >> Test omitted by user request: ... >> Starting test: CrossRefValidation ... >> Starting test: CheckSDRefDom ...
(microsoft.public.windows.server.active_directory)
dcdiag information
... Verify that the network path is ... Test omitted by user request: ... Starting test: CrossRefValidation ...
(microsoft.public.windows.server.active_directory)
Re: Forced client disconnect problem.
... * Connecting to directory service on server towner-s1. ... replicas and are not verifiably latent, or dc's no longer replicating this ... Test omitted by user request: ... Starting test: CrossRefValidation ...
(microsoft.public.windows.server.security)
Re: Forced client disconnect problem.
... * Identifying all servers. ... replicas and are not verifiably latent, or dc's no longer replicating this ... had no latency information. ... Test omitted by user request: ...
(microsoft.public.windows.server.security)
Re: Forced client disconnect problem.
... > * Connecting to directory service on server towner-s1. ... > replicas and are not verifiably latent, or dc's no longer replicating this ... > Test omitted by user request: ... > Starting test: CrossRefValidation ...
(microsoft.public.windows.server.security)