Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NTDS KCC 1311 & 1566 Errors Weekly! 1

Status
Not open for further replies.

Cooty

Technical User
Joined
Apr 25, 2003
Messages
16
Hi Guys

A slightly different spin on the usual KCC errors. We have a simple two site set-up with a single GC DC on each site. There are no errors at all reported until the weekend when 1 or both DCs start reporting these errors. Eventually server performance drops and a reboot of both DCs fixes the issue for another week. (We start seeing service specific routing problems for remote users before the restart is required. I.e. ping and browsing works fine but RDP only work locally and Exchange clients fail to connect at all, but this happens only hours after the above errors occur)
Any assistance greatfully received.
 
1311 and 1556 are both telling you there is not enough connectivity.

1. "ping and browsing works fine but RDP only work locally and Exchange clients fail to connect at all". Ping uses relatively small ICMP packets. Browsing used SMB, but again the packets are prelatively small. RDP and Exchange RPC connections use large UDP packets. Try ping -f -l <size> with packets of varying sizes. What happens?

2. Are all the servers 2000? What OS and service pack?

3. What about the clients? Anyone install MS05 019 lately?


On the surface, this sounds very much like your issue:

 
Thanks Guys
I seem to have read the entire Ms KB about NTDS issues. The Exchange and RDP issues occur a day or so after the KCC problem starts. The Primary DC is W2k SP4 however, the other DC is W2003 SP1 and I knew nothing of KB898060. I'll get the hotfix and see how it goes...
Thanks again, Cooty.
 
Yet another problem, as it relates to AD replication, is that in 2003 the timeout for replication was changed from 45 minutes to 5 minutes. You may also want to lengthen the timeout on the 2003 DC.

 
Hi XMSRE

No further problems to date - over two weeks now, many thanks

Cooty
 
Did your problem get completely fixed? I am experiencing the same issue.
 
Completely resolved - no further issues.
 
May I ask what the complete resolution was. Our owner is getting frustrated in us resolving this issue.
 
View KB898060. I downloaded and applied the hotfix for Windows 2003 SP1. Nothing else to do.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top