Some further tests.

>Does the 1.5.36 version of afslogon.dll work when installed with 1.5.61?

No. Not with 1.5.59 anyway.

>Were you using the incomplete LOCALHOST and LTU.SE registry keys with 
>1.5.36?

No. The problem is the same.

With incomplete do you refer to the fact that the key LogonOptions should be 
present?
I was under the impression that Integrated Logon is used if this key is not 
present.
On the other hand it makes perfect sense to add it for the LOCALHOST.

The "LoginRetryInterval" and "LoginSleepInterval keys doesn't seem to work 
either. Not in this Domain anyway. With earlier tests in our staff domain 
everything seems to work fine. Including this very problem.


Then enabling TraceOption at 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters

From application log:

AFS Logon: The following information is part of the event: NPLogonNotify - 
LoginId(0,301835).
AFS Logon: The following information is part of the event: In 
GetDomainLogonOptions for user [anha] in domain [LTU.SE].
Userenv: Windows cannot locate the server copy of your roaming profile...
Userenv: Windows cannot find the local profile and is logging you on with a 
temporary profile...
Folder Redirection: Failed to perform redirection of folder Desktop....
Folder Redirection: Failed to perform redirection of folder My Documents...
Userenv: The Group Policy client-side extension Folder Redirection failed to 
execute...
AFS Logon: The following information is part of the event: AFS_Logon_Event - 
Start.
AFS Logon: The following information is part of the event: AFS_Logon_Event 
Process ID: 720.
AFS Logon: The following information is part of the event: AFS_Logon_Event - 
pInfo UserName and Domain.
AFS Logon: The following information is part of the event: AFS_Logon_Event - 
Calling GetDomainLogonOptions.
AFS Logon: The following information is part of the event: In 
GetDomainLogonOptions for user [anha] in domain [LTU.SE].

And here is then winlogon craches and the system reboots. This happens then 
logging is enabled.
Logging then needs to be disabled remotely


Strangely enough on at least two computers this problem doesn't show up. Surely 
there is some difference but there should not be much.


/Anders Hannus


-----Original Message-----
From: Jeffrey Altman [mailto:[email protected]] 
Sent: den 6 augusti 2009 22:10
To: Anders Magnusson
Cc: [email protected]; Anders Hannus
Subject: Re: [OpenAFS] Strange problem with Windows client.

Does the 1.5.36 version of afslogon.dll work when installed with 1.5.61?

When you enable afslogon debugging, what are the error codes reported
during token acquisition?

Were you using the incomplete LOCALHOST and LTU.SE registry keys with
1.5.36?

Jeffrey Altman

Anders Magnusson wrote:
> Hi,
> 
> we have encountered a really strange problem when creating images for
> reinstallation
> of our Windows XP machines in out computer labs. All machines has
> mandatory profiles
> located on AFS. 
> 
> The problem is that when logging in to a newly installed machine it will
> try to fetch the
> profile and redirect Desktop and My Documents before the user has got a
> token,
> therefore loading profile and redirecting will fail.  But when the user
> is logged in,
> a token exists and AFS works as expected. Setting access to the profile to
> system:anyuser will allow the profile to be loaded.
> 
> This fails with clients 1.5.{59,60,61), but works with last years client
> 1.5.36.
> 
> More on, after trying to track the bug down, we found that if any of
> these three
> registry entries is set loading the mandatory profile will fail, but it
> works as
> it should if none of them are present:
> 
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]
> 
> "FailLoginsSilently"=dword:00000001
> 
>  
> 
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LTU.SE]
> 
> "LoginRetryInterval"=dword:0000001e
> 
> "LoginSleepInterval"=dword:00000005
> 
> 
> 
> The machines tested all runs Windows XP SP3 with all the recommended
> hotfixes.
> 
> Any ideas?  We are running out of them...
> 
> -- Ragge
> _______________________________________________
> OpenAFS-info mailing list
> [email protected]
> https://lists.openafs.org/mailman/listinfo/openafs-info
> 

Reply via email to