Why is kaserver starting kerberos service on port 88?

[Stephen G. Roseman]

Several weeks ago, I tried to get the /etc/services ports "right" on our 3
AFS servers (@(#)Base configuration afs3.4 5.77)  Per Transarc docs, I put 
kerberos5 on 88 and kerberos (plus kerberos4 and kerberos-iv) on 750.  I
restarted the kaservers, and AuthLog said "kerberos/udp port=750, 
kerberos5/udp port=88".  Good.

All 3 servers have been restarted at least once since then (for various
reasons), but for some reason 2 of them now refuse to listen on 750. AuthLog
says "kerberos/udp port=88, kerberos5/udp port=88".  The "first" server is
fine.  /etc/services had not touched since then.

The relevant lines in all 3 /etc/services are:
kerberos5       88/tcp                          # Kerberos
kerberos5       88/udp                          # Kerberos
kerberos4       750/tcp kerberos kerberos-iv    # Kerberos
kerberos4       750/udp kerberos kerberos-iv    # Kerberos

Swapping the words "kerberos4" and "kerberos" in the 750 lines (and of course
restarting kaserver) has no effect.

Even if I comment out the 4 lines, AuthLog says: "kerberos/udp port=88,
kerberos5/udp is unknown; check /etc/services.  Using port=88 as default".

lsof on the "good" one shows:
kaserver 14710 root    9u  IPv4 0x70038b00      0t0   UDP *:kerberos4 
kaserver 14710 root   10u  IPv4 0x700d9700      0t0   UDP *:kerberos5 

and on the other 2:
kaserver 15996 root    9u  IPv4 0x70086500      0t0   UDP *:kerberos5 

What could have changed?  How do I get 750 back so my krb-kth clients will
run regardless of the server?  Should I forget about 750 and just use 88? 

Thanks,
Steve

----------------------------------------------------------------------------
Steve Roseman
Lehigh University Computing Center
[EMAIL PROTECTED]