Thanks,
Al
I've actually,
seen this and tried some of it already, but was confused by the fact, that this
is, actually - for W2K3 and I'm having mapper warnings on W2K servers...oh,
and another thing, I should mention, perhaps: in Ntfrs.log on W2K3 server there
are lots of "ACCESS DENIED" errors, which could be a clue to why nothing from
staging folders gets transferred into sysvol. (?) I wish there would be an easy
way to read them, logs (and understand them as well :-(...Certainly - not for
late night reading to me.
I will revise KB article tomorrow again and test things
from it, as well as what Joe suggested.
Thanks to
everybody...
Lana From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al Sent: 19 May 2004 22:18 To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] FATAL kerberos error on W2K3 server This may be helpful then
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Svetlana Kouznetsova Sent: Wednesday, May 19, 2004 4:28 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] FATAL kerberos error on W2K3 server on W2K3 (new
DC):
in FRS
event viewer there are only warnings 13508 ("having troubles to
replicate..../sysvol...etc"); dcdiag shows [FAILED] on test
frsevent;
netdiag - PASSED
all tests
on W2K (old DC in
the same domain) :
No errors in FRS;
in Directory
Service: warning NTDS KCC 1265 :
"The attempt to
establish a replication link with parameters
Partition: CN=Schema,CN=Configuration,DC=ulib,DC=ox,DC=ac,DC=uk Source DSA DN: CN=NTDS Settings,CN=SERS016,CN=Servers,CN=Oxford,CN=Sites,CN=Configuration,DC=ulib,DC=ox,DC=ac,DC=uk Source DSA Address: a2bdda54-6d14-40ae-842f-eb32df2dfb75._msdcs.ulib.ox.ac.uk Inter-site Transport (if any): failed with the following status: There are no more endpoints available from the endpoint mapper. The record data is the status code. This operation will be retried. " (SERS016 = new
W2K3 DC in ULIB domain.)
dcdiag
shows [FAILED] on kccevent test;
netdiag - PASSED all
tests
{Is it just me or does this sounds like a
replication island? (a.k.a. The Replication Roach Motel, i.e. changes get but
they never get out.)
Yes,
Wook, when I look at NTDS settings in ADSS
on W2K3 server - I can see all links there <automatically
generated>;
when I look at the same
on other W2K DC - for this particular server there are no links in NTDS settings
shown...
same with replmon -
when looking into it on W2K3 server - it sees itself and the rest of DCs fine,
but replmon on W2K DC can't see W2K3 at all
..for some reason your
notice reminded me good old "Hotel California" song...("you can check out any
time you like, but you can never leave")
Lana From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al Sent: 19 May 2004 20:26 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] FATAL kerberos error on W2K3 server What was it you said was the errors logged in the FRS event
viewer? 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... 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