One way communication with DC's

P

peternied

I have 1 DC of backup1.our_domain.us which I will be phasing out in a
few days and I have its replacement online backup2.our_domain.us and I
can replicate data from backup1 onto backup2.

- The shares that are suppose to be created by frs aren't there
(backup2 and ns2 don't have sysvol shares when I consult net share)

- The following event log errors:
The File Replication Service is having trouble enabling replication
from backup1.our_domain.us to BACKUP2 for c:\windows\sysvol\domain
using the DNS name backup1.our_domain.us. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name backup1.our_domain.us
from this computer.
[2] FRS is not running on backup1.our_domain.us.
[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.

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

- There are other errors along these lines: NTDS Replicate ID1586 and
NetLogon 5782

The netlogon error doesn't make any sense to me, unless I need to
change the network cards dns controllers to the local machine first and
then the other DC. It is setup to talk to the current DC and then the
ISP dns provider

On the DNS for backup1 & 2, there _is_ entries in the our_domain.us for
the srv entries., this difference seems to be enough to let backup2
replicate from backup1.

Dcdiag dump:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\BACKUP1
Starting test: Connectivity
......................... BACKUP1 passed test Connectivity

Testing server: Default-First-Site\BACKUP2
Starting test: Connectivity
......................... BACKUP2 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site\BACKUP1
Starting test: Replications
......................... BACKUP1 passed test Replications
Starting test: NCSecDesc
......................... BACKUP1 passed test NCSecDesc
Starting test: NetLogons
......................... BACKUP1 passed test NetLogons
Starting test: Advertising
......................... BACKUP1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... BACKUP1 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... BACKUP1 passed test RidManager
Starting test: MachineAccount
......................... BACKUP1 passed test MachineAccount
Starting test: Services
......................... BACKUP1 passed test Services
Starting test: ObjectsReplicated
......................... BACKUP1 passed test
ObjectsReplicated
Starting test: frssysvol
......................... BACKUP1 passed test frssysvol
Starting test: frsevent
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.
......................... BACKUP1 failed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/04/2005 17:04:43
Event String: The attempt to establish a replication link
for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/04/2005 17:08:05
Event String: The attempt to establish a replication link
for
......................... BACKUP1 failed test kccevent
Starting test: systemlog
......................... BACKUP1 passed test systemlog
Starting test: VerifyReferences
......................... BACKUP1 passed test VerifyReferences

Testing server: Default-First-Site\BACKUP2
Starting test: Replications
......................... BACKUP2 passed test Replications
Starting test: NCSecDesc
......................... BACKUP2 passed test NCSecDesc
Starting test: NetLogons
......................... BACKUP2 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for
\\backup1.our_domain.us, when we were trying to reach BACKUP2.
Server is not responding or is not considered suitable.
......................... BACKUP2 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... BACKUP2 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... BACKUP2 passed test RidManager
Starting test: MachineAccount
......................... BACKUP2 passed test MachineAccount
Starting test: Services
......................... BACKUP2 passed test Services
Starting test: ObjectsReplicated
Authoritative attribute nTSecurityDescriptor on BACKUP2
(writeable)
usnLocalChange = 12290
LastOriginatingDsa = BACKUP2
usnOriginatingChange = 12290
timeLastOriginatingChange = 2005-11-04 09:30:56
VersionLastOriginatingChange = 2
Out-of-date attribute nTSecurityDescriptor on BACKUP1
(writeable)
usnLocalChange = 349261
LastOriginatingDsa = BACKUP1
usnOriginatingChange = 349261
timeLastOriginatingChange = 2005-11-04 09:34:05
VersionLastOriginatingChange = 1
Authoritative attribute servicePrincipalName on BACKUP2
(writeable)
usnLocalChange = 16385
LastOriginatingDsa = BACKUP2
usnOriginatingChange = 16385
timeLastOriginatingChange = 2005-11-04 15:59:07
VersionLastOriginatingChange = 13
Out-of-date attribute servicePrincipalName on BACKUP1
(writeable)
usnLocalChange = 349544
LastOriginatingDsa = BACKUP1
usnOriginatingChange = 349544
timeLastOriginatingChange = 2005-11-04 15:59:03
VersionLastOriginatingChange = 12
Authoritative attribute msDS-hasMasterNCs on BACKUP2
(writeable)
usnLocalChange = 12489
LastOriginatingDsa = BACKUP2
usnOriginatingChange = 12489
timeLastOriginatingChange = 2005-11-04 11:10:48
VersionLastOriginatingChange = 11
Out-of-date attribute msDS-hasMasterNCs on BACKUP1
(writeable)
usnLocalChange = 349276
LastOriginatingDsa = BACKUP1
usnOriginatingChange = 349276
timeLastOriginatingChange = 2005-11-04 09:35:42
VersionLastOriginatingChange = 1
......................... BACKUP2 failed test
ObjectsReplicated
Starting test: frssysvol
......................... BACKUP2 passed test frssysvol
Starting test: frsevent
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.
......................... BACKUP2 failed test frsevent
Starting test: kccevent
......................... BACKUP2 passed test kccevent
Starting test: systemlog
......................... BACKUP2 passed test systemlog
Starting test: VerifyReferences
......................... BACKUP2 passed test VerifyReferences

Running partition tests on : TAPI3Directory
Starting test: CrossRefValidation
......................... TAPI3Directory passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... TAPI3Directory 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 : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones 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 : our_domain
Starting test: CrossRefValidation
......................... our_domain passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... our_domain passed test CheckSDRefDom

Running enterprise tests on : our_domain.us
Starting test: Intersite
......................... our_domain.us passed test Intersite
Starting test: FsmoCheck
......................... our_domain.us passed test FsmoCheck


Any help is much appreciated, Note I have looked at a number of
knowledge base articles on this matter and I haven't come to any
conclusion
 
P

Paul Bergson

It appears that there is a name resolution issue.

Dcdiag reported:

The name Warning: DsGetDcName returned information for
\\backup1.our_domain.us, when we were trying to reach BACKUP2. Server is
not responding or is not considered suitable.

Check the srv records to see if they are registered properly
See Troubleshooting Domain Controller Locator DNS Records Registration
Failure at
http://www.microsoft.com/technet/pr...ory/maintain/opsguide/part1/adogd10.mspx#EDAA


--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.


I have 1 DC of backup1.our_domain.us which I will be phasing out in a
few days and I have its replacement online backup2.our_domain.us and I
can replicate data from backup1 onto backup2.

- The shares that are suppose to be created by frs aren't there
(backup2 and ns2 don't have sysvol shares when I consult net share)

- The following event log errors:
The File Replication Service is having trouble enabling replication
from backup1.our_domain.us to BACKUP2 for c:\windows\sysvol\domain
using the DNS name backup1.our_domain.us. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name backup1.our_domain.us
from this computer.
[2] FRS is not running on backup1.our_domain.us.
[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.

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

- There are other errors along these lines: NTDS Replicate ID1586 and
NetLogon 5782

The netlogon error doesn't make any sense to me, unless I need to
change the network cards dns controllers to the local machine first and
then the other DC. It is setup to talk to the current DC and then the
ISP dns provider

On the DNS for backup1 & 2, there _is_ entries in the our_domain.us for
the srv entries., this difference seems to be enough to let backup2
replicate from backup1.

Dcdiag dump:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\BACKUP1
Starting test: Connectivity
......................... BACKUP1 passed test Connectivity

Testing server: Default-First-Site\BACKUP2
Starting test: Connectivity
......................... BACKUP2 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site\BACKUP1
Starting test: Replications
......................... BACKUP1 passed test Replications
Starting test: NCSecDesc
......................... BACKUP1 passed test NCSecDesc
Starting test: NetLogons
......................... BACKUP1 passed test NetLogons
Starting test: Advertising
......................... BACKUP1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... BACKUP1 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... BACKUP1 passed test RidManager
Starting test: MachineAccount
......................... BACKUP1 passed test MachineAccount
Starting test: Services
......................... BACKUP1 passed test Services
Starting test: ObjectsReplicated
......................... BACKUP1 passed test
ObjectsReplicated
Starting test: frssysvol
......................... BACKUP1 passed test frssysvol
Starting test: frsevent
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.
......................... BACKUP1 failed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/04/2005 17:04:43
Event String: The attempt to establish a replication link
for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/04/2005 17:08:05
Event String: The attempt to establish a replication link
for
......................... BACKUP1 failed test kccevent
Starting test: systemlog
......................... BACKUP1 passed test systemlog
Starting test: VerifyReferences
......................... BACKUP1 passed test VerifyReferences

Testing server: Default-First-Site\BACKUP2
Starting test: Replications
......................... BACKUP2 passed test Replications
Starting test: NCSecDesc
......................... BACKUP2 passed test NCSecDesc
Starting test: NetLogons
......................... BACKUP2 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for
\\backup1.our_domain.us, when we were trying to reach BACKUP2.
Server is not responding or is not considered suitable.
......................... BACKUP2 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... BACKUP2 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... BACKUP2 passed test RidManager
Starting test: MachineAccount
......................... BACKUP2 passed test MachineAccount
Starting test: Services
......................... BACKUP2 passed test Services
Starting test: ObjectsReplicated
Authoritative attribute nTSecurityDescriptor on BACKUP2
(writeable)
usnLocalChange = 12290
LastOriginatingDsa = BACKUP2
usnOriginatingChange = 12290
timeLastOriginatingChange = 2005-11-04 09:30:56
VersionLastOriginatingChange = 2
Out-of-date attribute nTSecurityDescriptor on BACKUP1
(writeable)
usnLocalChange = 349261
LastOriginatingDsa = BACKUP1
usnOriginatingChange = 349261
timeLastOriginatingChange = 2005-11-04 09:34:05
VersionLastOriginatingChange = 1
Authoritative attribute servicePrincipalName on BACKUP2
(writeable)
usnLocalChange = 16385
LastOriginatingDsa = BACKUP2
usnOriginatingChange = 16385
timeLastOriginatingChange = 2005-11-04 15:59:07
VersionLastOriginatingChange = 13
Out-of-date attribute servicePrincipalName on BACKUP1
(writeable)
usnLocalChange = 349544
LastOriginatingDsa = BACKUP1
usnOriginatingChange = 349544
timeLastOriginatingChange = 2005-11-04 15:59:03
VersionLastOriginatingChange = 12
Authoritative attribute msDS-hasMasterNCs on BACKUP2
(writeable)
usnLocalChange = 12489
LastOriginatingDsa = BACKUP2
usnOriginatingChange = 12489
timeLastOriginatingChange = 2005-11-04 11:10:48
VersionLastOriginatingChange = 11
Out-of-date attribute msDS-hasMasterNCs on BACKUP1
(writeable)
usnLocalChange = 349276
LastOriginatingDsa = BACKUP1
usnOriginatingChange = 349276
timeLastOriginatingChange = 2005-11-04 09:35:42
VersionLastOriginatingChange = 1
......................... BACKUP2 failed test
ObjectsReplicated
Starting test: frssysvol
......................... BACKUP2 passed test frssysvol
Starting test: frsevent
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.
......................... BACKUP2 failed test frsevent
Starting test: kccevent
......................... BACKUP2 passed test kccevent
Starting test: systemlog
......................... BACKUP2 passed test systemlog
Starting test: VerifyReferences
......................... BACKUP2 passed test VerifyReferences

Running partition tests on : TAPI3Directory
Starting test: CrossRefValidation
......................... TAPI3Directory passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... TAPI3Directory 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 : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones 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 : our_domain
Starting test: CrossRefValidation
......................... our_domain passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... our_domain passed test CheckSDRefDom

Running enterprise tests on : our_domain.us
Starting test: Intersite
......................... our_domain.us passed test Intersite
Starting test: FsmoCheck
......................... our_domain.us passed test FsmoCheck


Any help is much appreciated, Note I have looked at a number of
knowledge base articles on this matter and I haven't come to any
conclusion
Click to expand...
 
J

Jorge_de_Almeida_Pinto

I have 1 DC of backup1.our_domain.us which I will be phasing
out in a
few days and I have its replacement online
backup2.our_domain.us and I
can replicate data from backup1 onto backup2.

- The shares that are suppose to be created by frs aren't
there
(backup2 and ns2 don't have sysvol shares when I consult net
share)

- The following event log errors:
The File Replication Service is having trouble enabling
replication
from backup1.our_domain.us to BACKUP2 for
c:windowssysvoldomain
using the DNS name backup1.our_domain.us. FRS will keep
retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name
backup1.our_domain.us
from this computer.
[2] FRS is not running on backup1.our_domain.us.
[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.

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

- There are other errors along these lines: NTDS Replicate
ID1586 and
NetLogon 5782

The netlogon error doesn't make any sense to me, unless I need
to
change the network cards dns controllers to the local machine
first and
then the other DC. It is setup to talk to the current DC and
then the
ISP dns provider

On the DNS for backup1 & 2, there _is_ entries in the
our_domain.us for
the srv entries., this difference seems to be enough to let
backup2
replicate from backup1.

Dcdiag dump:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-SiteBACKUP1
Starting test: Connectivity
......................... BACKUP1 passed test
Connectivity

Testing server: Default-First-SiteBACKUP2
Starting test: Connectivity
......................... BACKUP2 passed test
Connectivity

Doing primary tests

Testing server: Default-First-SiteBACKUP1
Starting test: Replications
......................... BACKUP1 passed test
Replications
Starting test: NCSecDesc
......................... BACKUP1 passed test
NCSecDesc
Starting test: NetLogons
......................... BACKUP1 passed test
NetLogons
Starting test: Advertising
......................... BACKUP1 passed test
Advertising
Starting test: KnowsOfRoleHolders
......................... BACKUP1 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... BACKUP1 passed test
RidManager
Starting test: MachineAccount
......................... BACKUP1 passed test
MachineAccount
Starting test: Services
......................... BACKUP1 passed test
Services
Starting test: ObjectsReplicated
......................... BACKUP1 passed test
ObjectsReplicated
Starting test: frssysvol
......................... BACKUP1 passed test
frssysvol
Starting test: frsevent
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.
......................... BACKUP1 failed test
frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/04/2005 17:04:43
Event String: The attempt to establish a
replication link
for
An Warning Event occured. EventID: 0x80000785
Time Generated: 11/04/2005 17:08:05
Event String: The attempt to establish a
replication link
for
......................... BACKUP1 failed test
kccevent
Starting test: systemlog
......................... BACKUP1 passed test
systemlog
Starting test: VerifyReferences
......................... BACKUP1 passed test
VerifyReferences

Testing server: Default-First-SiteBACKUP2
Starting test: Replications
......................... BACKUP2 passed test
Replications
Starting test: NCSecDesc
......................... BACKUP2 passed test
NCSecDesc
Starting test: NetLogons
......................... BACKUP2 passed test
NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for
\backup1.our_domain.us, when we were trying to reach BACKUP2.
Server is not responding or is not considered
suitable.
......................... BACKUP2 failed test
Advertising
Starting test: KnowsOfRoleHolders
......................... BACKUP2 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... BACKUP2 passed test
RidManager
Starting test: MachineAccount
......................... BACKUP2 passed test
MachineAccount
Starting test: Services
......................... BACKUP2 passed test
Services
Starting test: ObjectsReplicated
Authoritative attribute nTSecurityDescriptor on
BACKUP2
(writeable)
usnLocalChange = 12290
LastOriginatingDsa = BACKUP2
usnOriginatingChange = 12290
timeLastOriginatingChange = 2005-11-04 09:30:56
VersionLastOriginatingChange = 2
Out-of-date attribute nTSecurityDescriptor on
BACKUP1
(writeable)
usnLocalChange = 349261
LastOriginatingDsa = BACKUP1
usnOriginatingChange = 349261
timeLastOriginatingChange = 2005-11-04 09:34:05
VersionLastOriginatingChange = 1
Authoritative attribute servicePrincipalName on
BACKUP2
(writeable)
usnLocalChange = 16385
LastOriginatingDsa = BACKUP2
usnOriginatingChange = 16385
timeLastOriginatingChange = 2005-11-04 15:59:07
VersionLastOriginatingChange = 13
Out-of-date attribute servicePrincipalName on
BACKUP1
(writeable)
usnLocalChange = 349544
LastOriginatingDsa = BACKUP1
usnOriginatingChange = 349544
timeLastOriginatingChange = 2005-11-04 15:59:03
VersionLastOriginatingChange = 12
Authoritative attribute msDS-hasMasterNCs on
BACKUP2
(writeable)
usnLocalChange = 12489
LastOriginatingDsa = BACKUP2
usnOriginatingChange = 12489
timeLastOriginatingChange = 2005-11-04 11:10:48
VersionLastOriginatingChange = 11
Out-of-date attribute msDS-hasMasterNCs on BACKUP1
(writeable)
usnLocalChange = 349276
LastOriginatingDsa = BACKUP1
usnOriginatingChange = 349276
timeLastOriginatingChange = 2005-11-04 09:35:42
VersionLastOriginatingChange = 1
......................... BACKUP2 failed test
ObjectsReplicated
Starting test: frssysvol
......................... BACKUP2 passed test
frssysvol
Starting test: frsevent
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.
......................... BACKUP2 failed test
frsevent
Starting test: kccevent
......................... BACKUP2 passed test
kccevent
Starting test: systemlog
......................... BACKUP2 passed test
systemlog
Starting test: VerifyReferences
......................... BACKUP2 passed test
VerifyReferences

Running partition tests on : TAPI3Directory
Starting test: CrossRefValidation
......................... TAPI3Directory passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... TAPI3Directory 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 : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones 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 : our_domain
Starting test: CrossRefValidation
......................... our_domain passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... our_domain passed test
CheckSDRefDom

Running enterprise tests on : our_domain.us
Starting test: Intersite
......................... our_domain.us passed test
Intersite
Starting test: FsmoCheck
......................... our_domain.us passed test
FsmoCheck


Any help is much appreciated, Note I have looked at a number
of
knowledge base articles on this matter and I haven't come to
any
conclusion
Click to expand...

have you seen:
http://www.eventid.net/display.asp?eventid=1586&eventno=781&source=NTDS Replication&phase=1

http://www.eventid.net/display.asp?eventid=5782&eventno=481&source=NETLOGON&phase=1
 
P

Peter Nied

- Fixed

To fix it I ended up going into dns and creating a number of srv
records that should have been created during the promotion process.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

event 1265 ntds kcc - access denied 3
Slow Logons and Can't open files 0
For Chriss 3 netdiag and dcdiag 5
Re: adprep.exe problems 3
DC Issues... 2
RPC Endpoint Mapper Error 1
DCDIAG /e : replicatedobjects test fails 1
Windows 2000 Replication error 0

Top