Re: HELPP!!!!!!!!
- From: "Nik" <nik>
- Date: Wed, 21 Oct 2009 09:53:51 -0400
Thanks Paul,
I absolutely agree with you and to support our argument even more look at
this repadmin output
MyCity\MSDCMC01 @ USN 9832279 @ Time 2009-03-30 09:27:04
"Paul Bergson [MVP-DS]" <pbbergs@xxxxxxxxxxxxxx> wrote in message
news:eCh9NOlUKHA.3428@xxxxxxxxxxxxxxxxxxxxxxx
This dc needs to be removed from the domain/forest. I would demote and
repromote, anything else is going to be a problem from this point forward.
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
"Nik" <nik> wrote in message news:u2rNk$kUKHA.1372@xxxxxxxxxxxxxxxxxxxxxxx
Yeah!!! Sorry that I seem to be all over the place. The three that I
worked on last night are working like a charm. The Error I'm geting on
the PROBLEM server is Event ID:1864
This is the replication status for the following directory partition on
the local domain controller.
Directory partition:
DC=ForestDnsZones,DC=maxxam,DC=lab
The local domain controller has not recently received replication
information from a number of domain controllers. The count of domain
controllers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
1
Tombstone lifetime (days):
60
Domain controllers that do not replicate in a timely manner may encounter
errors. It may miss password changes and be unable to authenticate. A DC
that has not replicated in a tombstone lifetime may have missed the
deletion of some objects, and may be automatically blocked from future
replication until it is reconciled.
To identify the domain controllers by name, install the support tools
included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication
latencies of the domain controllers in the forest. The command is
"repadmin /showvector /latency <partition-dn>".
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
And with all that I'm still getiing updates on the PROBLEM Server. Just
that it takes pretty long. However, I will work on the others and then
demote that server and re-promote it.
I will stick to this thread as I go along.
I will try to keep you updated as much as possible on the process as I
move forward.
Thanks again
"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
news:6cb2911d7e558cc203ba0b60cb3@xxxxxxxxxxxxxxxxxxxxxxx
Hello Nik" nik,
Does this one belong to?
"Restart Server after site link configurations?"
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
" ...Naming context isn in the process of being removed or is not
replicated from the specified server ...". Guys Im having a problem
here. for whatever reasons the KCC is not generating the connection
and if i try to do it manually it reports the error mentioned above
.
- Follow-Ups:
- Re: HELPP!!!!!!!!
- From: Ace Fekay [MCT]
- Re: HELPP!!!!!!!!
- References:
- HELPP!!!!!!!!
- From: Nik
- Re: HELPP!!!!!!!!
- From: Meinolf Weber [MVP-DS]
- Re: HELPP!!!!!!!!
- From: Nik
- Re: HELPP!!!!!!!!
- From: Paul Bergson [MVP-DS]
- HELPP!!!!!!!!
- Prev by Date: Re: HELPP!!!!!!!!
- Next by Date: Joining XP desktop to domain, can't rename computer
- Previous by thread: Re: HELPP!!!!!!!!
- Next by thread: Re: HELPP!!!!!!!!
- Index(es):
Relevant Pages
|
