[OpenAFS] !@#$ integrated logon

[Noel Burton-Krahn]

Hi Jeffrey,

I'm currently running _with_ loopback on WinXP.  This happens both with the
loopback and without it, on WinXP and Win2k.  I have never seen the afs
service start properly during afslogon on WinXP or Win2k under any
configuration (and I've tried quite a few).

I believe it may work if my Windows name was the same as my AFS account
name, but it's not.  I don't think integrated login should be nuked
completely, but there should be some way to completely disable it.  It's
such a relief to be spared a 2 minute hang after login followed by
"Integrated Login Failure".  Like I said, that's my clients major reason for
removing the AFS software.

--Noel



----- Original Message -----
From: "Jeffrey Altman" <jaltman@columbia.edu>
To: "Noel Burton-Krahn" <noel@bkbox.com>
Cc: <openafs-info@openafs.org>
Sent: Thursday, September 25, 2003 3:03 PM
Subject: Re: [OpenAFS] !@#$ integrated logon


> There are numerous things wrong with OpenAFS on Windows.  The integrated
> logon is just one of them.  From your description it sounds like you are
> not installing the MS Loopback adapter on your user's machines.  Is that
> true?
>
> I think it is reasonable behavior for AFS Integrated Logon to wait for
> the client service as long as the service state is START_PENDING.  In
> that case, you really need to know the outcome before you decide to fail.
>
> Jeffrey Altman
>
> Noel Burton-Krahn wrote:
>
> >AFS's integrated login has been a real pain for my users.  Most remove
the
> >windows clients after a few "Integrated Login failed" messages.  You can
see
> >the problem is in afslogon.c.  Even if the LogonOptions  registrey key is
0,
> >afslogon.dll always waits for the afs services to start, times out, then
> >fails.  Ugh.
> >
> >You can totally disable afslogon.dll by removing this key from the
registry:
>
>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Netw
o
> >rkProvider\AuthentProviderPath
> >
> >Yahoo! maybe we should fix afslogon.c sometime on th future too.
> >
> >
> >--Noel
> >
> >
> >PS: Rob Murawski, your NSIS/OpenAFS.nsi setup is missing a registry key.
> >
> >To failfully reproduce the (broken) afslogon.dll behaviour, you have to
> >append "TransarcAFSDaemon" to this registry key:
>
>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NetworkProvider\Provide
r
> >Order
> >(see
>
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/s
e
> >curity/authentication_registry_keys.asp)
> >
> >
> >
> >_______________________________________________
> >OpenAFS-info mailing list
> >OpenAFS-info@openafs.org
> >https://lists.openafs.org/mailman/listinfo/openafs-info
> >
> >
>