[OpenAFS] Strange behaviour of Windows AFS client for Windows NT

Michael Lasevich openafslist@lasevich.net
Thu, 25 Apr 2002 11:22:31 -0700


I have the same setup, but everything seems to work fine (I get 10 hour
expiration time) however the token start date seems to be to epoch (12/31/69
16:00:00) which does not affect anything. I would guess there may be
something wrong with your krb524d process. Is the expiration time of your K5
ticket also screwed up? What about the afs K5 ticket? In my case all 3 have
same expiration time.

Also, what are you using to get the MIT version of K5 ticket and the AFS
token? Bill Richardson of Rose-Hulman Institute of Technology wrote a pretty
awesome windows app called WinAFSEnabler that combines ms2mit and aklog (and
a few other things). You find it at
http://www.rose-hulman.edu/~richarwk/WinAFSEnabler/ . Works great (except I
had some trouble with having cell name not same as realm name, but I made a
small mod to it to be able to overwrite the auto-set values)


-Michael

----- Original Message -----
From: "Fabian Aichele" <faichele@primusnetz.de>
To: <openafs-info@openafs.org>
Sent: Thursday, April 25, 2002 9:35 AM
Subject: [OpenAFS] Strange behaviour of Windows AFS client for Windows NT


> Hello!
>
> A week ago I received a lot of extremely useful help on AFS authentication
> against a Windows 2000 KDC. After three days of experimentation I
> successfully made a Linux workstation get AFS tokens from a Windows 2000
KDC
> with a krb524d running on my AFS server to handle V4 ticket conversion.
> The next thing I tried was to get the OpenAFS client for Windows NT to do
> the same. I configured the AFS cell settings exactly as I did for Linux.
>
> When I try to obtain an AFS token, I get one, but its lifetime is dated
> "tokens expire 02:21:28 01.01.1601", which obviously does not make sense.
>
> Has anyone encountered a similar problem with the combination of a Windows
> 2000 KDC and a krb524d on a Unix station for AFS authentication and the
> OpenAFS for Windows NT client?
> Or is this a known problem?
>
> Regards,
> Fabian Aichele
>
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>