[OpenAFS] Re: Integrated Login problem

Jeffrey Altman jaltman@your-file-system.com
Sun, 18 Nov 2012 18:11:38 -0500


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

-1765328164 =3D Cannot resolve network address for KDC in requested realm=


aklog -d will tell you what realm is being queried.


On 11/18/2012 4:22 AM, R. Laatsch wrote:
> Dear all,
> there is a problem with Integrated Login here.
>=20
> This is my setup:
> Server: 'slinux.localdomain' (SL58) with AFS cell test.rl and krb5kdc f=
or realm TEST2.RL
> (not the standard name).
> The Afs version is openafs-1.6.1, the krb5 version is krb5-1.10.3 .
> The kdc has entries for the user and afs/test.rl (DES type).
>=20
> Client: Windows-7 (VirtualBox) with AFS, KfW, NIM installed. Realm set =
to TEST2.RL
> The KfW version is MIT 3.2.2
>=20
> Login to the Client gives an 'unknown RPC error (-1765328164)' and no A=
FS token.
> Doing manually 'gssklog.exe' (with password), i do get a token.
> But there seems to be no 'gssklog Auth Provider' for NIM, that could he=
lp circumvent the=20
> 'wrong realm name' problems.
> On the linux server after kinit user, aklog -d gets me a working token.=
=20
>=20
> The realm name was chosen to check out problems under Windows.
> I do *NOT* want CrossRealm Authentication.
>=20
> Any help in this matter would be greatly appreciated.
>=20
> Somewhere I found 'linked cells' mentioned (double named cells in CellS=
ervDB), but no hints
> to do it correctly. Did someone use this to bypass above problem?
>=20
> Best regards
> Rainer
> ________________________________________________
> Kerberos mailing list           Kerberos@mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
>=20


--------------enig866C92889EE5270E87067A3A
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)

iQEcBAEBAgAGBQJQqWssAAoJENxm1CNJffh4Rp4H/3yKPeXlG8IzcIOJO2HBVi8X
1CkaISbT7ont4rxCnTHstef4QHc3GqVNrxSYhz0CAnmI4UoTlRcTj+66AYGm3eyu
0bYN6h+pZM+XIt+7LwKjtZYgGTTu3ulis4Wo9kpusXSA8YF4Nt6esvUVXlRUHi1C
IQQK3TEJ2zpLLjHwogPov8AdNPCu86dt4YetM6yC9y1iUDWDzA/O50sv96y19bdw
GgJQSvnAAdJmbYsQRhLcI2rgk8vooHVLqyZpO+kfhKbUub5AjaNP3NWqKEyDkri2
zTBBxVbPu4IPEkaWvqoGL9KKkKlC46kiHyW14xjtbd2f4SwFFp0fXeolvqjX6Lo=
=SIMq
-----END PGP SIGNATURE-----

--------------enig866C92889EE5270E87067A3A--