Replication Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Okay here is my problem. This has been my worst nightmare for the last few
weeks. A few months ago a DC crashed at one of our off campus sites. I put
a new server in place ran dcpromo and think everything is okay right? Wrong.
slowly but, surely we start getting problems. Can't add new computers to
the domain, and the new server isn't replicating with other DC's on the
network. Now everything is running super slow at the affected campus. I
have tried to manually replicate but, here is a problem. There are no NTDS
setting under Sites and Services for the new DC? Any help would be greatly
appreciated.
 
Okay here is my problem. This has been my worst nightmare for
the last few
weeks. A few months ago a DC crashed at one of our off campus
sites. I put
a new server in place ran dcpromo and think everything is okay
right? Wrong.
slowly but, surely we start getting problems. Can't add new
computers to
the domain, and the new server isn't replicating with other
DC's on the
network. Now everything is running super slow at the affected
campus. I
have tried to manually replicate but, here is a problem.
There are no NTDS
setting under Sites and Services for the new DC? Any help
would be greatly
appreciated.
Click to expand...

what are event ids in the event logs

What does DCDIAG /V say?

See also:
http://support.microsoft.com/?kbid=232538 (Unsuccessful Replication
Without Partner Listed)
 
Okay here is my problem. This has been my worst nightmare for
the last few
weeks. A few months ago a DC crashed at one of our off campus
sites. I put
a new server in place ran dcpromo and think everything is okay
right? Wrong.
slowly but, surely we start getting problems. Can't add new
computers to
the domain, and the new server isn't replicating with other
DC's on the
network. Now everything is running super slow at the affected
campus. I
have tried to manually replicate but, here is a problem.
There are no NTDS
setting under Sites and Services for the new DC? Any help
would be greatly
appreciated.
Click to expand...

Hi

did you perform metadata cleanup for the DC that got crashed
and if not then go ahead and demote the DC that you promoted with that
old name

perform the metadata cleanup for that
and make sure that this information gets replicated to all the DCs

and then go ahead and promote the that DC
and make sure that your DNS is working fine
check for all the records in the DNS
and check if you have all the default shares are available on the DCs
like sysvol, netlogon, admin$, IPC$
 
Okay i did the dcdiag /v and I had a huge amount of errors.

lsaPolicy operation failed with error 67

many error 1722

also in event viewer I see a id of 16650 many times.
 
Okay here is my problem. This has been my worst nightmare for
the last few
weeks. A few months ago a DC crashed at one of our off campus
sites. I put
a new server in place ran dcpromo and think everything is okay
right? Wrong.
slowly but, surely we start getting problems. Can't add new
computers to
the domain, and the new server isn't replicating with other
DC's on the
network. Now everything is running super slow at the affected
campus. I
have tried to manually replicate but, here is a problem.
There are no NTDS
setting under Sites and Services for the new DC? Any help
would be greatly
appreciated.
Click to expand...

hi

ok, so you are getting 1722 "RPC server is unavailable"

so you need to check the DNS
and if you are using 2003 SP1 then call microsoft and ask for the
hotfix 898060

and if you have win2000 with hotfix 893066 install on it then also
call microsoft and ask for hotfix 898060

and check if your machine is pointing to right DNS server
and see if it can resolve all the other DCs
 
Okay i did the dcdiag /v and I had a huge amount of errors.

lsaPolicy operation failed with error 67

many error 1722

also in event viewer I see a id of 16650 many times.
Click to expand...

The DC that crashed... which FSMO roles did it host? Did it host a RID
FSMO? Or is another DC the FSMO role? Is your RID FSMO avalable?

When you ran DCDIAG /V the RIDMANAGER test must have reported failed.

For the 16650 event id (RID FSMO problems) look at:
http://www.eventid.net/display.asp?eventid=16650&eventno=896&source=SAM&phase=1
and http://support.microsoft.com/kb/248410/

The reason you can’t create any computers is that computers also are
security principal. In other words each computer needs an unique SID
in the domain. When you create a security principal on a DC the DC
uses one of the RIDs from its RID block (=500 RIDs). When the RID
block reaches 50% the DC wil ask a new RID block at the RID FSMO DC.
If it is not available it will get no new RID block, although you can
still create securityu principals until the RID block has been
exhausted.
Also see: http://support.microsoft.com/?kbid=839879

Goto a healthy DC and type DCdiag /test:Knowsofroleholders /v to
retrieve who the FSMO owners are.
(http://support.microsoft.com/kb/234790/EN-US/)

If the old DC that crashed host any FSMO roles, have you seized them
to another DC? By the way: only seize a FSMO role when the old FSMO
role owner will never come online again!!!
 
Back
Top