|
This whole thing just sounds weird.
At this point I would do two things. Please note I don't
have great reasons for suggesting them, just gut feeling.
1. I would check the SMB signing policies to see if they
are aligned. Most likely if you don't have that set at the domain controller
policy level you have signing on on the K3 machine and undefined on the 2K. Yes,
this shouldn't be an issue with 2K machines but I have seen it be an issue with
2K and XP machines touching K3.
2. I would verify that the SPNs for the DCs are identical
on all of the DCs.... I.E. DC1 has the same SPNs registered on every DC. Ditto
DC2, DC3, DCn. I have seen these out of sync before and causing interesting
replication issues. It took manual editing of the SPNs to
correct.
joe From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Svetlana Kouznetsova Sent: Wednesday, May 19, 2004 2:58 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] FATAL kerberos error on W2K3 server Well, endpoint
mapper error message is actually, in event log for the W2K domain controller,
which started to complain only after W2K3 DC appeared in the
domain...
Interesting that
I've run all tests possible in dcdiag separately, testing connectivity,
replications, security discriptors, frsevent, etc, etc on both DC - w2k (old
one) and W2K3 (new one) - all tests - ...passed! Error of endpoint mappers has
been only discovered after replication to the new DC didn't take place and
I went on checking old DCs.
On the new W2K3
DC - sysvol permissions, etc - everything, as it should be, but - all the data
hangs in staging and staging area since first time replication (after
dcpromo).
Replmon shows
that W2K3 server has up to date data replicated from other DCs, but on other DC
replmon doesn't show that this new server is a replication partner...Also - no
NTDS links shown for W2K3 in ADSS ... (hmmm..looks a bit a mess, huh?)
netdiag on W2K3
server only shows frsevent as FAILED.
To be honest, I
don't know where else to look now...:-/
RE: The fact that you had machines not getting tickets before but are now is a wee bit scary as well.
Lana.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman Sent: Wednesday, May 19, 2004 12:48 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] FATAL kerberos error on W2K3 server Debugging lsass is highly underrated. That’s right, under. Sure it’s
not for the faint of heart, but man the fun stuff you get in there. I say just
attach and have fun just for the heck of it. That’s what I do on my weekends
(sad yet true). So the error below, is that from netdiag?
Or another tool? From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of joe I hate to say it but
when I see endpoint mapper issues one of my first responses is a reboot of the
offensive box. Hopefully ~Eric or others will come along and club me for
that and say a good way to troubleshoot it that doesn't include debugging LSASS.
The fact that you had
machines not getting tickets before but are now is a wee bit scary as well.
joe From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Svetlana
Kouznetsova No, actually, we haven't disjointed
namespace in the first place. This kerberos error was on every W2K3 member
server only. I've promoted one of them to DC and that made keberos
happy - no more complains... No erorrs reported in dcpromo logs
either...Although I do have an issue with replication to this new DC -for
some reason NTDS settings in ADSS are empty and the event log on the DC,
from which it suppossed to replicate, mentions "there are no more endpoints
available from an endpoints mapper", which I am currently trying to sort out,
but no problems in netdiag and dcdiag
anymore... Lana From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of joe Oh, so did you have a
disjoint on the namespace? And if so is this intentional? Is it on all machines
or just this one? If not intentional and just on that one you should pop the NV
DomainName attribute and bring it in line with the rest of the environment. If
it is on all machines, you will most likely find you have the same kerberos
errors on them unless this one computer object was set up
incorrectly.
joe From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Svetlana
Kouznetsova You right about DC, Joe. Guess what
happenned after dcpromo? - kerberos error in netdiag...dissapeared! Now -
imagine how I feel after wasting so much time trying to fix
it! Wish Microsoft could warn about such
"little" things... Lana
|
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Svetlana Kouznetsova
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Mulnick, Al
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Svetlana Kouznetsova
- RE: [ActiveDir] FATAL kerberos error on W2K3... Patrick - IT Department
- RE: [ActiveDir] FATAL kerberos error on W2K3... joe
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Eric Fleischman
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Svetlana Kouznetsova
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Mulnick, Al
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Svetlana Kouznetsova
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Mulnick, Al
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Svetlana Kouznetsova
- RE: [ActiveDir] FATAL kerberos error on W2K3 serv... Svetlana Kouznetsova
