ldap and kerberos errors

[{OOE}Death]

I'm having problems with the DNS lots of the above. I can't figure it out. M$ is no help

[Malice]

Advanced Server, .NET or what?

[Kyraath]

I remember the visg server having a ton of errors like that also, can't remember for sure but it might be the error that MS told us to just ignore.
Stupid MS

[D-Bone]

I have no idea what that even means, I thought your keyboard was broken while you were typing that....

[Malice]

Lol so did I!!

[Ghost]

You guys are so helpfull. Usually when I've seen those errors it is on a 2000 AD controller where the DNS is not working properly for registering the _tcp and _udp resource records. Usually when you fix those errors things go away. I've also seen similar errors on 2k pro and XP pro joined to a domain where either the DNS is not functioning properly or the 2k AD is not available for some reason.

[D-Bone]

Right, exactly what I was thinking. Me and Ghosty think so much alike its scary....

[Kyraath]

yeah, when I said "MS told us to ignore it" that translates to what ghosty said, I just said it in dragon :wink:

[JiMbOb]

My interpreptation of it is the following:

Since Kerberos is a distributed key architecture, and Windblows uses Kerberos for communications, if you get a mismatched key (either by un-synched time or what-not) you'll get a plethora of Kerberos errors as Windblows is trying to send calls back and forth.

Maybe I'm just talking out my butt. Good luck.

-Kris