[OpenAFS] Windows (1.5.76) integrated login problem

Jeffrey Altman jaltman@secure-endpoints.com
Wed, 01 Sep 2010 07:12:30 -0400


This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0F7CD422A96C0C9E0628A2BF
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I have opened bug #128022 for this issue.

  http://rt.central.org/rt/Ticket/Display.html?id=3D128022

Jeffrey Altman

On 8/31/2010 2:39 PM, geza@kzsdabas.hu wrote:
> Dear list,
>=20
> I have a strange problem:
> With 1.5.75 integrated login went smoothly, but with the hosts upgraded=

> (even the freshly installed ones) at version 1.5.76 integrated login fa=
ils
> with unknown error KT 4. Later on at NetidMgr (the version supplied wit=
h
> the latest kfw build) the user has tickets for everything, except afs,
> only after a few renew attempts the afs tokens are acquired. There are =
no
> AD credentials, as the users are logging into a samba3 (NT4 level) doma=
in.
>=20
> In the Eventlog the message is:
> 1 Application 177 Tue Aug 31 17:08:18 2010 1008 AFS Logon Unknown User =
N/A
> Warning ikb0 None Integrated login failed: Unknown code KTC 4 52
>=20
> Sorry if the format is unusual I've extracted it from the centralized l=
ogs
>=20
> Thanks for your help!
>=20
> Geza
>=20
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20


--------------enig0F7CD422A96C0C9E0628A2BF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJMfjUgAAoJENxm1CNJffh4iBwH/3ymRIsYZ2G1x/ByMMM2iM5o
85X+1EqmDeUpEKy+GZszcbLWwm5DGGBWo4ErKnZHeNb8oPC/BLyLBuf0LqwaNX4F
sqVIg6ZacZgyxdQLZWdD49ayfHehMaxDc/K02wis0ljyr4JN/6OkpHzBIwaG56i8
c1cnW/lH5jELxNUgjubrPJafLOnfs8HMKhW0k2cNO8mDDDH/oUgY8bdzNW8ZAHf9
QN1JUZAvuOf25iyTisK5nmQVcFqLbSAO2Qu1SFEWAmFaNMWKhRD+hmnt/FCwbhGF
d7xWvNQABdD7UxL9pZG7iIShkw+syxJIWeEYU/u16a/sGXc+5vLXEYWl5HeNIHw=
=d64b
-----END PGP SIGNATURE-----

--------------enig0F7CD422A96C0C9E0628A2BF--