[OpenAFS] OpenAFS inconsistent behavior - Windows 7 32 bit

Jeffrey Altman jaltman@secure-endpoints.com
Tue, 23 Aug 2011 16:38:36 -0400


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

On 8/23/2011 3:20 PM, Dvorkin, Asya wrote:
> Hi everyone,
>=20
> I've been working on getting OpenAFS to work on Windows 7 32 bit and ha=
ving some issues.  A little bit about the system:
>=20
> Virtual Machine running on Mac (tested on a desktop as well with simila=
r results)
> Windows 7 32bit fully patched.
> OpenAFS - 1.5.9906
> MIT Kerberos - 1.3.1.0
>=20
> My problem that it works very inconsistently.  It's working (case 1) I =
reboot and all of a sudden it stops working (case 2).  Could it be relate=
d to the network performance?  There is also a third case where it can't =
even successfully get initial kerberos credentials (case 3).  All logs ar=
e below.  Did anyone get OpenAFS work properly on Windows 7 32 bit?  Than=
k you for all your help.

The logs you are quoting are Network Identity Manager logs.  Network
Identity Manager is an application that runs within the user logon
session.  OpenAFS will always have started prior to the logon session
desktop appears.

Kerberos authentication must always occur after OpenAFS starts.  If
OpenAFS has not started, there is no service with which to register AFS
tokens.

I suggest you read the OpenAFS for Windows Release Notes that are
installed on your Windows system along with OpenAFS.  In particular,
read the Troubleshooting section.   It describes the various logs used
by OpenAFS and the tools you can use to assist with debugging.

Jeffrey Altman


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

iQEcBAEBAgAGBQJOVA/OAAoJENxm1CNJffh4jVQH/3yfL+qvnBzmZZHCTBKffPTs
s24Pyvjvy0RFBNOGN9d26KnpMjY28E9xxRZ7ZS0n41xnp8023owIM8S4jf/z7O3b
sWJcTsMkqI3SHh/BrxXOy4fb+R+dN+BISnL7KUHiMbk7fS2mIcQcJ1rmvigcvifB
xQuk4v6sCbJzY00i7zDp2t9LW1CqrEF3gYp4GXQRklEqyVL6Lu7/sApP8p4+e6e1
Uw4DKP/6WOy1KyJHZ4AyTXkAsNFIIKKhU7NTIEkGfvT0TwdEXU1Yxa90b0D+7NlG
Y1R5AMZNxfme0r2xND6SF00wdlt0/PECrRTGG3NCiIerMUVqLVCAjQ5WmEOlIJo=
=1Ry1
-----END PGP SIGNATURE-----

--------------enig4A6BAE227BFDC1C92A4FF9DD--