All,
We are seeing a rash of errors on some of our Windows NT 4.0
AFS clients on campus during calls to ktc_SetToken from our
own custom aklog application, and in klog.exe itself. The
error we are getting is KTC_RPC.
We've been running 3.4 and 3.5 clients on campus for 3 years
now, and have the 3.5 client on over 1400 machines, and this
is the first time we've seen anything like this, and I can't
make the error seem to go away. I'm in stage one of more
in-depth troubleshooting - and testing upgraded clients
(yes I know that's before stage one - but it's a little
complicated here to do and test that correctly because
we custom-repackaged the original 3.5 client, and the
patch updates don't work right to update our repackaged
install).
The major things that have changed are: we moved from a
custom replacement GINA environment - to a Novell-login
based environment - and we've upgraded our AFS services
backend (not all the file servers have moved) from
3.4 mumble to 3.5 (3.46).
What I'm asking before I go off and reinvent the broken
wheel is if anyone else has seen a lot of KTC_RPC errors
from klog or whatever and what, if anything, seemed to
fix the problem. (This note is a little simplistic, but
to describe the troubleshooting to date would take me
a while).
I'd appreciate it,
Jason
---------------------------------------------
Jason Young, Systems Programmer
ITD Computing Services
[EMAIL PROTECTED], 919.515.9778
---------------------------------------------
