Netdiag kerberos failure
From: bjhink (bjhink_at_discussions.microsoft.com)
Date: 08/13/04
- Next message: bjhink: "Re: Connecting two switches with auto-uplinks?"
- Previous message: Steven L Umbach: "Re: Lost Network Access to Netlogon"
- Next in thread: Steven L Umbach: "Re: Netdiag kerberos failure"
- Reply: Steven L Umbach: "Re: Netdiag kerberos failure"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 12 Aug 2004 22:09:02 -0700
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: bjhink: "Re: Connecting two switches with auto-uplinks?"
- Previous message: Steven L Umbach: "Re: Lost Network Access to Netlogon"
- Next in thread: Steven L Umbach: "Re: Netdiag kerberos failure"
- Reply: Steven L Umbach: "Re: Netdiag kerberos failure"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
