Re: server 2003 [error_netname_deleted]
- From: "Carl O" <carlo@xxxxxxxxxxxxxx>
- Date: Fri, 22 Jul 2005 23:10:36 GMT
Hey! I have the exact same problem! are you using cisco routers inbetween
your sites?
i get the following event ID errors all together every 15 minutes exactly:
1865
1311
1566
I did the MTU change and it doesnt work. If you have control of your
routers, can you try adding crypto ipsec df-bit clear to the config as
suggested here ( http://x220.minasi.com/forum/topic.asp?TOPIC_ID=9047 )?
I have no control over that equipment, but it looks to be the same issue.
Additionally, running openVPN ( http://sourceforge.net/projects/openvpn/ )
on both of the DC's clears the error out completely. I would love to know if
this solution works as then i can force the cisco admins to at least TRY it,
which they are unwilling to do now because, as they say, "ipsec is not
turned on in the routers" so its supposed to not make a difference.
anyways please keep the thread posted!
"rodge" <rodge@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9B33BE45-BD24-466A-93BC-E1009E473D47@xxxxxxxxxxxxxxxx
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> * Verifying that the local machine maindc, is a DC.
> * Connecting to directory service on server maindc.
> * Collecting site info.
> * Identifying all servers.
> * Identifying all NC cross-refs.
> * Found 29 DC(s). Testing 1 of them.
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Main\MAINDC
> Starting test: Connectivity
> * Active Directory LDAP Services Check
> * Active Directory RPC Services Check
> ......................... MAINDC passed test Connectivity
>
> Doing primary tests
>
> Testing server: Main\MAINDC
> Starting test: Replications
> * Replications Check
> [Replications Check,MAINDC] No replication recently attempted:
> From FRIENDSVILLE to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:59 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From FROSTBURG to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:59 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From SMITHSBURG to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:00 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From GRANTSVILLE to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:00 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From LAKE to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:00 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From WHITEOAKS to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:00 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From BALLENGER to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:00 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From KEYSER to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:00 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From RIVERSIDE to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:00 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From MYERSVILLE to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:01 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From HAGERSTOWN to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:01 (about 7 hours
> ago).
> [Replications Check,MAINDC] A recent replication attempt failed:
> From MIDTOWNS to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The replication generated an error (8524):
> The DSA operation is unable to proceed because of a DNS lookup
> failure.
> The failure occurred at 2005-07-19 13:57:02.
> The last success occurred at 2005-07-19 13:45:46.
> 1 failures have occurred since the last success.
> The guid-based DNS name
> bf665d72-1ab1-4a42-9edc-9ce72aa5bf7f._msdcs.func.com
> is not registered on one or more DNS servers.
> [Replications Check,MAINDC] A recent replication attempt failed:
> From TSDC to MAINDC
> Naming Context: CN=Schema,CN=Configuration,DC=func,DC=com
> The replication generated an error (8524):
> The DSA operation is unable to proceed because of a DNS lookup
> failure.
> The failure occurred at 2005-07-19 13:57:32.
> The last success occurred at 2005-07-19 13:45:46.
> 1 failures have occurred since the last success.
> The guid-based DNS name
> c13a6a27-fabc-410f-8670-53a74409580a._msdcs.func.com
> is not registered on one or more DNS servers.
> [Replications Check,MAINDC] No replication recently attempted:
> From FRIENDSVILLE to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:47 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From FROSTBURG to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:47 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From SMITHSBURG to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:48 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From GRANTSVILLE to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:49 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From LAKE to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:49 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From WHITEOAKS to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:50 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From BALLENGER to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:57 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From KEYSER to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:58 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From RIVERSIDE to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:58 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From MYERSVILLE to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:59 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From HAGERSTOWN to MAINDC
> Naming Context: CN=Configuration,DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:59 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From FRIENDSVILLE to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:45:47 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From FROSTBURG to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:01 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From SMITHSBURG to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:01 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From GRANTSVILLE to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:01 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From LAKE to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:01 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From WHITEOAKS to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:02 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From BALLENGER to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:02 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From KEYSER to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:02 (about 7 hours
> ago).
> [Replications Check,MAINDC] A recent replication attempt failed:
> From RIVERSIDE to MAINDC
> Naming Context: DC=func,DC=com
> The replication generated an error (1726):
> The remote procedure call failed.
> The failure occurred at 2005-07-19 06:46:02.
> The last success occurred at 2005-07-17 11:58:06.
> 10 failures have occurred since the last success.
> The replication RPC call executed for too long at the server
> and
> was cancelled.
> Check load and resouce usage on RIVERSIDE.
> [Replications Check,MAINDC] No replication recently attempted:
> From MYERSVILLE to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:03 (about 7 hours
> ago).
> [Replications Check,MAINDC] No replication recently attempted:
> From HAGERSTOWN to MAINDC
> Naming Context: DC=func,DC=com
> The last attempt occurred at 2005-07-19 06:46:03 (about 7 hours
> ago).
> * Replication Latency Check
> CN=Schema,CN=Configuration,DC=func,DC=com
> Latency information for 22 entries in the vector were
> ignored.
> 20 were retired Invocations. 0 were either: read-only
> replicas and are not verifiably latent, or dc's no longer replicating this
> nc. 2 had no latency information (Win2K DC).
> CN=Configuration,DC=func,DC=com
> Latency information for 22 entries in the vector were
> ignored.
> 20 were retired Invocations. 0 were either: read-only
> replicas and are not verifiably latent, or dc's no longer replicating this
> nc. 2 had no latency information (Win2K DC).
> REPLICATION-RECEIVED LATENCY WARNING
> MAINDC: Current time is 2005-07-19 14:18:05.
> DC=func,DC=com
> Last replication recieved from RIVERSIDE at 2005-07-17
> 11:58:06.
> Latency information for 20 entries in the vector were
> ignored.
> 18 were retired Invocations. 0 were either: read-only
> replicas and are not verifiably latent, or dc's no longer replicating this
> nc. 2 had no latency information (Win2K DC).
> * Replication Site Latency Check
> ......................... MAINDC 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=func,DC=com
> (Schema,Version 2)
> * Security Permissions Check for
> CN=Configuration,DC=func,DC=com
> (Configuration,Version 2)
> * Security Permissions Check for
> DC=func,DC=com
> (Domain,Version 2)
> ......................... MAINDC passed test NCSecDesc
> Starting test: NetLogons
> * Network Logons Privileges Check
> ......................... MAINDC passed test NetLogons
> Starting test: Advertising
> The DC MAINDC is advertising itself as a DC and having a DS.
> The DC MAINDC is advertising as an LDAP server
> The DC MAINDC is advertising as having a writeable directory
> The DC MAINDC is advertising as a Key Distribution Center
> The DC MAINDC is advertising as a time server
> ......................... MAINDC passed test Advertising
> Starting test: KnowsOfRoleHolders
> Role Schema Owner = CN=NTDS
> Settings,CN=TSDC,CN=Servers,CN=Main,CN=Sites,CN=Configuration,DC=func,DC=com
> Role Domain Owner = CN=NTDS
> Settings,CN=TSDC,CN=Servers,CN=Main,CN=Sites,CN=Configuration,DC=func,DC=com
> Role PDC Owner = CN=NTDS
> Settings,CN=TSDC,CN=Servers,CN=Main,CN=Sites,CN=Configuration,DC=func,DC=com
> Role Rid Owner = CN=NTDS
> Settings,CN=TSDC,CN=Servers,CN=Main,CN=Sites,CN=Configuration,DC=func,DC=com
> Role Infrastructure Update Owner = CN=NTDS
> Settings,CN=MAINDC,CN=Servers,CN=Main,CN=Sites,CN=Configuration,DC=func,DC=com
> ......................... MAINDC passed test KnowsOfRoleHolders
> Starting test: RidManager
> * Available RID Pool for the Domain is 29105 to 1073741823
> * tsdc.func.com is the RID Master
> * DsBind with RID Master was successful
> * rIDAllocationPool is 25105 to 25604
> * rIDPreviousAllocationPool is 25105 to 25604
> * rIDNextRID: 25185
> ......................... MAINDC passed test RidManager
> Starting test: MachineAccount
> * SPN found :LDAP/maindc.func.com/func.com
> * SPN found :LDAP/maindc.func.com
> * SPN found :LDAP/MAINDC
> * SPN found :LDAP/maindc.func.com/FUNC
> * SPN found
> :LDAP/71ebfa96-7bff-454e-bdf5-b934cef3dc0d._msdcs.func.com
> * SPN found
> :E3514235-4B06-11D1-AB04-00C04FC2DCD2/71ebfa96-7bff-454e-bdf5-b934cef3dc0d/func.com
> * SPN found :HOST/maindc.func.com/func.com
> * SPN found :HOST/maindc.func.com
> * SPN found :HOST/MAINDC
> * SPN found :HOST/maindc.func.com/FUNC
> * SPN found :GC/maindc.func.com/func.com
> ......................... MAINDC 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
> ......................... MAINDC passed test Services
> Test omitted by user request: OutboundSecureChannels
> Starting test: ObjectsReplicated
> MAINDC is in domain DC=func,DC=com
> Checking for CN=MAINDC,OU=Domain Controllers,DC=func,DC=com in
> domain DC=func,DC=com on 1 servers
> Object is up-to-date on all servers.
> Checking for CN=NTDS
> Settings,CN=MAINDC,CN=Servers,CN=Main,CN=Sites,CN=Configuration,DC=func,DC=com
> in domain CN=Configuration,DC=func,DC=com on 1 servers
> Object is up-to-date on all servers.
> ......................... MAINDC passed test ObjectsReplicated
> Starting test: frssysvol
> * The File Replication Service SYSVOL ready test
> File Replication Service's SYSVOL is ready
> ......................... MAINDC passed test frssysvol
> Starting test: frsevent
> * The File Replication Service Event log test
> ......................... MAINDC passed test frsevent
> Starting test: kccevent
> * The KCC Event log test
> An Warning Event occured. EventID: 0x8000061E
> Time Generated: 07/19/2005 14:15:38
> Event String: All domain controllers in the following site that
>
> can replicate the directory partition over this
>
> transport are currently unavailable.
>
>
>
> Site:
>
> CN=Riverside,CN=Sites,CN=Configuration,DC=func,DC=com
>
>
>
> Directory partition:
>
> DC=func,DC=com
>
> Transport:
>
> CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=func,DC=com
>
>
> An Error Event occured. EventID: 0xC000051F
> Time Generated: 07/19/2005 14:15:38
> Event String: The Knowledge Consistency Checker (KCC) has
>
> detected problems with the following directory
>
> partition.
>
>
>
> Directory partition:
>
> DC=func,DC=com
>
>
>
> There is insufficient site connectivity
>
> information in Active Directory Sites and
>
> Services for the KCC to create a spanning tree
>
> replication topology. Or, one or more domain
>
> controllers with this directory partition are
>
> unable to replicate the directory partition
>
> information. This is probably due to inaccessible
>
> domain controllers.
>
>
>
> User Action
>
> Use Active Directory Sites and Services to
>
> perform one of the following actions:
>
> - Publish sufficient site connectivity
>
> information so that the KCC can determine a route
>
> by which this directory partition can reach this
>
> site. This is the preferred option.
>
> - Add a Connection object to a domain controller
>
> that contains the directory partition in this
>
> site from a domain controller that contains the
>
> same directory partition in another site.
>
>
>
> If neither of the Active Directory Sites and
>
> Services tasks correct this condition, see
>
> previous events logged by the KCC that identify
>
> the inaccessible domain controllers.
> An Warning Event occured. EventID: 0x80000749
> Time Generated: 07/19/2005 14:15:38
> Event String: The Knowledge Consistency Checker (KCC) was
>
> unable to form a complete spanning tree network
>
> topology. As a result, the following list of
>
> sites cannot be reached from the local site.
>
>
>
> Sites:
>
> CN=Riverside,CN=Sites,CN=Configuration,DC=func,DC=com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> An Warning Event occured. EventID: 0x8000061E
> Time Generated: 07/19/2005 14:15:38
> Event String: All domain controllers in the following site that
>
> can replicate the directory partition over this
>
> transport are currently unavailable.
>
>
>
> Site:
>
> CN=Riverside,CN=Sites,CN=Configuration,DC=func,DC=com
>
>
>
> Directory partition:
>
> CN=Configuration,DC=func,DC=com
>
> Transport:
>
> CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=func,DC=com
>
>
> An Error Event occured. EventID: 0xC000051F
> Time Generated: 07/19/2005 14:15:38
> Event String: The Knowledge Consistency Checker (KCC) has
>
> detected problems with the following directory
>
> partition.
>
>
>
> Directory partition:
>
> CN=Configuration,DC=func,DC=com
>
>
>
> There is insufficient site connectivity
>
> information in Active Directory Sites and
>
> Services for the KCC to create a spanning tree
>
> replication topology. Or, one or more domain
>
> controllers with this directory partition are
>
> unable to replicate the directory partition
>
> information. This is probably due to inaccessible
>
> domain controllers.
>
>
>
> User Action
>
> Use Active Directory Sites and Services to
>
> perform one of the following actions:
>
> - Publish sufficient site connectivity
>
> information so that the KCC can determine a route
>
> by which this directory partition can reach this
>
> site. This is the preferred option.
>
> - Add a Connection object to a domain controller
>
> that contains the directory partition in this
>
> site from a domain controller that contains the
>
> same directory partition in another site.
>
>
>
> If neither of the Active Directory Sites and
>
> Services tasks correct this condition, see
>
> previous events logged by the KCC that identify
>
> the inaccessible domain controllers.
> An Warning Event occured. EventID: 0x80000749
> Time Generated: 07/19/2005 14:15:38
> Event String: The Knowledge Consistency Checker (KCC) was
>
> unable to form a complete spanning tree network
>
> topology. As a result, the following list of
>
> sites cannot be reached from the local site.
>
>
>
> Sites:
>
> CN=Riverside,CN=Sites,CN=Configuration,DC=func,DC=com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ......................... MAINDC failed test kccevent
> Starting test: systemlog
> * The System Event log test
> An Error Event occured. EventID: 0xC25A001D
> Time Generated: 07/19/2005 13:56:06
> Event String: The time provider NtpClient is configured to
>
> acquire time from one or more time sources,
>
> however none of the sources are currently
>
> accessible. No attempt to contact a source will
>
> be made for 15 minutes. NtpClient has no source
>
> of accurate time.
> ......................... MAINDC failed test systemlog
> Test omitted by user request: VerifyReplicas
> Starting test: VerifyReferences
> The system object reference (serverReference)
>
> CN=MAINDC,OU=Domain Controllers,DC=func,DC=com and backlink on
>
>
> CN=MAINDC,CN=Servers,CN=Main,CN=Sites,CN=Configuration,DC=func,DC=com
>
> are correct.
> The system object reference (frsComputerReferenceBL)
>
> CN=MAINDC,CN=Domain System Volume (SYSVOL share),CN=File
> Replication Service,CN=System,DC=func,DC=com
>
> and backlink on CN=MAINDC,OU=Domain Controllers,DC=func,DC=com are
>
> correct.
> The system object reference (serverReferenceBL)
>
> CN=MAINDC,CN=Domain System Volume (SYSVOL share),CN=File
> Replication Service,CN=System,DC=func,DC=com
>
> and backlink on
>
> CN=NTDS
> Settings,CN=MAINDC,CN=Servers,CN=Main,CN=Sites,CN=Configuration,DC=func,DC=com
>
> are correct.
> ......................... MAINDC 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 : func
> Starting test: CrossRefValidation
> ......................... func passed test CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... func passed test CheckSDRefDom
>
> Running enterprise tests on : func.com
> Starting test: Intersite
> Skipping site Grantsville, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Riverside, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Friendsville, this site is outside the scope
> provided
> by
>
> the command line arguments provided.
> Skipping site Frostburg, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Myersville, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Hagerstown, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Smithsburg, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Whiteoaks, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Lake, this site is outside the scope provided by the
>
> command line arguments provided.
> Skipping site Belair, this site is outside the scope provided by
> the
>
> command line arguments provided.
> Skipping site Moorefield, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site EdwinMiller, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Keyser, this site is outside the scope provided by
> the
>
> command line arguments provided.
> Skipping site Tritowns, this site is outside the scope provided by
> the
>
> command line arguments provided.
> Skipping site Centercity, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Barton, this site is outside the scope provided by
> the
>
> command line arguments provided.
> Skipping site SBerkeley, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site SFoxcroft, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Ballenger, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Martinsburg, this site is outside the scope provided
> by
>
> the command line arguments provided.
> Skipping site Potomac, this site is outside the scope provided by
> the
>
> command line arguments provided.
> Skipping site Sabraton, this site is outside the scope provided by
> the
>
> command line arguments provided.
> Skipping site Main, this site is outside the scope provided by the
>
> command line arguments provided.
> Skipping site Littman, this site is outside the scope provided by
> the
>
> command line arguments provided.
> Skipping site MBurgOakFirst, this site is outside the scope
> provided
>
> by the command line arguments provided.
> ......................... func.com passed test Intersite
> Starting test: FsmoCheck
> GC Name: \\midtowns.func.com
> Locator Flags: 0xe00001fc
> PDC Name: \\tsdc.func.com
> Locator Flags: 0xe00001fd
> Time Server Name: \\maindc.func.com
> Locator Flags: 0xe00001f8
> Preferred Time Server Name: \\maindc.func.com
> Locator Flags: 0xe00001f8
> KDC Name: \\maindc.func.com
> Locator Flags: 0xe00001f8
> ......................... func.com passed test FsmoCheck
>
>
> "Paul Williams [MVP]" wrote:
>
>> Start here:
>> www.eventid.net
>>
>> Can you also post the whole event log?
>>
>> --
>> Paul Williams
>> Microsoft MVP - Windows Server - Directory Services
>> http://www.msresource.net | http://forums.msresource.net
>>
>>
>>
.
- Follow-Ups:
- Re: server 2003 [error_netname_deleted]
- From: rodge
- Re: server 2003 [error_netname_deleted]
- References:
- server 2003 [error_netname_deleted]
- From: rodge
- Re: server 2003 [error_netname_deleted]
- From: Paul Williams [MVP]
- Re: server 2003 [error_netname_deleted]
- From: rodge
- Re: server 2003 [error_netname_deleted]
- From: Paul Williams [MVP]
- Re: server 2003 [error_netname_deleted]
- From: rodge
- Re: server 2003 [error_netname_deleted]
- From: Paul Williams [MVP]
- Re: server 2003 [error_netname_deleted]
- From: rodge
- server 2003 [error_netname_deleted]
- Prev by Date: RE: Demoting DC
- Next by Date: Reset user passwords permission
- Previous by thread: Re: server 2003 [error_netname_deleted]
- Next by thread: Re: server 2003 [error_netname_deleted]
- Index(es):
Relevant Pages
|
