DC rejecting replications requests

I have a virtual server enviroment. I performed a checkpoint on a dc before
I was making a chang eto the group policy. I then restored the checkpoint.
I have severl domains and this dc is in my root. THis is a lab so I only
have i dc in my root.
I have event ID 2103 and 2095
How do I get it replicatiing again? I cannot forcebly demote snce it is the
only dc in the root.

How did you create this DC in a VM? Did you Ghost it? If so, this is
unsupported:
http://eventid.net/display.asp?event...eneral&phase=1
http://eventid.net/display.asp?eventid=2095&source=
se
Also, if it is the only DC in the forest, what is it trying to replicate to
or from? There are no other DCs. So it seems to point that it may have been
ghosted, imaged or attempted a restore from a backup. So the DC either
thinks that there still are other replica DCs, as well as/or the restore or
ghosted image after creating it, got corrupted.

The best way to create such a test environment is to create a replica DC of
the current domain into a VM, then disconnect the VM, then seize all FSMO
roles, make it a GC and make sure you never reintroduce it back into the
main corp network.

Checkpoint? How did you restore that?
What OS are you talking about?
How many DC's are you talking about for the lab domain?
Is the DC a restore and the event id this?

Event Type: Error
Event Source: NTDS General
Event Category: Service Control
Event ID: 2103
Date: 3/10/2005
Time: 4:26:51 PM
User: USN\xxxx$
Computer: xxxx
Description: The Active Directory database has been restored using an unsupported
restoration procedure. Active Directory will be unable to log on users while
this condition persists. As a result, the Net Logon service has paused. User
Action See previous event logs for details. For more information, see Help
and Support Center at http://support.microsoft.com

Sounds that your DC has an USN rollback becasue of creating it from unsupported
way:
http://support.microsoft.com/kb/885875
http://support.microsoft.com/kb/875495/

I did not ghost it. It is a dc in the root domain.
the other dcs in the child domain think that their copy is newer so they
will not accept any from this root dc.

server 2003 os
it is running on hyper v
I know i should not hav retoed the checkpoint
i have 5 child domains
they will not accept rpelication becasue they copy of ad is newer

Sorry but that makes no sense. The root Dc still have to sync with the child
domain and should not be "older". Is that the event id where i posted a complete
entry?

I don't understand your response. How can one DC be newer than another? And
as Meinolf said, it doesn't make any sense and lacks info to assist you
properly.

AD replication uses USN (update sequence numbers) to keep track of each DC
and what their current USN is to determine if it received their updated info
or not. If you ghosted it or used a restore point, you've just completely
changd the USN numbers and threw all the other DCs off and will totally
ignore this DC. If it is the Root DC, then this is detrimental to the whole
forest, and if this is the case, the one main alternative is to rebuild the
whole forest from scratch.

Can you elaborate exactly step by step, the procedure you used to set this
up, please? Include everything including how you used the checkpoint, etc,
to create this machine in the VM and whether it was previously installed on
a physical machine, etc. With that info, we may be able to better assist
with specifics.

[issana]

I have the same problem. I did last month an update to our secondary domain controller (from Windows server 2000 to 2003) on the VMware Server. Then, I find out there is no enough space and then I revert to Windows Server 2000 Image. I didn't realize what I did until I get a complaint from our employees that the changes are not taking effect. Then I find out I have a replication issue. I did the replication manually by opening the inbound and the outbound for the server. Then I did an upgrade to Windows Server 2003 (After I fix the space issue). After that I'm always getting this error when I reboot the Server and the only workaround that I have right now to enable Net Logon Manually. Is there an easy way to fix this without demoting the server??

Event Type: Error
Event Source: NTDS General
Event Category: Service Control
Event ID: 2103
Date: 8/2/2010
Time: 9:41:38 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: PROMETHIUM
Description:
The Active Directory database has been restored using an unsupported restoration procedure.

Active Directory will be unable to log on users while this condition persists. As a result, the Net Logon service has paused.

User Action
See previous event logs for details.

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