DCPROMO / Replication issues

Tech-Archive recommends: Fix windows errors by optimizing your registry

I added a 2nd DC to my W2K3 Domain.

The Domain name <DOMAIN.org> is my public internet domain. This was all
created before I got on the scene, so I’m stuck with it.

Could this be a DNS issue since my internal domain is the same as my
internet domain name?

It should be noted that when I first ran DCPROMO the process failed and my
2nd server was just a member of the domain upon reboot.

I ran DCPROMO again and got no errors.

But now I notice the replication is not working.

The File Replication Service is having trouble enabling replication from
AD02 to AD01 for c:\windows\sysvol\domain using the DNS name AD02.domain.org.
FRS will keep retrying.


In fact it seems the Sysvol folder on the 2nd server was never really created.
The folder structure is there but it is not shared nor is my policies or
scripts. It’s just empty folders.

I demoted and promoted with no change.

I ran dcdiag on the 1st DC below are the results :


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

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

Doing primary tests

Testing server: Default-First-Site-Name\AD01
Starting test: Replications
......................... AD01 passed test Replications
Starting test: NCSecDesc
......................... AD01 passed test NCSecDesc
Starting test: NetLogons
......................... AD01 passed test NetLogons
Starting test: Advertising
......................... AD01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... AD01 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... AD01 passed test RidManager
Starting test: MachineAccount
......................... AD01 passed test MachineAccount
Starting test: Services
......................... AD01 passed test Services
Starting test: ObjectsReplicated
......................... AD01 passed test ObjectsReplicated
Starting test: frssysvol
......................... AD01 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.
......................... AD01 failed test frsevent
Starting test: kccevent
......................... AD01 passed test kccevent
Starting test: systemlog
......................... AD01 passed test systemlog
Starting test: VerifyReferences
......................... AD01 passed test VerifyReferences

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

Running enterprise tests on : DOMAIN.org
Starting test: Intersite
......................... DOMAIN.org passed test Intersite
Starting test: FsmoCheck
......................... DOMAIN.org passed test FsmoCheck


I do believe this was originally a Windows 2000 Domain but the DC is
retired. (I recently found the old DC dusty in a closet, still as a DC with
windows 2000 installed but no reference to it in AD users and computers on my
windows 2003 system) I wonder if the upgrade of AD failed upon creation like
6 months ago.

Any Thoughts?

.

Relevant Pages

  • RE: DNS/Active Directory Issue
    ... PASS - All the DNS entries for DC are registered on DNS server ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... The File Replication Service SYSVOL ready test ...
    (microsoft.public.windows.server.general)
  • Re: frsevent error after promoting to a domain controller
    ... I restarted the file replication server and the errors went away. ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... Starting test: CheckSDRefDom ...
    (microsoft.public.windows.server.active_directory)
  • RE: System cannot log you on error
    ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... Starting test: CheckSDRefDom ... No network provider accepted the given network path.. ...
    (microsoft.public.windows.terminal_services)
  • Re: One way communication with DCs
    ... > The File Replication Service is having trouble enabling ... > Starting test: CrossRefValidation ... > Starting test: CheckSDRefDom ... > Running partition tests on: ...
    (microsoft.public.win2000.active_directory)
  • Re: DCDiag.exe errors
    ... > replication attempt failed: ... > Running partition tests on: ... > Starting test: CrossRefValidation> ... > Starting test: CheckSDRefDom ...
    (microsoft.public.win2000.dns)