Re: Slow Windows logins with AFS installed

Ted Anderson wrote:
> I reinstalled the OpenAFS client from the 1.4.1rc5 (non-debug) bits and
> configured it by deselecting all the integrated logon features.  I used
> RegEdit to turn on extra tracing.  I verified with Spybot - search and
> destroy, that AfsLogon and KFWLogon were reattached to afslogon.dll in
> System.ini as reported earlier[1].  Then I rebooted at about 20:30.

All the data is in the log entries.

2/1/2006 21:01:01 AFS Logon         AFS_Logon_Event - Start

2/1/2006 21:01:01 AFS Logon         AFS_Logon_Event Process ID: 260

2/1/2006 21:01:01 AFS Logon         Domain: ALOHOMORA

2/1/2006 21:01:01 AFS Logon         Got SID string
[S-1-5-21-117609710-1604221776-725345543-1001]
2/1/2006 21:01:16 AFS Logon         NameTranslate Init GC failed
[-2147023541]
2/1/2006 21:01:31 AFS Logon         NameTranslate Init Domain failed
[-2147023541]
2/1/2006 21:01:46 AFS Logon         Domain:

2/1/2006 21:01:46 AFS Logon         Got SID string
[S-1-5-21-117609710-1604221776-725345543-1001]


You can see above that there are three delays of 15 seconds.  These
delays are the Windows machine attempting to contact your domain
controller.  If you read the release notes, Integrated Login can be
enabled on a per-domain basis.  The Network Provider is asking Windows
to tell us the domain of the user so we can look in the registry to
determine if Integrated Login should be used or not for this login.
The Network Provider makes a number of calls because it must support
both Active Directory and NT4/Samba.

My laptop is joined to a domain and I am frequently on the road
such that my laptop cannot reach the domain controller.  I never see
these delays.   The question I am wondering is "why are you seeing
these delays?"  15 seconds per call is pretty regular.  If you have
a method of watching the traffic in a network monitor it would be
interesting to see what it is attempting to do.

Jeffrey Altman

P.S. - openafs-bugs is an automated request tracker.  please do
not cc'd it to mail traffic sent to the mailing list.  If you do,
every person who "replies to all" will create a new ticket in the
request tracker.