G
Guest
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.
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.