Re: Netdiag Kerberos Fail
From: Jimmy Andersson [MVP] (jimmy_noSpam__at_mvps.org)
Date: 08/16/04
- Next message: Jimmy Andersson [MVP]: "Re: Migrating NT 4 PDC to Exisitng Win 2000 AD"
- Previous message: Jimmy Andersson [MVP]: "Re: Add new server to existing AD"
- In reply to: bjhink: "Re: Netdiag Kerberos Fail"
- Next in thread: Herb Martin: "Re: Netdiag Kerberos Fail"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 16 Aug 2004 20:03:50 +0200
Have you seen the MS Product Support's Reporting Tools?
http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-88B7-F9C79B7306C0&displaylang=en#filelist
Regards,
/Jimmy
-- Jimmy Andersson, Q Advice AB Microsoft MVP - Directory Services ---------- www.qadvice.com ---------- "bjhink" <bjhink@discussions.microsoft.com> wrote in message news:24305FF5-53C9-4758-812D-DF35687E3B4E@microsoft.com... > Can I run dcdiag and netdiag on a windows server 2003? Do I run the same > dcdiag/netdiag that I run on my windows 2000 machines? > > "Herb Martin" wrote: > > > "bjhink" <bjhink@discussions.microsoft.com> wrote in message > > news:0595DA15-BB85-471E-BC23-ECFCCFCFCE23@microsoft.com... > > > Upgraded our windows nt domain to windows server 2003 active directory. > > Our > > > windows 2000 prof workstations were getting event id 5788 5789 errors > > > constantly. Ran netdiag on workstation with a failure on kerberos and > > ldap. > > > It was suggested that I disjoint the workstation from the domain and > > rejoin, > > > which I did. This has solved our event id errors and the ldap failure in > > > netdiag. I am however still getting a failure in netdiag on kerberos. > > The > > > error states [FATAL] Kerberos does not have a ticket for computername$. I > > > don't seem to be having any trouble login in to the network or accessing > > > servers, etc. Can I ignore this error or is there something wrong here. > > > Thanks. > > > > It's usually a DNS problem -- run DCDiag on each DC and > > then check the following in your DNS setups: > > > > > > -- > > DNS > > 1) Dynamic for the zone supporting AD > > 2) All internal DNS client NIC\IP properties must specify SOLELY > > that internal, dynamic DNS server (set.) > > 3) DCs and even DNS servers are DNS clients too -- see #2 > > > > Restart NetLogon on any DC if you change any of the above that > > affects a DC. > > > > > > -- > > Herb Martin > > > > > > "bjhink" <bjhink@discussions.microsoft.com> wrote in message > > news:0595DA15-BB85-471E-BC23-ECFCCFCFCE23@microsoft.com... > > > Upgraded our windows nt domain to windows server 2003 active directory. > > Our > > > windows 2000 prof workstations were getting event id 5788 5789 errors > > > constantly. Ran netdiag on workstation with a failure on kerberos and > > ldap. > > > It was suggested that I disjoint the workstation from the domain and > > rejoin, > > > which I did. This has solved our event id errors and the ldap failure in > > > netdiag. I am however still getting a failure in netdiag on kerberos. > > The > > > error states [FATAL] Kerberos does not have a ticket for computername$. I > > > don't seem to be having any trouble login in to the network or accessing > > > servers, etc. Can I ignore this error or is there something wrong here. > > > Thanks. > > > > > > > > >
- Next message: Jimmy Andersson [MVP]: "Re: Migrating NT 4 PDC to Exisitng Win 2000 AD"
- Previous message: Jimmy Andersson [MVP]: "Re: Add new server to existing AD"
- In reply to: bjhink: "Re: Netdiag Kerberos Fail"
- Next in thread: Herb Martin: "Re: Netdiag Kerberos Fail"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
