Re: Replication problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Fri, 01 Feb 2008 04:08:01 -0800, LynnA wrote:

Hi,
We have two DC's - W2k server and W2k3 Standard Server. All was working
well until the 2k server crashed with a hardware problem. Since then the
2k server cannot browse 2k3 shares ( Logon Failure: The target account
name is incorrect. ), but can browse client XP shares. Net View
\\2k3server gives System error 5 has occured - Access Denied. This is
not a show stopper as I have changed any script using \\computername to
\\ipaddress which works. I have tried KB288167 on the 2k server with no
success. DCDiag shows replication problems from the 2k3 to 2k server. I
can email DCDIAG and NETDIAG files. How can I fix this?

w2k server

Domain Controller Diagnosis

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

Doing initial required tests

Testing server: Default-First-Site-Name\DELLSERVER
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DELLSERVER passed test Connectivity

Testing server: Default-First-Site-Name\MILLENNIUM-100
Starting test: Connectivity
* Active Directory LDAP Services Check
[MILLENNIUM-100] LDAP bind failed with error 31,
Win32 Error 31.
......................... MILLENNIUM-100 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DELLSERVER
Starting test: Replications
* Replications Check
[Replications Check,DELLSERVER] A recent replication attempt
failed:
From MILLENNIUM-100 to DELLSERVER
Naming Context: CN=Schema,CN=Configuration,DC=millennium
The replication generated an error (1908):
Win32 Error 1908
The failure occurred at 2008-02-01 08:45.08.
The last success occurred at 2007-12-12 08:45.40.
1246 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
[Replications Check,DELLSERVER] A recent replication attempt
failed:
From MILLENNIUM-100 to DELLSERVER
Naming Context: CN=Configuration,DC=millennium
The replication generated an error (1908):
Win32 Error 1908
The failure occurred at 2008-02-01 08:45.08.
The last success occurred at 2007-12-12 09:13.59.
2026 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
[Replications Check,DELLSERVER] A recent replication attempt
failed:
From MILLENNIUM-100 to DELLSERVER
Naming Context: DC=millennium
The replication generated an error (1908):
Win32 Error 1908
The failure occurred at 2008-02-01 08:45.08.
The last success occurred at 2007-12-12 09:34.02.
8216 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
......................... DELLSERVER 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=millennium
* Security Permissions Check for
CN=Configuration,DC=millennium
* Security Permissions Check for
DC=millennium
......................... DELLSERVER passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... DELLSERVER passed test NetLogons
Starting test: Advertising
The DC DELLSERVER is advertising itself as a DC and having a DS.
The DC DELLSERVER is advertising as an LDAP server
The DC DELLSERVER is advertising as having a writeable directory
The DC DELLSERVER is advertising as a Key Distribution Center
Warning: DELLSERVER is not advertising as a time server.
The DS DELLSERVER is advertising as a GC.
......................... DELLSERVER failed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=DELLSERVER,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=millennium
Role Domain Owner = CN=NTDS
Settings,CN=MILLENNIUM-100,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=millennium
[MILLENNIUM-100] DsBind() failed with error -2146893022,
Win32 Error -2146893022.
Warning: MILLENNIUM-100 is the Domain Owner, but is not
responding to DS RPC Bind.
Warning: MILLENNIUM-100 is the Domain Owner, but is not
responding to LDAP Bind.
Role PDC Owner = CN=NTDS
Settings,CN=MILLENNIUM-100,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=millennium
Warning: MILLENNIUM-100 is the PDC Owner, but is not responding
to DS RPC Bind.
Warning: MILLENNIUM-100 is the PDC Owner, but is not responding
to LDAP Bind.
Role Rid Owner = CN=NTDS
Settings,CN=MILLENNIUM-100,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=millennium
Warning: MILLENNIUM-100 is the Rid Owner, but is not responding
to DS RPC Bind.
Warning: MILLENNIUM-100 is the Rid Owner, but is not responding
to LDAP Bind.
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=MILLENNIUM-100,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=millennium
Warning: MILLENNIUM-100 is the Infrastructure Update Owner, but
is not responding to DS RPC Bind.
Warning: MILLENNIUM-100 is the Infrastructure Update Owner, but
is not responding to LDAP Bind.
......................... DELLSERVER failed test
KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 2600 to 1073741823
* millennium-100.millennium is the RID Master
[DELLSERVER] DsBindWithCred() failed with error -2146893022.
Win32 Error -2146893022
......................... DELLSERVER failed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/DELLSERVER.millennium/millennium
* SPN found :LDAP/DELLSERVER.millennium
* SPN found :LDAP/DELLSERVER
* SPN found :LDAP/DELLSERVER.millennium/MILLENNIUM
* SPN found :LDAP/cea65b61-4c2b-42fa-b178-
af798b621154._msdcs.millennium
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/
cea65b61-4c2b-42fa-b178-af798b621154/millennium
* SPN found :HOST/DELLSERVER.millennium/millennium
* SPN found :HOST/DELLSERVER.millennium
* SPN found :HOST/DELLSERVER
* SPN found :HOST/DELLSERVER.millennium/MILLENNIUM
* SPN found :GC/DELLSERVER.millennium/millennium
......................... DELLSERVER 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: RPCLOCATOR
* Checking Service: w32time
w32time Service is stopped on [DELLSERVER]
* Checking Service: TrkWks
* Checking Service: TrkSvr
* Checking Service: NETLOGON
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... DELLSERVER failed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
DELLSERVER is in domain DC=millennium
Checking for CN=DELLSERVER,OU=Domain Controllers,DC=millennium
in domain DC=millennium on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=DELLSERVER,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=millennium in domain
CN=Configuration,DC=millennium on 1 servers
Object is up-to-date on all servers.
......................... DELLSERVER passed test
ObjectsReplicated
Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 01/31/2008 19:47:51
Event String: The File Replication Service is having trouble

enabling replication from MILLENNIUM-100 to

DELLSERVER for c:\winnt\sysvol\domain using the

DNS name MILLENNIUM-100.millennium. FRS will keep

retrying.

Following are some of the reasons you would see

this warning.



[1] FRS can not correctly resolve the DNS name

MILLENNIUM-100.millennium from this computer.

[2] FRS is not running on

MILLENNIUM-100.millennium.

[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.
......................... DELLSERVER passed test frssysvol
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last
15 minutes.
......................... DELLSERVER passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... DELLSERVER passed test systemlog

Testing server: Default-First-Site-Name\MILLENNIUM-100
Skipping all tests, because server MILLENNIUM-100 is
not responding to directory service requests
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Test omitted by user request: OutboundSecureChannels

Running enterprise tests on : millennium
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the
scope

provided by the command line arguments provided.
......................... millennium passed test Intersite
Starting test: FsmoCheck
GC Name: \\DELLSERVER.millennium
Locator Flags: 0xe00001bc
PDC Name: \\millennium-100.millennium
Locator Flags: 0xe00003f9
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error 1355
A Good Time Server could not be located.
KDC Name: \\DELLSERVER.millennium
Locator Flags: 0xe00001bc
......................... millennium failed test FsmoCheck
.

Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Replication failure
    ... Connecting to directory service on server arnelfs1. ... ARNELDC1 is the Schema Owner, but is not responding to DS ... prevented from starting by the File Replication Service. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication problems
    ... We have two DC's - W2k server and W2k3 Standard Server. ... DCDiag shows replication problems from the 2k3 to 2k server. ... From MILLENNIUM-100 to DELLSERVER ... Test omitted by user request: ...
    (microsoft.public.windows.server.active_directory)