Windows 2003 KCC errors

Configuration:

“LAN A� is behind Watchguard firebox x700 and contains 2 Windows 2003
servers and 1 Windows 2003 Exchange server.

“LAN B� is behind a Watchguard soho6 and contains 1 Windows 2003 server and
1 Windows 2003 Exchane server.

“LAN C� is “LAN B� is behind a Watchguard soho6 and contains 1 Windows 2003
Exchane server.


Problem:

Within a 48-72 hour time frame any given server may experience this error
message in the event log:

Source: NTDS KCC
Category: Knowledge Consistency
Event ID 1865

This error usually has the communication issue with the server from "LAN C".
It may also continue in this state from 3 hours to 2 days. The server will
then refuse access from any device not on it's local area network. However I
can ping the IP address of that server from the LAN and WAN.

My temporary solution has been to reboot the server on "LAN C" and the
server having the issue. After rebooting both servers all is fine until it
happens again.

I have reconfugred the DNS zone and it replicates to all DC's just fine. I
have removed the ntds settings from all servers in AD Sites and Services and
allowed AD to automatically generate connections. I have tried a few other
things but the problem still persists. Any ideas?

Ray

Ray,
Have a look at this article.
http://support.microsoft.com/?kbid=898060

"Ray Johnson KLG" wrote:

> Configuration:
>
> “LAN A� is behind Watchguard firebox x700 and contains 2 Windows 2003
> servers and 1 Windows 2003 Exchange server.
>
> “LAN B� is behind a Watchguard soho6 and contains 1 Windows 2003 server and
> 1 Windows 2003 Exchane server.
>
> “LAN C� is “LAN B� is behind a Watchguard soho6 and contains 1 Windows 2003
> Exchane server.
>
>
> Problem:
>
> Within a 48-72 hour time frame any given server may experience this error
> message in the event log:
>
> Source: NTDS KCC
> Category: Knowledge Consistency
> Event ID 1865
>
> This error usually has the communication issue with the server from "LAN C".
> It may also continue in this state from 3 hours to 2 days. The server will
> then refuse access from any device not on it's local area network. However I
> can ping the IP address of that server from the LAN and WAN.
>
> My temporary solution has been to reboot the server on "LAN C" and the
> server having the issue. After rebooting both servers all is fine until it
> happens again.
>
> I have reconfugred the DNS zone and it replicates to all DC's just fine. I
> have removed the ntds settings from all servers in AD Sites and Services and
> allowed AD to automatically generate connections. I have tried a few other
> things but the problem still persists. Any ideas?
>
> Ray
>
>

Ray,

I ran into the same problem with the same configuration. It drove me nuts.
Under sites and services, make sure your transport is IP and not SMTP and the
KCC error will go away.

Mike

"Ray Johnson KLG" wrote:

> Configuration:
>
> “LAN A� is behind Watchguard firebox x700 and contains 2 Windows 2003
> servers and 1 Windows 2003 Exchange server.
>
> “LAN B� is behind a Watchguard soho6 and contains 1 Windows 2003 server and
> 1 Windows 2003 Exchane server.
>
> “LAN C� is “LAN B� is behind a Watchguard soho6 and contains 1 Windows 2003
> Exchane server.
>
>
> Problem:
>
> Within a 48-72 hour time frame any given server may experience this error
> message in the event log:
>
> Source: NTDS KCC
> Category: Knowledge Consistency
> Event ID 1865
>
> This error usually has the communication issue with the server from "LAN C".
> It may also continue in this state from 3 hours to 2 days. The server will
> then refuse access from any device not on it's local area network. However I
> can ping the IP address of that server from the LAN and WAN.
>
> My temporary solution has been to reboot the server on "LAN C" and the
> server having the issue. After rebooting both servers all is fine until it
> happens again.
>
> I have reconfugred the DNS zone and it replicates to all DC's just fine. I
> have removed the ntds settings from all servers in AD Sites and Services and
> allowed AD to automatically generate connections. I have tried a few other
> things but the problem still persists. Any ideas?
>
> Ray
>
>