Re: KRB_APP_ERR_MODIFIED

Hi Meinolf!

Thank you for your answer.

Yes it is event id 4, system, source kerberos. see below:

-----------
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server
host/ho2.ins.lan. The target name used was
LDAP/92BD3F78-2E3C-44A1-9F55-0DF888AB65B6._msdcs.INS.LAN. This indicates that
the password used to encrypt the kerberos service ticket is different than
that on the target server. Commonly, this is due to identically named
machine accounts in the target realm (INS.LAN), and the client realm.
Please contact your system administrator.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
----------------

all DC's are global catalogs, dns is AD integrated.

i have attached a dcdiag log file.

Thank you

Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for
CN=Schema,CN=Configuration,DC=INS,DC=LAN.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Schema,CN=Configuration,DC=INS,DC=LAN.
These servers can't get changes from home server HO2:
Default-First-Site-Name/HO1
Default-First-Site-Name/HO
* Analyzing the connection topology for
CN=Configuration,DC=INS,DC=LAN.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
Downstream topology is disconnected for
CN=Configuration,DC=INS,DC=LAN.
These servers can't get changes from home server HO2:
Default-First-Site-Name/HO1
Default-First-Site-Name/HO
* Analyzing the connection topology for DC=INS,DC=LAN.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
Downstream topology is disconnected for DC=INS,DC=LAN.
These servers can't get changes from home server HO2:
Default-First-Site-Name/HO1
Default-First-Site-Name/HO
......................... HO2 failed test Topology
Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for
CN=Schema,CN=Configuration,DC=INS,DC=LAN.
* Performing upstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context specified
for this replication operation is invalid..
* Performing downstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context specified
for this replication operation is invalid..
* Analyzing the alive system replication topology for
CN=Configuration,DC=INS,DC=LAN.
* Performing upstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context specified
for this replication operation is invalid..
* Performing downstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context specified
for this replication operation is invalid..
* Analyzing the alive system replication topology for DC=INS,DC=LAN.
* Performing upstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context specified
for this replication operation is invalid..
* Performing downstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context specified
for this replication operation is invalid..
......................... HO2 passed test CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC HO2.
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=INS,DC=LAN
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=INS,DC=LAN
(Configuration,Version 2)
* Security Permissions Check for
DC=INS,DC=LAN
(Domain,Version 2)
......................... HO2 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Unable to connect to the NETLOGON share! (\\HO2\netlogon)
[HO2] An net use or LsaPolicy operation failed with error 1203, No
network provider accepted the given network path..
......................... HO2 failed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\ho.INS.LAN, when we
were trying to reach HO2.
Server is not responding or is not considered suitable.
The DC HO2 is advertising itself as a DC and having a DS.
The DC HO2 is advertising as an LDAP server
The DC HO2 is advertising as having a writeable directory
The DC HO2 is advertising as a Key Distribution Center
The DC HO2 is advertising as a time server
......................... HO2 failed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=HO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN
Role Domain Owner = CN=NTDS
Settings,CN=HO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN
Role PDC Owner = CN=NTDS
Settings,CN=HO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN
Role Rid Owner = CN=NTDS
Settings,CN=HO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=HO1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN
......................... HO2 passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 6272 to 1073741823
* HO1.INS.LAN is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 5772 to 6271
* rIDPreviousAllocationPool is 5772 to 6271
* rIDNextRID: 5772
......................... HO2 passed test RidManager
Starting test: MachineAccount
Checking machine account for DC HO2 on DC HO2.
* SPN found :LDAP/HO2.INS.LAN/INS.LAN
* SPN found :LDAP/HO2.INS.LAN
* SPN found :LDAP/HO2
* SPN found :LDAP/HO2.INS.LAN/INS
* SPN found :LDAP/92bd3f78-2e3c-44a1-9f55-0df888ab65b6._msdcs.INS.LAN
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/92bd3f78-2e3c-44a1-9f55-0df888ab65b6/INS.LAN
* SPN found :HOST/HO2.INS.LAN/INS.LAN
* SPN found :HOST/HO2.INS.LAN
* SPN found :HOST/HO2
* SPN found :HOST/HO2.INS.LAN/INS
* SPN found :GC/HO2.INS.LAN/INS.LAN
......................... HO2 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
......................... HO2 passed test Services
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
......................... HO2 passed test OutboundSecureChannels
Starting test: ObjectsReplicated
HO2 is in domain DC=INS,DC=LAN
Checking for CN=HO2,OU=Domain Controllers,DC=INS,DC=LAN in domain
DC=INS,DC=LAN on 3 servers
Authoritative attribute name on HO1 (writeable)
usnLocalChange = 127899
LastOriginatingDsa = HO
usnOriginatingChange = 3386613
timeLastOriginatingChange = 2008-06-26 08:37:38
VersionLastOriginatingChange = 4
Out-of-date attribute name on HO2 (writeable)
usnLocalChange = 11835
LastOriginatingDsa = HO1
usnOriginatingChange = 123671
timeLastOriginatingChange = 2008-06-25 10:26:55
VersionLastOriginatingChange = 2
Authoritative attribute nTSecurityDescriptor on HO2 (writeable)
usnLocalChange = 28674
LastOriginatingDsa = HO2
usnOriginatingChange = 28674
timeLastOriginatingChange = 2008-06-25 10:32:14
VersionLastOriginatingChange = 2
Out-of-date attribute nTSecurityDescriptor on HO1 (writeable)
usnLocalChange = 123546
LastOriginatingDsa = HO1
usnOriginatingChange = 123546
timeLastOriginatingChange = 2008-06-25 10:01:46
VersionLastOriginatingChange = 1
Out-of-date attribute nTSecurityDescriptor on HO (writeable)
usnLocalChange = 3378729
LastOriginatingDsa = HO1
usnOriginatingChange = 123546
timeLastOriginatingChange = 2008-06-25 10:01:46
VersionLastOriginatingChange = 1
Authoritative attribute servicePrincipalName on HO2 (writeable)
usnLocalChange = 36881
LastOriginatingDsa = HO2
usnOriginatingChange = 36881
timeLastOriginatingChange = 2008-06-25 12:51:52
VersionLastOriginatingChange = 3
Out-of-date attribute servicePrincipalName on HO (writeable)
usnLocalChange = 3378991
LastOriginatingDsa = HO1
usnOriginatingChange = 123666
timeLastOriginatingChange = 2008-06-25 10:26:41
VersionLastOriginatingChange = 1
Out-of-date attribute servicePrincipalName on HO1 (writeable)
usnLocalChange = 123666
LastOriginatingDsa = HO1
usnOriginatingChange = 123666
timeLastOriginatingChange = 2008-06-25 10:26:41
VersionLastOriginatingChange = 1
Checking for CN=NTDS
Settings,CN=HO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN in domain CN=Configuration,DC=INS,DC=LAN on 3 servers
Authoritative attribute msDS-hasMasterNCs on HO2 (writeable)
usnLocalChange = 26547
LastOriginatingDsa = HO2
usnOriginatingChange = 26547
timeLastOriginatingChange = 2008-06-25 10:28:36
VersionLastOriginatingChange = 5
Out-of-date attribute msDS-hasMasterNCs on HO (writeable)
usnLocalChange = 3379000
LastOriginatingDsa = HO1
usnOriginatingChange = 123665
timeLastOriginatingChange = 2008-06-25 10:26:41
VersionLastOriginatingChange = 1
Out-of-date attribute msDS-hasMasterNCs on HO1 (writeable)
usnLocalChange = 123665
LastOriginatingDsa = HO1
usnOriginatingChange = 123665
timeLastOriginatingChange = 2008-06-25 10:26:41
VersionLastOriginatingChange = 1
......................... HO2 failed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
The registry lookup failed to determine the state of the SYSVOL. The

error returned was 0 (The operation completed successfully.). Check

the FRS event log to see if the SYSVOL has successfully been shared.
......................... HO2 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: 0x800034FD
Time Generated: 06/26/2008 14:52:17
(Event String could not be retrieved)
......................... HO2 failed test frsevent
Starting test: kccevent
* The KCC Event log test
An Warning Event occured. EventID: 0x80000785
Time Generated: 06/27/2008 09:41:55
Event String: The attempt to establish a replication link for

the following writable directory partition

failed.



Directory partition:

CN=Configuration,DC=INS,DC=LAN

Source domain controller:

CN=NTDS
Settings,CN=HO,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN



Source domain controller address:

d289a902-e573-415e-a321-39d3ee5f4d16._msdcs.INS.LAN



Intersite transport (if any):





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:

5 Access is denied.
An Warning Event occured. EventID: 0x80000785
Time Generated: 06/27/2008 09:41:55
Event String: The attempt to establish a replication link for

the following writable directory partition

failed.



Directory partition:

CN=Schema,CN=Configuration,DC=INS,DC=LAN

Source domain controller:

CN=NTDS
Settings,CN=HO,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN



Source domain controller address:

d289a902-e573-415e-a321-39d3ee5f4d16._msdcs.INS.LAN



Intersite transport (if any):





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:

5 Access is denied.
An Warning Event occured. EventID: 0x80000785
Time Generated: 06/27/2008 09:41:55
Event String: The attempt to establish a replication link for

the following writable directory partition

failed.



Directory partition:

DC=INS,DC=LAN

Source domain controller:

CN=NTDS
Settings,CN=HO,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN



Source domain controller address:

d289a902-e573-415e-a321-39d3ee5f4d16._msdcs.INS.LAN



Intersite transport (if any):





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:

5 Access is denied.
......................... HO2 failed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x40000004
Time Generated: 06/27/2008 09:43:33
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 06/27/2008 09:43:34
(Event String could not be retrieved)
......................... HO2 failed test systemlog
Starting test: VerifyReplicas
For the partition (DC=ForestDnsZones,DC=INS,DC=LAN) we encountered

the following error retrieving the cross-ref's


(CN=115b376a-700f-4891-9d69-83262667be35,CN=Partitions,CN=Configuration,DC=INS,DC=LAN)

information:
LDAP Error 0x2095 (8341).
For the partition (DC=DomainDnsZones,DC=INS,DC=LAN) we encountered

the following error retrieving the cross-ref's


(CN=8c554781-5cbc-480c-a9da-834c6e9d04fd,CN=Partitions,CN=Configuration,DC=INS,DC=LAN)

information:
LDAP Error 0x2095 (8341).
......................... HO2 failed test VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)

CN=HO2,OU=Domain Controllers,DC=INS,DC=LAN and backlink on


CN=HO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN

are correct.
The system object reference (frsComputerReferenceBL)

CN=HO2,CN=Domain System Volume (SYSVOL share),CN=File Replication
Service,CN=System,DC=INS,DC=LAN

and backlink on CN=HO2,OU=Domain Controllers,DC=INS,DC=LAN are

correct.
The system object reference (serverReferenceBL)

CN=HO2,CN=Domain System Volume (SYSVOL share),CN=File Replication
Service,CN=System,DC=INS,DC=LAN

and backlink on

CN=NTDS
Settings,CN=HO2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=INS,DC=LAN

are correct.
......................... HO2 passed test VerifyReferences
Starting test: VerifyEnterpriseReferences
Can't determine the age of the cross-ref


CN=115b376a-700f-4891-9d69-83262667be35,CN=Partitions,CN=Configuration,DC=INS,DC=LAN

for the partition DC=ForestDnsZones,DC=INS,DC=LAN, so following
errors

relating to this cross-ref/partition may disappear after replication

coalesces. Please ensure that replication is working from the Domain

Naming FSMO to this DC, and retry this test to see if errors
continue.

Can't determine the age of the cross-ref


CN=8c554781-5cbc-480c-a9da-834c6e9d04fd,CN=Partitions,CN=Configuration,DC=INS,DC=LAN

for the partition DC=DomainDnsZones,DC=INS,DC=LAN, so following
errors

relating to this cross-ref/partition may disappear after replication

coalesces. Please ensure that replication is working from the Domain

Naming FSMO to this DC, and retry this test to see if errors
continue.

Can't determine the age of the cross-ref

CN=Enterprise
Configuration,CN=Partitions,CN=Configuration,DC=INS,DC=LAN

for the partition CN=Configuration,DC=INS,DC=LAN, so following errors

relating to this cross-ref/partition may disappear after replication

coalesces. Please ensure that replication is working from the Domain

Naming FSMO to this DC, and retry this test to see if errors
continue.

Can't determine the age of the cross-ref

CN=Enterprise Schema,CN=Partitions,CN=Configuration,DC=INS,DC=LAN for

the partition CN=Schema,CN=Configuration,DC=INS,DC=LAN, so following

errors relating to this cross-ref/partition may disappear after

replication coalesces. Please ensure that replication is working

from the Domain Naming FSMO to this DC, and retry this test to see if

errors continue.
Can't determine the age of the cross-ref

CN=INS,CN=Partitions,CN=Configuration,DC=INS,DC=LAN for the partition

DC=INS,DC=LAN, so following errors relating to this

cross-ref/partition may disappear after replication coalesces.

Please ensure that replication is working from the Domain Naming FSMO

to this DC, and retry this test to see if errors continue.
......................... HO2 failed test VerifyEnterpriseReferences
Starting test: CheckSecurityError
* Dr Auth: Beginning security errors check!
Found KDC HO for domain INS.LAN in site Default-First-Site-Name
Checking machine account for DC HO2 on DC HO.
* Missing SPN :LDAP/HO2.INS.LAN/INS.LAN
* Missing SPN :LDAP/HO2.INS.LAN
* Missing SPN :LDAP/HO2
* Missing SPN :LDAP/HO2.INS.LAN/INS
* Missing SPN
:LDAP/92bd3f78-2e3c-44a1-9f55-0df888ab65b6._msdcs.INS.LAN
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/92bd3f78-2e3c-44a1-9f55-0df888ab65b6/INS.LAN
* Missing SPN :HOST/HO2.INS.LAN/INS.LAN
* Missing SPN :HOST/HO2.INS.LAN
* Missing SPN :HOST/HO2
* Missing SPN :HOST/HO2.INS.LAN/INS
* Missing SPN :GC/HO2.INS.LAN/INS.LAN
Unable to verify the machine account (CN=HO2,OU=Domain
Controllers,DC=INS,DC=LAN) for HO2 on HO.
Source DC HO1 has possible security error (5). Diagnosing...
Found KDC HO for domain INS.LAN in site Default-First-Site-Name
Checking time skew between servers:
HO1
HO
Time is in sync: 0 seconds different.
Checking machine account for DC HO1 on DC HO.
* SPN found :LDAP/HO1.INS.LAN/INS.LAN
* SPN found :LDAP/HO1.INS.LAN
* SPN found :LDAP/HO1
* SPN found :LDAP/HO1.INS.LAN/INS
* SPN found
:LDAP/c11bb666-c889-4cc0-9c25-a51bf1ac5614._msdcs.INS.LAN
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/c11bb666-c889-4cc0-9c25-a51bf1ac5614/INS.LAN
* SPN found :HOST/HO1.INS.LAN/INS.LAN
* SPN found :HOST/HO1.INS.LAN
* SPN found :HOST/HO1
* SPN found :HOST/HO1.INS.LAN/INS
* SPN found :GC/HO1.INS.LAN/INS.LAN
Checking for CN=HO1,OU=Domain Controllers,DC=INS,DC=LAN in
domain DC=INS,DC=LAN on 2 servers
Object is up-to-date on all servers.
* Security Permissions check for all NC's on DC HO1.
* Security Permissions Check for
DC=ForestDnsZones,DC=INS,DC=LAN
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=INS,DC=LAN
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=INS,DC=LAN
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=INS,DC=LAN
(Configuration,Version 2)
* Security Permissions Check for
DC=INS,DC=LAN
(Domain,Version 2)
* Network Logons Privileges Check
Verified share \\HO1\netlogon
Verified share \\HO1\sysvol
Checking for CN=HO1,OU=Domain Controllers,DC=INS,DC=LAN in
domain DC=INS,DC=LAN on 3 servers
Authoritative attribute dBCSPwd on HO1 (writeable)
usnLocalChange = 129911
LastOriginatingDsa = HO1
usnOriginatingChange = 129911
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 4
Out-of-date attribute dBCSPwd on HO2 (writeable)
usnLocalChange = 80879
LastOriginatingDsa = HO2
usnOriginatingChange = 80879
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 3
Authoritative attribute lmPwdHistory on HO (writeable)
usnLocalChange = 3390588
LastOriginatingDsa = HO1
usnOriginatingChange = 129911
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 4
Out-of-date attribute lmPwdHistory on HO2 (writeable)
usnLocalChange = 80879
LastOriginatingDsa = HO2
usnOriginatingChange = 80879
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 3
Authoritative attribute ntPwdHistory on HO1 (writeable)
usnLocalChange = 129911
LastOriginatingDsa = HO1
usnOriginatingChange = 129911
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 4
Out-of-date attribute ntPwdHistory on HO2 (writeable)
usnLocalChange = 80879
LastOriginatingDsa = HO2
usnOriginatingChange = 80879
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 3
Authoritative attribute pwdLastSet on HO1 (writeable)
usnLocalChange = 129911
LastOriginatingDsa = HO1
usnOriginatingChange = 129911
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 4
Out-of-date attribute pwdLastSet on HO2 (writeable)
usnLocalChange = 80879
LastOriginatingDsa = HO2
usnOriginatingChange = 80879
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 3
Authoritative attribute supplementalCredentials on HO
(writeable)
usnLocalChange = 3390588
LastOriginatingDsa = HO1
usnOriginatingChange = 129912
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 3
Out-of-date attribute supplementalCredentials on HO2
(writeable)
usnLocalChange = 80880
LastOriginatingDsa = HO2
usnOriginatingChange = 80880
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 2
Authoritative attribute unicodePwd on HO1 (writeable)
usnLocalChange = 129911
LastOriginatingDsa = HO1
usnOriginatingChange = 129911
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 4
Out-of-date attribute unicodePwd on HO2 (writeable)
usnLocalChange = 80879
LastOriginatingDsa = HO2
usnOriginatingChange = 80879
timeLastOriginatingChange = 2008-06-26 16:12:30
VersionLastOriginatingChange = 3
Unable to verify the convergence of this machine account
(CN=HO1,OU=Domain Controllers,DC=INS,DC=LAN) on this domain (DC=INS,DC=LAN).
Does the machine account password need reseting or are the SPN's in sync?
[HO1] Unable to diagnose problem for this source. See any
errors reported in attempting tests.
Source DC HO has possible security error (5). Diagnosing...
Found KDC HO for domain INS.LAN in site Default-First-Site-Name
.

Relevant Pages

  • Re: "Access Denied" message when adding member server in existing
    ... The server seems not having connectivity to the RID master. ... The File Replication Service SYSVOL ready test ... Source domain controller address: ... Running partition tests on: ForestDnsZones ...
    (microsoft.public.windows.server.active_directory)
  • Re: KRB_APP_ERR_MODIFIED
    ... After that make sure that your replication between the two existing DC's is correct, repadmin /showrepl on a command prompt. ... These servers can't get changes from home server HO2: ... Authoritative attribute name on HO1 (writeable) ... Source domain controller address: ...
    (microsoft.public.windows.server.active_directory)
  • Re: "Access Denied" message when adding member server in existing
    ... The server seems not having connectivity to the RID master. ... The File Replication Service SYSVOL ready test ... Source domain controller address: ... Running partition tests on: ForestDnsZones ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication error on domain member W2K3 DC?
    ... AD replication is VERY fussy about DNS being in tip top shape. ... > from the SBS server which is the NTP server as well. ... >> Source domain controller address: ...
    (microsoft.public.windows.server.sbs)
  • Re: Ran DCPromo now no replication
    ... If you don't have the tools installed, install them from your server install ... Just select both dcdiag and netdiag make sure verbose is set. ... DC but then i try to force replication i get this error "Naming Context is ... Source domain controller address: ...
    (microsoft.public.windows.server.active_directory)