Why do clents and my new E2k3 server that exists in the root forestmake requests to child dc's over TCP 3268, 389, & 88?

March 27, 2008

Why do clents and my new E2k3 server that exists in the root forestmake requests to child dc's over TCP 3268, 389, & 88?

I have a root domain 'parent.com'. I have a child domain

'child.parent.com'. Lately I've been noticing on my router syslogs

that some of my XP clients on parent.com have been hitting the child

ADC over tcp 389 and 88. Also, a new E2k3 server I built on

parent.com last week is hitting/receiving traffic over tcp 3268 & 389

to/from the child ADC. Shouldn't this traffic be directed to the

parent.com ADC/GC? I've also noticed that the E2k3 server is sending

Echo requests to the child ADC about every 10 mins.

I've checked my 2 parent ADC's and they are both GC's.

Any help would be appreciated.

March 31, 2008

Re: Why do clents and my new E2k3 server that exists in the rootforest make requests to child dc's over TCP 3268, 389, & 88?

Re: Why do clents and my new E2k3 server that exists in the rootforest make requests to child dc's over TCP 3268, 389, & 88?

On Mar 27, 9:46 am, 05hammer <robert.aus...@rl.af.mil> wrote:

> I have a root domain 'parent.com'. I have a child domain

> 'child.parent.com'. Lately I've been noticing on my router syslogs

> that some of my XP clients on parent.com have been hitting the child

> ADC over tcp 389 and 88. Also, a new E2k3 server I built on

> parent.com last week is hitting/receiving traffic over tcp 3268 & 389

> to/from the child ADC. Shouldn't this traffic be directed to the

> parent.com ADC/GC? I've also noticed that the E2k3 server is sending

> Echo requests to the child ADC about every 10 mins.

>

> I've checked my 2 parent ADC's and they are both GC's.

>

> Any help would be appreciated.

No One has a Clue?

Recommended Posts