Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA10331; Wed, 20 Dec 95 17:00:28 EST
Received: from pad-thai.cam.ov.com by MIT.EDU with SMTP
	id AA24337; Wed, 20 Dec 95 16:44:00 EST
Received:  by pad-thai.cam.ov.com (8.6.12/)
	id <QAA17451@pad-thai.cam.ov.com>; Wed, 20 Dec 1995 16:46:55 -0500
Received: from GATEWAY by pad-thai.cam.ov.com with netnews
	for kerberos-wrapper@cam.ov.com (kerberos@mit.edu)
To: kerberos@MIT.EDU
Date: 20 Dec 1995 20:58:12 GMT
From: frnkzk@ (Kevin Kane)
Message-Id: <4b9td4$fgs@eagle.dmv.com>
Organization: Arcturus, The Bear Guard
Sender: usenet@cam.ov.com
Subject: Service tickets for K4 login with K5 server


I am using a K4-based login program, but have a K5 KDC.  I cannot do a
root login from the console, so I am guessing that something is wrong
with service tickets (much like ksu will not work if there is no host
ticket in /etc/v5srvtab).  But I can't seem to find where to put this
stuff.  I've tried using v5 and v4 srvtabs, but no dice.  Can anyone
tell me what ticket I need to make in the principal database, whether
to extract it as v5 or v4, and where to put it?  Many thanks.
-- 
Kevin Kane (Frnkzk) / Rockville, Maryland, USA / frnkzk@musenet.org

