Re: Cross reference for the specified naming context could not be
- From: "Jorge de Almeida Pinto [MVP - DS]" <SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx>
- Date: Thu, 26 Oct 2006 23:09:09 +0200
NEVER ignore replication failures...solve that FIRST!
replication errors CAN turn into the future gates of hell and headaches. Do
you want that? (I would not want that, but that is me!)
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Orvs" <Orvs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4905B40B-607D-4886-9EB6-4CD9B5856978@xxxxxxxxxxxxxxxx
Thanks Jorge!
I run Dcdiag and found so many Replication Latency Warning..
Shall I ignore this or this can cause a problem??? What is this REpli
"Jorge de Almeida Pinto [MVP - DS]" wrote:
is the domain naming master FSMO available? (check its health)
are you using enterprise admin permissions?
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Orvs" <Orvs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:95A1208B-3295-4944-9BF2-B4B325F0C4AD@xxxxxxxxxxxxxxxx
Paul Hi!
I already did the extension of my Forest. Actually I have 12 Child
Domains
and some of them are already migrated to Win2003. However, forest root
domain itself is still in Windows 2000.
For the new incomming Child Domain, I want to use Windows 2003
straight.
However when I promote new one I'm having an error. Question is Is
this
related to Windows 2003/Windows 2000 migration..
Thanks
"Paul Bergson [MVP-DS]" wrote:
Since it is a single forest the Schema FSMO role won't know about all
the
new objects from 2003 until you have prep'd your forest. You can't
introduce a 2003 dc until the forest has been extended.
See an article I have to help with this
http://www.pbbergs.com
Select articles and click on upgrading your forest
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
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.
"Orvs" <Orvs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8B2DAC03-8246-4870-8738-836D15849ACE@xxxxxxxxxxxxxxxx
I'm trying to insert new chid domain (Win2003) on my Forest still on
Win200
Native.
I keep getting this error during DCPROMO.
The cross reference for the specified naming context could not be
found.
This is halfway thru and when it reach the CN partition etc then
error
occured.
What are the causes of this??
.
- References:
- Re: Cross reference for the specified naming context could not be foun
- From: Paul Bergson [MVP-DS]
- Re: Cross reference for the specified naming context could not be
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: Cross reference for the specified naming context could not be
- From: Orvs
- Re: Cross reference for the specified naming context could not be foun
- Prev by Date: Re: Create a lot of account fast
- Next by Date: Re: migrating 2003 AD domains
- Previous by thread: Re: Cross reference for the specified naming context could not be
- Next by thread: Re: another "attribute conversion operation" error
- Index(es):
Relevant Pages
|
Loading