KFW 2.6.1

[Jeffrey Altman]

Dan:

Quoting from the release notes:

	System Requirements
	Operating System

	KfW requires Windows 95, 98, 98SE, ME, NT 4.0, 2000, XP, 2003
	or higher.

To disable the request of Kerberos 4 tickets in Leash, access the
Options->Leash Properties... dialog and uncheck the "Request Krb4 
credentials"checkbox.

This setting does not affect the command line kinit.exe command.
If you wish to use the command line to only obtain Kerberos 5
tickets you must use the -5 option.  Feel free to file a feature request 
at kfw-bugs at mit.edu and I will strive to make this change for the next 
release.

As for why you are unable to obtain a KDC from Leash but can from
kinit.exe, I have no idea.  They should both be using the same krb5.ini
file and the same libraries.  Are you sure you have only one version
of KFW on the machine?

Jeffrey Altman




Dan Million wrote:
> Hi.  I've run Kerberos on Unix boxes for years, but never on Windows. 
> Now I have a user who has installed the MIT KFW 2.6.1 and is having 
> problems.
> 
> He wants KRB5 tickets only.  kinit from a command window always fails:
> 
>   kinit<v524>: Cannot contact any KDC for requested realm converting 
> to     V4 credentials
>   kinit<v4>: Can't send request <send_to_kdc>
>   Maybe your KDC does not support v4. Try the -5 option next time.
> 
> If he uses "kinit -5" it works OK.  This in itself is not a big problem, 
> but he can't get Leash to work at all.  He gets a popup which says:
> 
>   Ticket initialization failed.
>   Kerberos 5: Cannot find KDC for the rquested realm (error 154)
> 
> We have flipped all kinds of options in the Leash config screens, and it 
> has not helped.
> 
> Is there a simple secret to getting this to work with a KRB5 KDC that we 
> have overlooked?  We have no interest in KRB4 tickets.  (By the way, 
> this is on Windows XP, which is not mentioned as being supported in the 
> release notes.)
> 
> Thanks.
> 
> Dan
> 

-- 
-----------------
This e-mail account is not read on a regular basis.
Please send private responses to jaltman at mit dot edu