Key version number for principal in key table is incorrect

Turbo Fredriksson turbo at bayour.com
Tue Jun 4 09:36:10 EDT 2002


I'm setting  up two new machines  (morwen and rmgztk) that  is to take
over  the job  of  being  Kerberos/LDAP servers  from  my main  server
(papadoc).

Using the dump of the current database I'm doing every night, I sat up
the new KDC/KAdmin on rmgztk...

I can authenticate etc between tuzjfi, which is a test machine I'm
using to pre-test migrations etc on.

Getting a ticket on tuzjfi, from rmgztk goes well, but when I try to
ktelnet to papadoc (tuzjfi, rmgztk and morwen is behind a firewall),
using address-less tickets, I get

----- s n i p -----
[ Kerberos V5 refuses authentication because telnetd: krb5_rd_req failed: Key version number for principal in key table is incorrect ]
----- s n i p -----

If trying 'kadmin -p turbo at BAYOUR.COM' (on tuzjfi which is configured
to have rmgztk as KDC/KAdmin) I get the following in rmgztk's logs:

----- s n i p -----
Jun 04 15:30:32 rmgztk kadmind[1222](Notice): Authentication attempt failed: 192.168.1.4, GSS-API error strings are:
Jun 04 15:30:32 rmgztk kadmind[1222](Notice):     Miscellaneous failure
Jun 04 15:30:32 rmgztk kadmind[1222](Notice):     Key version number for principal in key table is incorrect
Jun 04 15:30:32 rmgztk kadmind[1222](Notice):    GSS-API error strings complete.
----- s n i p -----

Why do I get this, what did I do wrong when I loaded the database?
-- 
critical 767 supercomputer Clinton pits South Africa domestic
disruption terrorist nuclear president arrangements 747 SDI PLO North
Korea
[See http://www.aclu.org/echelonwatch/index.html for more about this]



More information about the Kerberos mailing list