NTDS Replication

[Guest Victor]

Hi,

I encountered these error msg. How to resolve it ?

 

Starting test: KnowsOfRoleHolders

The directory service on TPEDC01 has not finished initializing.

In order for the directory service to consider itself synchronized,

it must attempt an initial synchronization with at least one replica

of this server's writeable domain. It must also obtain Rid

information from the Rid FSMO holder.

The directory service has not signalled the event which lets other

services know that it is ready to accept requests. Services such as

the Key Distribution Center, Intersite Messaging Service, and

NetLogon

will not consider this system as an eligible domain controller.

Thanks.

Victor

[Guest wakaman]

Re: NTDS Replication

 

Hi Victor,

 

Messages as that comes up after you just recently promote a server

into a domain controller. Initialization and replication is still

taking place. so just give it some time and after sysvol

initialization is complete the error will go away,

 

Isaac

[Guest Meinolf Weber]

Re: NTDS Replication

 

Hello Victor,

 

Is the server just promoted, then wait for replication? Or is the server

running longer? Then please describe your domain setup, how many DC's in

how many sites and how are they connected. Also post an unedited ipconfig

/all form all DC's.

 

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

 

> Hi,

> I encountered these error msg. How to resolve it ?

> Starting test: KnowsOfRoleHolders

> The directory service on TPEDC01 has not finished

> initializing.

> In order for the directory service to consider itself

> synchronized,

> it must attempt an initial synchronization with at least one

> replica

> of this server's writeable domain. It must also obtain Rid

> information from the Rid FSMO holder.

> The directory service has not signalled the event which lets

> other

> services know that it is ready to accept requests. Services

> such as

> the Key Distribution Center, Intersite Messaging Service, and

> NetLogon

> will not consider this system as an eligible domain

> controller.

> Thanks.

> Victor

>

[Guest Victor]

Re: NTDS Replication

 

Hi Meinolf,

 

Noped. Its happened since 20/08. I have 2 DC in SG & my parent Co is in

Taipei.

Windows IP Configuration

Host Name . . . . . . . . . . . . : sgpdc01

Primary Dns Suffix . . . . . . . : wtmec.com

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : wtmec.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2

Physical Address. . . . . . . . . : 00-09-6B-8C-8A-42

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.7.1.1

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . : 10.7.1.251

DNS Servers . . . . . . . . . . . : 10.7.1.3

10.1.1.3

"Meinolf Weber" wrote:

> Hello Victor,

>

> Is the server just promoted, then wait for replication? Or is the server

> running longer? Then please describe your domain setup, how many DC's in

> how many sites and how are they connected. Also post an unedited ipconfig

> /all form all DC's.

>

> 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

>

>

> > Hi,

> > I encountered these error msg. How to resolve it ?

> > Starting test: KnowsOfRoleHolders

> > The directory service on TPEDC01 has not finished

> > initializing.

> > In order for the directory service to consider itself

> > synchronized,

> > it must attempt an initial synchronization with at least one

> > replica

> > of this server's writeable domain. It must also obtain Rid

> > information from the Rid FSMO holder.

> > The directory service has not signalled the event which lets

> > other

> > services know that it is ready to accept requests. Services

> > such as

> > the Key Distribution Center, Intersite Messaging Service, and

> > NetLogon

> > will not consider this system as an eligible domain

> > controller.

> > Thanks.

> > Victor

> >

>

>

>

[Guest Victor]

Re: NTDS Replication

 

Hi Meinolf,

 

Noped. Its happened since 20/08. I have 2 DC in SG & my parent Co is in

Taipei.

Windows IP Configuration

Host Name . . . . . . . . . . . . : sgpdc01

Primary Dns Suffix . . . . . . . : wtmec.com

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : wtmec.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2

Physical Address. . . . . . . . . : 00-09-6B-8C-8A-42

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.7.1.1

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . : 10.7.1.251

DNS Servers . . . . . . . . . . . : 10.7.1.3

10.1.1.3

 

"Meinolf Weber" wrote:

> Hello Victor,

>

> Is the server just promoted, then wait for replication? Or is the server

> running longer? Then please describe your domain setup, how many DC's in

> how many sites and how are they connected. Also post an unedited ipconfig

> /all form all DC's.

>

> 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

>

>

> > Hi,

> > I encountered these error msg. How to resolve it ?

> > Starting test: KnowsOfRoleHolders

> > The directory service on TPEDC01 has not finished

> > initializing.

> > In order for the directory service to consider itself

> > synchronized,

> > it must attempt an initial synchronization with at least one

> > replica

> > of this server's writeable domain. It must also obtain Rid

> > information from the Rid FSMO holder.

> > The directory service has not signalled the event which lets

> > other

> > services know that it is ready to accept requests. Services

> > such as

> > the Key Distribution Center, Intersite Messaging Service, and

> > NetLogon

> > will not consider this system as an eligible domain

> > controller.

> > Thanks.

> > Victor

> >

>

>

>

[Guest Meinolf Weber]

Re: NTDS Replication

 

Hello Victor,

 

Please post also the ipconfig /all from TPEDC01 and additional describe how

they are connected, VPN or router or DSL connection. Did you also configure

AD sites and services with both subnets and move the DC's to the belonging

site?

 

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

 

> Hi Meinolf,

>

> Noped. Its happened since 20/08. I have 2 DC in SG & my parent Co is

> in

> Taipei.

> Windows IP Configuration

> Host Name . . . . . . . . . . . . : sgpdc01

> Primary Dns Suffix . . . . . . . : wtmec.com

> Node Type . . . . . . . . . . . . : Unknown

> IP Routing Enabled. . . . . . . . : No

> WINS Proxy Enabled. . . . . . . . : No

> DNS Suffix Search List. . . . . . : wtmec.com

> Ethernet adapter Local Area Connection:

> Connection-specific DNS Suffix . :

> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit

> Ethernet #2

> Physical Address. . . . . . . . . : 00-09-6B-8C-8A-42

> DHCP Enabled. . . . . . . . . . . : No

> IP Address. . . . . . . . . . . . : 10.7.1.1

> Subnet Mask . . . . . . . . . . . : 255.255.0.0

> Default Gateway . . . . . . . . . : 10.7.1.251

> DNS Servers . . . . . . . . . . . : 10.7.1.3

> 10.1.1.3

> "Meinolf Weber" wrote:

>

>> Hello Victor,

>>

>> Is the server just promoted, then wait for replication? Or is the

>> server running longer? Then please describe your domain setup, how

>> many DC's in how many sites and how are they connected. Also post an

>> unedited ipconfig /all form all DC's.

>>

>> 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

>>> Hi,

>>> I encountered these error msg. How to resolve it ?

>>> Starting test: KnowsOfRoleHolders

>>> The directory service on TPEDC01 has not finished

>>> initializing.

>>> In order for the directory service to consider itself

>>> synchronized,

>>> it must attempt an initial synchronization with at least one

>>> replica

>>> of this server's writeable domain. It must also obtain Rid

>>> information from the Rid FSMO holder.

>>> The directory service has not signalled the event which lets

>>> other

>>> services know that it is ready to accept requests. Services

>>> such as

>>> the Key Distribution Center, Intersite Messaging Service, and

>>> NetLogon

>>> will not consider this system as an eligible domain

>>> controller.

>>> Thanks.

>>> Victor